Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Error at calling service amavisd restart when SELinux is in enforce mode
https://bugzilla.redhat.com/show_bug.cgi?id=480129
Summary: Error at calling service amavisd restart when SELinux
is in enforce mode
Product: Fedora EPEL
Version: el5
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: amavisd-new
AssignedTo: steve(a)silug.org
ReportedBy: frank-buettner(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.5)
Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)
Version: amavisd-new-2.4.5-1.el5
When run service amavisd restart I get the message:
amavisd beenden: Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
/proc /proc proc defaults
In the meantime, run "mount /proc /proc -t proc"
Daemon [2389] terminated by SIGTERM
[ OK ]
amavisd stopped
amavisd starten: [ OK ]
Reproducible: Always
Steps to Reproduce:
1. run service amavisd restart
Actual Results:
Getting the message above.
Expected Results:
restart without the messeage
--
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: Fedora::Bugzilla - get_flag() doesn't work for all flags
https://bugzilla.redhat.com/show_bug.cgi?id=529172
Summary: Fedora::Bugzilla - get_flag() doesn't work for all
flags
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl-Fedora-Bugzilla
AssignedTo: cweyl(a)alumni.drew.edu
ReportedBy: jpirko(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: cweyl(a)alumni.drew.edu,
fedora-perl-devel-list(a)redhat.com, mmaslano(a)redhat.com
Classification: Fedora
Target Release: ---
Created an attachment (id=364891)
--> (https://bugzilla.redhat.com/attachment.cgi?id=364891)
test script
Description of problem:
I have trouble with get_flag() method of Fedora::Bugzilla::Bug. It works for me
for all flags except of "rhel-5.5.0" (and probably others). When I walk thru
the flags manually, the flag is there.
Version-Release number of selected component (if applicable):
0.10-1 - I tried 0.13 from CPAN and problem is still there.
How reproducible:
always
Steps to Reproduce:
run attached script
Actual results:
has pm_ack
+
has rhel-5.5.0
can't get rhel-5.5.0 flag
devel_ack, +
qa_ack, +
pm_ack, +
rhel-5.5.0, +
Expected results:
has pm_ack
+
has rhel-5.5.0
+
devel_ack, +
qa_ack, +
pm_ack, +
rhel-5.5.0, +
--
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: perl-Pugs-Compiler-Rule
https://bugzilla.redhat.com/show_bug.cgi?id=611015
Summary: perl-Pugs-Compiler-Rule
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: low
Component: perl-Pugs-Compiler-Rule
AssignedTo: steve(a)silug.org
ReportedBy: rc040203(a)freenet.de
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Description of problem:
perl-Pugs-Compiler-Rule fails to build in rawhide.
Version-Release number of selected component (if applicable):
perl-Pugs-Compiler-Rule-0.37-5.fc14
How reproducible:
Always.
Steps to Reproduce:
1. rebuild the package
Actual results:
Fails to build.
Expected results:
Success.
Additional info:
* Apparently this package is incompatible to perl-5.12 and can't be built
against it.
* Its upstream appears dead.
This package needs to be made working or it will have to be removed from
Fedora >= 14. AFAICT, this package is not used by Fedora itself, so it's
probably safe to remove it.
--
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: non-responsive maintainer
https://bugzilla.redhat.com/show_bug.cgi?id=614982
Summary: non-responsive maintainer
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl-Pugs-Compiler-Rule
AssignedTo: steve(a)silug.org
ReportedBy: iarnell(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Steve,
please respond to bug #611015.
perl-Pugs-Compiler-Rule fails to build under perl 5.12. It should either be
fixed
or retired. According to rel-eng, perl-sig and perl maintainer can't initiate
EOL for these packages[1].
There have also been automatic broken dependency mails for several weeks
already.
[1] https://fedorahosted.org/rel-eng/ticket/3882
--
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 report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247253
Summary: Conflicting Provides
Product: Fedora
Version: f7
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: perl-Time-Piece-MySQL
AssignedTo: chris(a)chrisgrau.com
ReportedBy: bugs.michael(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
perl-Time-Piece provides perl(Time::Piece) EQ 0 1.09
perl-Time-Piece-MySQL provides perl(Time::Piece)
required by: perl-Email-Date - 1.102-2.fc7.noarch
required by: perl-Time-Piece-MySQL - 0.05-3.fc6.noarch
required by: perl-Time-Piece-MySQL - 0.05-3.fc6.noarch
required by: perl-Email-Date - 1.102-2.fc7.noarch
Indeed. perl-Time-Piece-MySQL does not include a Time::Piece
module and therefore must not provide perl(Time::Piece).
Luck has it that a second dependency on Time::Seconds
pulls in perl-Time-Piece. Else it would break.
[...]
Further reference, similar cases:
https://www.redhat.com/archives/fedora-perl-devel-list/2007-July/msg00011.h…
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=450412
Summary: please build in EL-5
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: perl-JSON
AssignedTo: cweyl(a)alumni.drew.edu
ReportedBy: jonstanley(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: bpeck@redhat.com,dmalcolm@redhat.com,fedora-perl-devel-
list@redhat.com,jlaska@redhat.com,poelstra@redhat.com
If you could branch this module for EL-5, it's required for Testopia, which is
currently under review.
I'd be happy to be co-maintainer for EPEL if you'd like, it builds fine as is in F9.
--
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, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=603502
Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process
/usr/bin/perl was killed by signal 11 (SIGSEGV)
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:1c0f880ad9686d02efbd3096ee944822c284105a
Severity: medium
Priority: low
Component: perl-Padre
AssignedTo: mmaslano(a)redhat.com
ReportedBy: it_rom(a)gmx.de
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
mmaslano(a)redhat.com, ppisar(a)redhat.com,
psabata(a)redhat.com
Classification: Fedora
abrt 1.1.1 detected a crash.
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/perl /usr/bin/padre
component: perl-Padre
executable: /usr/bin/perl
global_uuid: 1c0f880ad9686d02efbd3096ee944822c284105a
kernel: 2.6.33.5-112.fc13.x86_64
package: perl-Padre-0.50-4.fc13
rating: 3
reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
-----
1.closed padre through the gnome-terminal
2.
3.
--
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: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=598989
Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process
/usr/bin/perl was killed by signal 11 (SIGSEGV)
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:70e28391c1a250dd6698df00e84aff62011f8668
Severity: medium
Priority: low
Component: perl-Padre
AssignedTo: mmaslano(a)redhat.com
ReportedBy: rob+redhat(a)pangalactic.org
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
mmaslano(a)redhat.com, ppisar(a)redhat.com
Classification: Fedora
abrt 1.1.0 detected a crash.
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/perl /usr/bin/padre
comment: See "How to reproduce" for instructions. I verified this twice.
Problem does not occur when run locally.
component: perl-Padre
crash_function: _gdk_x11_screen_process_owner_change
executable: /usr/bin/perl
global_uuid: 70e28391c1a250dd6698df00e84aff62011f8668
kernel: 2.6.33.4-95.fc13.x86_64
package: perl-Padre-0.50-4.fc13
rating: 4
reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
-----
1. Start Hummingbird Exceed 12.0.0.124 on a Windows XP system
2. SSH into a Fedora 13 system with X11 tunnelling enabled using PuTTY
3. Start padre, loading a perl5 source file (e.g. "padre dbi-test.pl")
4. Select a module name such as "DBI" and press F2
--
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: AMAVISD_DB_HOME in amavisd-agent has wrong default
https://bugzilla.redhat.com/show_bug.cgi?id=574195
Summary: AMAVISD_DB_HOME in amavisd-agent has wrong default
Product: Fedora
Version: 12
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: amavisd-new
AssignedTo: steve(a)silug.org
ReportedBy: bugzilla_redhat(a)penguinpee.nl
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Created an attachment (id=400564)
--> (https://bugzilla.redhat.com/attachment.cgi?id=400564)
Fix default location of amavisd database
Description of problem:
AMAVISD_DB_HOME in amavisd-agent defaults to '/var/amavis/db' whereas the
package installs the database in '/var/spool/amavisd/db'. Thus, running
amavisd-agent will not produce the desired output.
Version-Release number of selected component (if applicable):
amavisd-new-2.6.4-1.fc12.noarch
How reproducible:
Always.
Steps to Reproduce:
1. run amavisd-agent
2.
3.
Actual results:
No snmp database /var/amavis/db/snmp.db; waiting...
Expected results:
Output of amavisd statistics
Additional info:
The attached patch will fix the problem. Setting AMAVISD_DB_HOME to the right
location will circumvent this problem.
--
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.