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.
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=207470
Jaroslav Kortus <jkortus(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jkortus(a)redhat.com
--- Comment #28 from Jaroslav Kortus <jkortus(a)redhat.com> 2012-03-27 13:51:46 EDT ---
I found another way how to mount images which (may) have duplicate vg names:
1. setup loopback device with the name
2. setup loopback device for data you are going to write to it (must have)
3. use device mapper to map loopback device to dm target, read-only (will
allow us to use snapshots)
4. create writeable snapshot of the device from 3.
5. use kpartx to map partitions to new dm devices (kpartx -a <device from 4.>)
6. use vgcloneimport -n my_not_colliding_vg_name /dev/mapper/jkdev_snap2
(replace with output from 5)
7. pvscan, lvscan, vgchange ... all that fun you wish to do with the newly
created VG and its LVs
The reason for using this is that vgcloneimport destroys the mapping and
corrupts the image (no longer bootable without further changes) by changing
UUIDs/names. This way the changes go right to the snapshot and keeps the
original image intact.
If you wish to write to the original image while you are doing backup, it would
be better to create proper snapshot with snapshot-origins as described in
http://www.redhat.com/archives/dm-devel/2004-July/msg00071.html (use dm create
... --notable). For shutdown&examine (my case) this is probably the most simple
way.
Clean up via dmsetup remove <device> and losetup -d.
# sample script:
imgfile="/var/lib/libvirt/images/node02.img"
snapfile="/var/lib/libvirt/images/snapshot.img"
devname="jkdev"
snap="jkdev_snap"
loop1="/dev/loop1"
loop2="/dev/loop2"
# loop device
# map loop1 -> image file
# map loop2 -> snapshot file
losetup -r $loop1 $imgfile
dd if=/dev/zero of=$snapfile bs=1M seek=100 count=0
losetup $loop2 $snapfile
# map dm -> loop1
dmsetup -r create $devname --table "0 `blockdev --getsize $loop1` linear $loop1
0"
# snapshot mappings
dmsetup create $snap --table "0 `blockdev --getsize /dev/mapper/$devname`
snapshot /dev/mapper/$devname $loop2 p 64 "
--
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.
https://bugzilla.redhat.com/show_bug.cgi?id=199246
Bill McGonigle <bill-bugzilla.redhat.com(a)bfccomputing.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bill-bugzilla.redhat.com@bf
| |ccomputing.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.
Product: Fedora
Version: 14
Component: esc
abrt-bot(a)fedoraproject.org has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 622147: [abrt] crash in esc-1.1.0-12.fc13: raise: Process
/usr/lib64/esc-1.1.0/esc was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=622147
Product: Fedora
Version: 14
Component: abiword
abrt-bot(a)fedoraproject.org has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 576231: [abrt] crash in abiword-1:2.8.2-1.fc12: Process /usr/bin/abiword
was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=576231
Product: Fedora
Version: rawhide
Component: gdb
abrt-bot(a)fedoraproject.org has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 612572: [abrt] crash in gdb-7.1-28.fc13: raise: Process /usr/bin/gdb was
killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=612572
Product: Fedora
Version: 14
Component: abiword
abrt-bot(a)fedoraproject.org has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 576014: [abrt] crash in abiword-1:2.8.2-1.fc12: Process /usr/bin/abiword
was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=576014
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=246990
Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|lemenkov(a)gmail.com |fedora(a)affix.me
--- Comment #5 from Fedora Admin XMLRPC Client <fedora-admin-xmlrpc(a)redhat.com> 2012-03-18 17:49:54 EDT ---
This package has changed ownership in the Fedora Package Database. Reassigning
to the new owner of this component.
--
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.