Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2219991 - F39FailsToInstall: fail2ban-server, fail2ban-tests
Summary: F39FailsToInstall: fail2ban-server, fail2ban-tests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fail2ban
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
: 2176186 (view as bug list)
Depends On:
Blocks: F39FailsToInstall PYTHON3.12 F39FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2023-07-05 19:04 UTC by Fedora Fails To Install
Modified: 2023-10-10 02:32 UTC (History)
9 users (show)

Fixed In Version: fail2ban-1.0.2-9.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-05 21:15:15 UTC
Type: ---
Embargoed:
hobbes1069: needinfo+
hobbes1069: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources fail2ban pull-request 9 0 None None None 2023-09-27 18:23:11 UTC
Github fail2ban fail2ban issues 3487 0 None open [BR]: Fails to build with Python 3.12 - ModuleNotFoundError: No module named 'asynchat' 2023-07-15 14:08:50 UTC

Description Fedora Fails To Install 2023-07-05 19:04:04 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

Your package (fail2ban) Fails To Install in Fedora 39:

can't install fail2ban-server:
  - nothing provides python(abi) = 3.11 needed by fail2ban-server-1.0.2-5.fc39.noarch
  
can't install fail2ban-tests:
  - nothing provides python(abi) = 3.11 needed by fail2ban-tests-1.0.2-5.fc39.noarch
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-39-x86_64 --config-opts mirrored=False install fail2ban-server fail2ban-tests


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!
Comment 1 Fedora Fails To Install 2023-07-13 11:39:47 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 7+ weeks.
This is the first reminder (step 3) from the policy.

Don't hesitate to ask for help on devel.org if you are unsure how to fix this bug.
Comment 2 Orion Poplawski 2023-07-15 14:08:51 UTC 
Reported upstream.  This is going to take a while to fix.
Comment 3 Fedora Release Engineering 2023-08-16 07:15:47 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.
Comment 4 Miro Hrončok 2023-09-21 07:58:15 UTC 
Orion, Richard,

is it probable that this will be fixed (or worked around) for the time of Fedora 39 final freeze? If not, would you consider retiring the package and reintroducing it later?
Comment 5 Miro Hrončok 2023-09-21 07:59:18 UTC 
*** Bug 2176186 has been marked as a duplicate of this bug. ***
Comment 6 Adam Williamson 2023-09-27 16:21:31 UTC 
Would it be viable to just vendor the old async stuff into the package until upstream manages to rewrite it?
Comment 7 Adam Williamson 2023-09-27 16:22:06 UTC 
POST is inaccurate status here, we use POST to mean a *fix* is available upstream, not just that it's *reported* upstream.
Comment 8 Miro Hrončok 2023-09-27 16:24:07 UTC 
Note that https://pypi.org/project/pyasynchat/ and https://pypi.org/project/pyasyncore/ exist. They can be packaged and used as dependencies.
Comment 9 Miro Hrončok 2023-09-27 16:29:26 UTC 
For completeness, I've proposed that in the upstream issue as well.
Comment 10 Adam Williamson 2023-09-27 16:50:05 UTC 
Yeah, that's an option too. vendoring directly is quicker and avoids a couple of package reviews, but if we have any other cases where we might want to do it, that might be a better way.

On a quick try, vendoring them directly into fail2ban works, but there are two other issues remaining: a test case that uses smtpd (also removed in Python 3.12) and a database repair test that fails (not sure why yet). I'm working on those.
Comment 11 Adam Williamson 2023-09-27 18:23:12 UTC 
https://src.fedoraproject.org/rpms/fail2ban/pull-request/9 gets it building, at least, with some ugliness (vendoring asyncore and asynchat directly, disabling some tests that I can't practically fix quickly - if anyone else is a dab hand with aiosmtpd or can figure out a precision-targeted way to corrupt the database file, please go for it)
Comment 12 Fedora Update System 2023-09-29 23:27:28 UTC 
FEDORA-2023-e36c5fb76b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e36c5fb76b
Comment 13 Fedora Update System 2023-09-30 03:31:34 UTC 
FEDORA-2023-e36c5fb76b has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e36c5fb76b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e36c5fb76b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 14 Fedora Fails To Install 2023-09-30 17:34:14 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 40.

Thanks for taking care of it!
Comment 15 Adam Williamson 2023-10-04 16:53:11 UTC 
+3 in https://pagure.io/fedora-qa/blocker-review/issue/1360 , marking accepted.
Comment 16 Fedora Update System 2023-10-05 21:15:15 UTC 
FEDORA-2023-e36c5fb76b has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.