perl-devel November 2005

perl-devel@lists.fedoraproject.org

7 participants
70 discussions

Start a nNew thread

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 13 Nov '05

13 Nov '05

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 13 Nov '05

13 Nov '05

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 12 Nov '05

12 Nov '05

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From rc040203(a)freenet.de 2005-11-12 23:51 EST ------- (In reply to comment #5) > I think the bundling makes sense in this case. I could not disagree more. * Readonly-XS and Readonly are independent, there is no dependency between both. Actually, Readonly-XS is a sort of overlay plugin to Readonly * Readonly is noarch/Readonly-XS is arch'ed. Probs will occur, should Readonly-XS not be buildable on one particular architecture. * Splitting both makes the *specs much simpler and less error-prone. => There is no technically need to merge these perl-dists into one, therefore there is no need to make an exception from the FE packaging rules. -- 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.

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 12 Nov '05

12 Nov '05

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 12 Nov '05

12 Nov '05

1 0

[Bug 172998] New: spamassassin 3.0.4 DOS vulnerability
by Red Hat Bugzilla 11 Nov '05

11 Nov '05

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=172998 Summary: spamassassin 3.0.4 DOS vulnerability Product: Fedora Core Version: fc4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: spamassassin AssignedTo: wtogami(a)redhat.com ReportedBy: goemon(a)anime.net CC: fedora-perl-devel- list@redhat.com,felicity@kluge.net,jm@jmason.org,parkerm @pobox.com,reg+redhat@sidney.com,wtogami@redhat.com Description of problem: spamassassin 3.0.4 is vulnerable to DOS attacks. Version-Release number of selected component (if applicable): 3.0.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: http://secunia.com/advisories/17386/ http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4570 -- 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.

1 1

[Bug 113304] perl should not export -D_FILE_OFFSET_BITS=64
by Red Hat Bugzilla 10 Nov '05

10 Nov '05

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl should not export -D_FILE_OFFSET_BITS=64 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113304 jvdias(a)redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE Fixed In Version| |ALL ------- Additional Comments From jvdias(a)redhat.com 2005-11-10 14:13 EST ------- I believe this is no longer a problem - all current kernels fully support largefiles, and perl largefile support can be turned on / off by the '%define largefiles 1' (default 1) in the .spec files for all current perl releases - if I'm wrong, please let me know and re-open this bug - thanks. -- 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.

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 10 Nov '05

10 Nov '05

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters(a)mac.com 2005-11-10 13:47 EST ------- I'm going to contact my service provider and ask why access isn't working for some people. -=- With respect to splitting it - I can do that, but then perl-Readonly-XS will need to Require perl-Require because it is useless without perl-Readonly. However - perl-Readonly should also require perl-Readonly-XS because it gives perl-Readonly-XS a performance boost, and perl scripts that use perl-Readonly will not require perl-Readonly-XS by automatic dep resolution, so the only way to get perl-Readonly-XS pulled in with yum is to have perl-Readonly require it. Since the two modules will thus need to require each other, and are maintained by the same maintainer, and released in pair (new version of one means new version of other) - does it really make sense for them to be separate packages in this case? -- 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.

1 0

[Bug 172677] Review Request: perl-Readonly
by Red Hat Bugzilla 10 Nov '05

10 Nov '05

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From rc040203(a)freenet.de 2005-11-10 12:56 EST ------- I am still unable to access your site. Therefore only some comments on the spec file from the attachment: 1. FE's packaging policy recommends to ship one package per perl distribution, and I don't see many compelling reasons to make an exception in this case. I.e. I recommend to split this package into 2 packages: perl-Readonly and perl-Readonly-XS 2. Readonly wants to ship this file: /usr/lib/perl5/vendor_perl/5.8.6/benchmark.pl IMO, shipping a script of this name at this location should be avoided. I recommend to move it elsewhere (eg. %doc) or to remove it entirely. -- 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.

1 0

[Bug 161785] spamassassin restart fails - functions bug?
by Red Hat Bugzilla 10 Nov '05

10 Nov '05

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: spamassassin restart fails - functions bug? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161785 ------- Additional Comments From john.horne(a)plymouth.ac.uk 2005-11-10 09:50 EST ------- Re comment 8: I have installed onto one of our FC4 mailhubs spamassassin-3.0.4-2.fc4 from the fedora-updates repo. This seems to work fine; restarting spamassassin repeatedly using 'service spamassassin restart' worked every time. Previously this would have failed pretty much immediately. Many thanks. John. -- 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.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

perl-devel November 2005