[Bug 1315525] New: perl-Net-DNS-1.05 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1315525
Bug ID: 1315525
Summary: perl-Net-DNS-1.05 is available
Product: Fedora
Version: rawhide
Component: perl-Net-DNS
Keywords: FutureFeature, Triaged
Assignee: pwouters(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
psabata(a)redhat.com, pwouters(a)redhat.com
Latest upstream release: 1.05
Current version/release in rawhide: 1.04-3.fc24
URL: http://search.cpan.org/dist/Net-DNS/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
6Â years, 2Â months
[Bug 1389064] New: EPEL7 branch missing (required for psad)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1389064
Bug ID: 1389064
Summary: EPEL7 branch missing (required for psad)
Product: Fedora
Version: rawhide
Component: perl-IPTables-ChainMgr
Assignee: mitr(a)redhat.com
Reporter: dominik(a)greysector.net
QA Contact: extras-qa(a)fedoraproject.org
CC: mitr(a)redhat.com, perl-devel(a)lists.fedoraproject.org
Description of problem:
EPEL7 branch is missing for perl-IPTables-ChainMgr, preventing psad from being
installed. Please build it for EPEL7.
--
You are receiving this mail because:
You are on the CC list for the bug.
6Â years, 2Â months
[Bug 1447528] New: perl-MojoX-JSON-RPC-0.10-2.fc27 FTBFS: Can'
t locate object method "is_status_class" via package "Mojo::Message::
Response"
by bugzillaï¼ redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1447528
Bug ID: 1447528
Summary: perl-MojoX-JSON-RPC-0.10-2.fc27 FTBFS: Can't locate
object method "is_status_class" via package
"Mojo::Message::Response"
Product: Fedora
Version: rawhide
Component: perl-MojoX-JSON-RPC
Assignee: emmanuel(a)seyman.fr
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: emmanuel(a)seyman.fr, perl-devel(a)lists.fedoraproject.org
External Bug ID: CPAN 121395
perl-MojoX-JSON-RPC-0.10-2.fc27 fails to build in F27 because tests fail like
this:
Can't locate object method "is_status_class" via package
"Mojo::Message::Response" at t/../lib/MojoX/JSON/RPC/Client.pm line 111.
# Looks like your test exited with 255 just after 2.
t/basic.t ......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 34/36 subtests
This is caused by upgrading perl-Mojolicious from 7.30-1.fc27 to 7.31-1.fc27
that removed deprecated methods.
--
You are receiving this mail because:
You are on the CC list for the bug.
6Â years, 3Â months
[Bug 1473017] New: amavisd-new-2.11.0-1 has issue with DCC, can'
t write to /etc/dcc
by bugzillaï¼ redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1473017
Bug ID: 1473017
Summary: amavisd-new-2.11.0-1 has issue with DCC, can't write
to /etc/dcc
Product: Fedora EPEL
Version: epel7
Component: amavisd-new
Severity: low
Assignee: j.orti.alcaine(a)gmail.com
Reporter: pb(a)bieringer.de
QA Contact: extras-qa(a)fedoraproject.org
CC: janfrode(a)tanso.net, j.orti.alcaine(a)gmail.com,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org,
vanmeeuwen+fedora(a)kolabsys.com
Description of problem:
since upgrading EL7 system strange DCC messages are occuring.
Version-Release number of selected component (if applicable):
amavisd-new-2.11.0-1
How reproducible:
always
Steps to Reproduce:
1. have amavisd+spamassassin+DCC installed
Actual results:
Jul 19 22:29:57 *** dccproc[29496]: open(/etc/dcc/map): Permission denied
Jul 19 22:29:57 *** dccproc[29496]: lock_open(/etc/dcc/whiteclnt.dccx):
Permission denied; file not writeable for locking
Expected results:
Working as before the update
Additional info:
related systemd unit file changed,
2.11.0-1 added:
ProtectSystem=full
This prevents dccproc from writing to /etc/dcc
"Workaround": reduce restriction to
ProtectSystem=true
Looks like systemd.exec is missing a feature, because
ReadWritePaths=-/etc/dcc
is not supported on ProtectSystem=full, only on ProtectSystem=strict (which is
even more hard...)
Imho "full" should already honor ReadWritePaths
--
You are receiving this mail because:
You are on the CC list for the bug.
6Â years, 3Â months
[Bug 1408326] New: build for EPEL7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1408326
Bug ID: 1408326
Summary: build for EPEL7
Product: Fedora EPEL
Version: epel7
Component: perl-EV
Assignee: emmanuel(a)seyman.fr
Reporter: carl.george(a)rackspace.com
QA Contact: extras-qa(a)fedoraproject.org
CC: emmanuel(a)seyman.fr, perl-devel(a)lists.fedoraproject.org
I'm a co-maintainer of uwsgi in Fedora and EPEL. Uwsgi has a subpackage for a
coroae plugin, but it is disabled on EPEL7 because it needs perl-Coro, which
needs this package. Please consider adding an EPEL7 branch for perl-EV so that
I can enable the uwsgi-plugin-coroae subpackage for EPEL7.
--
You are receiving this mail because:
You are on the CC list for the bug.
6Â years, 3Â months
[Bug 1029710] New: Amavisd fails to identify attached zipped files with .exe extensions
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1029710
Bug ID: 1029710
Summary: Amavisd fails to identify attached zipped files with
.exe extensions
Product: Fedora EPEL
Version: el6
Component: amavisd-new
Severity: medium
Assignee: steve(a)silug.org
Reporter: s10dal(a)elrepo.org
QA Contact: extras-qa(a)fedoraproject.org
CC: janfrode(a)tanso.net, kanarip(a)kanarip.com,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org
Description of problem:
Mail attachments containing zipped files with .exe extensions are not properly
identified due to a failure of 7za (p7zip) as called by amavisd to correctly
list the contents of the zipped file. Based on maillog errors, the failure
appears to be due to an improperly composed 7za option, specifically -w not
being separated from the target by a separator (e.g., space character).
Manually executing 7za using the options noted in the maillog error (see below)
demonstrates the need to insert a separator between the -w option and the
target.
Fails: $ 7za l -slt -w./contains_exe.zip
Works: $ 7za l -slt -w ./contains_exe.zip
Also, this issue may be specific to EL6. This issue came to my attention
because an EL6 mail server acting as a Backup MX for an EL5 mail server was
forwarding zipped exe attachments, which were correctly identified and
quarantined on the EL5 system.
Version-Release number of selected component (if applicable):
# uname -rpmi
2.6.32-358.23.2.el6.i686 i686 i686 i386
# rpm -q amavisd-new p7zip
amavisd-new-2.8.0-4.el6.noarch
p7zip-9.20.1-2.el6.i686
How reproducible:
Very. Observed on 3 EL6 mail servers.
Steps to Reproduce:
1. Install/configure postfix, amavisd-new, clam\*, etc.
2. Create a test attachment:
$ touch test.exe
$ 7za a -tzip test_exe.zip test.exe
3. Send a mail with test_exe.zip attached
4. Check /var/log/maillog for the specific error
Actual results:
From /var/log/maillog:
Nov 12 17:17:46 Mail amavis[1568]: (28807-12) (!)run_command: child process
[1568]: run_command: failed to exec /usr/bin/7za l -slt
-w/var/spool/amavisd/tmp/amavis-20131112T051218-28807-HPbWePoN/parts --
/var/spool/amavisd/tmp/amavis-20131112T051218-28807-HPbWePoN/parts/p002: 13 at
/usr/sbin/amavisd line 4062.
Nov 12 17:17:46 Mail amavis[28807]: (28807-12) (!)Decoding of p002 (Zip archive
data, at least v1.0 to extract) failed, leaving it unpacked: do_7zip: can't get
a list of archive members: exit 6; at (eval 117) line 781.
Expected results:
Identify zipped exe file as such.
Additional info:
It may not be relevant to the observed error, but 8 months ago, amavisd-new and
clam\* were converted from RepoForge/RPMforge versions to EPEL versions. Except
for a few initial hiccups, the mail servers have been running without apparent
issues until the current 7za issue was observed.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=KMKdGzsZdn&a=cc_unsubscribe
6Â years, 4Â months