Bug 31538

Summary: python-django-crispy-forms - Django DRY Forms
Product: Mageia Reporter: Kristoffer Grundström <lovaren>
Component: New RPM package requestAssignee: All Packagers <pkg-bugs>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Normal CC: marja11, python, yvesbrungard
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://github.com/maraujop/django-crispy-forms
Whiteboard:
Source RPM: python3-django-crispy-forms CVE:
Status comment:
Attachments: Proposal spec file

Description Kristoffer Grundström 2023-02-11 06:06:34 CET
Description of problem: In order to package the Weblate client to interact with the translations being done in the web UI I need python3-django-crispy-forms to be packaged for Mageia and here's my spec for it.

Version-Release number of selected component (if applicable): 1.14.0
Comment 1 Kristoffer Grundström 2023-02-11 06:07:20 CET
Created attachment 13692 [details]
Proposal spec file
Comment 2 Marja Van Waes 2023-02-11 22:32:00 CET
(In reply to Kristoffer Grundström from comment #1)
> Created attachment 13692 [details]
> Proposal spec file

Thanks.

Assigning to all packagers collectively, because we always do that with package requests. However, CC'ing our Python Stack maintainers.

URL: (none) => https://github.com/maraujop/django-crispy-forms
Severity: minor => enhancement
Assignee: bugsquad => pkg-bugs
Summary: {PKG REQUEST}python-django-crispy-forms - Django DRY Forms => python-django-crispy-forms - Django DRY Forms
CC: (none) => marja11, python

Comment 3 papoteur 2023-02-12 22:04:43 CET
Hello,
This proposed spec file doesn't help.
It uses directives not known in Mageia :
%{python_module django >= 2.2}
It doesn't use pyproject macros which are know our standard.
It's probably more direct to use pyp2spec command (in cauldron at the moment) to get a more adapted skeleton.

CC: (none) => yves.brungard_mageia