[Bug 614982] New: non-responsive maintainer
by Red Hat Bugzilla
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.
12 years, 5 months
[Bug 660826] New: FTBFS perl-Class-DBI-AsForm-2.42-11.fc14
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: FTBFS perl-Class-DBI-AsForm-2.42-11.fc14
https://bugzilla.redhat.com/show_bug.cgi?id=660826
Summary: FTBFS perl-Class-DBI-AsForm-2.42-11.fc14
Product: Fedora
Version: rawhide
Platform: All
URL: http://linux.dell.com/files/fedora/FixBuildRequires/mo
ck-results/
OS/Version: Linux
Status: NEW
Keywords: Triaged
Severity: high
Priority: high
Component: perl-Class-DBI-AsForm
AssignedTo: tcallawa(a)redhat.com
ReportedBy: ftbfs(a)fedoraproject.org
QAContact: extras-qa(a)fedoraproject.org
CC: tcallawa(a)redhat.com, fedora-perl-devel-list(a)redhat.com
Blocks: 659965
Classification: Fedora
perl-Class-DBI-AsForm-2.42-11.fc14.src.rpm Failed To Build From Source against
the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more
information.
If you believe this is actually a bug in another package, do NOT change the
component in this bug or close this bug. Instead, add the appropriate bug
number from the other package to the "Depends on" line in this bug. If the
other package does not yet have a bug created that you think matches, please
create one. Doing so helps us properly track bugs and their dependencies, just
as we track package dependencies. (If you close this bug, and the other
package is not fixed before the next FTBFS run, a new bug will get created.
Please follow the above advice to avoid such duplication.)
--
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.
12 years, 6 months
[Bug 247253] New: Conflicting Provides
by Red Hat Bugzilla
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...
--
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.
12 years, 6 months
[Bug 450412] New: please build in EL-5
by Red Hat Bugzilla
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(a)redhat.com,fedora-perl-devel-
list@redhat.com,jlaska@redhat.com,poelstra(a)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.
12 years, 8 months
[Bug 637077] New: PID file location miss match
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: PID file location miss match
https://bugzilla.redhat.com/show_bug.cgi?id=637077
Summary: PID file location miss match
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: amavisd-new
AssignedTo: steve(a)silug.org
ReportedBy: tomo(a)appletz.jp
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com,
kanarip(a)kanarip.com
Classification: Fedora
Description of problem:
'/usr/share/clamav/clamd-wrapper' considers the place of the PID file to be
'/var/run/clamd.${CLAMD_SERVICE}/clamd.pid' if it isn't specified.
However, because '/etc/clamd.d/amavisd.conf' specifies
'var/run/amavisd/clamd.pid', so
it is necessary to be specified in '/etc/sysconfig/clamd.amavisd'.
--- SOURCES/amavis-clamd.sysconfig~ 2006-01-26 17:11:54.000000000 -0500
+++ SOURCES/amavis-clamd.sysconfig 2010-09-24 07:51:42.605828909 -0400
@@ -1,3 +1,4 @@
CLAMD_CONFIGFILE=/etc/clamd.d/amavisd.conf
CLAMD_SOCKET=/var/spool/amavisd/clamd.sock
+CLAMD_PIDFILE=/var/run/amavisd/clamd.pid
CLAMD_OPTIONS=
--
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.
12 years, 9 months
[Bug 603502] New: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla
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.
12 years, 10 months
[Bug 598989] New: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla
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.
12 years, 10 months
[Bug 574195] New: AMAVISD_DB_HOME in amavisd-agent has wrong default
by Red Hat Bugzilla
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.
12 years, 10 months
[Bug 616626] New: python-pip pkg conflict with perl-pip
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: python-pip pkg conflict with perl-pip
https://bugzilla.redhat.com/show_bug.cgi?id=616626
Summary: python-pip pkg conflict with perl-pip
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl-pip
AssignedTo: mmaslano(a)redhat.com
ReportedBy: astokes(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
mmaslano(a)redhat.com, phalliday(a)excelsiorsystems.net
Depends on: 616399
Classification: Fedora
Target Release: ---
Clone Of: 616399
+++ This bug was initially created as a clone of Bug #616399 +++
Description of problem:
Attempting to do a wildcard install of both python and perl packages results a
file conflict for both python-pip and perl-pip
Version-Release number of selected component (if applicable):
python-pip 0.6.3-1 & perl-pip 1.16-1
How reproducible:
100%
Steps to Reproduce:
1. yum install python* perl*
2.
3.
Actual results:
Running Transaction Test
Transaction Check Error:
file /usr/bin/pip conflicts between attempted installs of
python-pip-0.6.3-1.fc13.noarch and perl-pip-1.16-1.fc13.noarch
Expected results:
No conflicts
Additional info:
--- Additional comment from phalliday(a)excelsiorsystems.net on 2010-07-20
14:26:35 EDT ---
Well, I think the Debian approach
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551926) should be done here.
Both packages should have to rename their /usr/bin/pip. Something like
/usr/bin/pip-perl and /usr/bin/pip-python. That way completion will work at
least.
--
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.
12 years, 10 months