Bug 2480875

Summary: perl-WWW-RobotRules-6.03 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: perl-WWW-RobotRulesAssignee: Michal Josef Spacek <mspacek>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mspacek, perl-devel, ppisar
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-WWW-RobotRules-6.03-2.fc45 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-09 15:50:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 6.03 (#2480875) none

Description Upstream Release Monitoring 2026-05-23 04:50:43 UTC 
Releases retrieved: 6.03
Upstream release that is considered latest: 6.03
Current version/release in rawhide: 6.02-43.fc44
URL: http://search.cpan.org/dist/WWW-RobotRules/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/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.


Based on the information from Anitya: https://release-monitoring.org/project/3506/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-WWW-RobotRules
Comment 1 Upstream Release Monitoring 2026-05-23 04:50:47 UTC 
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-e06uke9q/perl-WWW-RobotRules.spec']' returned non-zero exit status 1.

StdOut:
Building target platforms: noarch
Building for target noarch
setting SOURCE_DATE_EPOCH=1779494400
error: Bad file: WWW-RobotRules-6.03.tar.gz: No such file or directory

RPM build errors:
    Bad file: WWW-RobotRules-6.03.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.14/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 55, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.14/site-packages/hotness/builders/koji.py", line 251, in build
    raise BuilderException(
        str(exc), value=output, std_out=std_out, std_err=std_err
    )

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Comment 2 Upstream Release Monitoring 2026-05-23 04:50:49 UTC 
Created attachment 2142424 [details]
Update to 6.03 (#2480875)
Comment 3 Michal Josef Spacek 2026-06-02 14:33:34 UTC 
Changes:

6.03      2026-05-23 02:23:28Z
    - Doing a proper version bump.


For rawhide, F44 and F43
Comment 4 Michal Josef Spacek 2026-06-05 11:07:14 UTC 
There was accidental change from 6.02 to 6.02:

6.02      2026-05-21 14:45:27Z
    - WWW::RobotRules::AnyDBM_File::agent() no longer truncates the on-disk
      cache through an untie/tie(O_TRUNC) sequence. Stale-data reset now goes
      through the tied-hash CLEAR, eliminating a symlink-follow race that a
      local attacker with write access to the cache directory could exploit
      to overwrite arbitrary files writable by the crawler user.
    - The on-disk cache file mode has been tightened from 0640 to 0600.
    - t/rules-dbm.t has been hardened against symlink attacks on its tempfile
      during package builds.
    - A new SECURITY CONSIDERATIONS POD section documents the residual
      caller-trust requirement: the constructor's tie still follows symlinks
      because AnyDBM_File cannot portably plumb O_NOFOLLOW, so the caller
      must store the cache file in a directory writable only by the user
      that runs the code.
    - References: CWE-377, CWE-378, CWE-379.
Comment 5 Michal Josef Spacek 2026-06-09 14:25:20 UTC 
Many changes in module, only for Fedora Rawhide.