Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65907 - [python-m2crypto] Missing backport

Attached to Project: Community Packages
Opened by Giovanni Santini (ItachiSan) - Friday, 20 March 2020, 17:55 GMT
Last edited by Morten Linderud (Foxboron) - Saturday, 06 June 2020, 14:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Morten Linderud (Foxboron)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
`osc`, a tool using `python-m2crypto`, fails without the necessary backport.
In order to properly work, the developer suggest a backport which is mentioned as `necessary` for Python 3.8.

Additional info:
* package version: 0.35.2-2
* tool bug report: https://github.com/openSUSE/osc/issues/771
* upstream merge request: https://gitlab.com/m2crypto/m2crypto/-/merge_requests/242

Steps to reproduce:
1. Install `osc` (via AUR or the OpenSUSE tools repository)
2. See the tool bug report
This task depends upon

Closed by  Morten Linderud (Foxboron)
Saturday, 06 June 2020, 14:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.35.2-3
Comment by Giovanni Santini (ItachiSan) - Thursday, 28 May 2020, 12:56 GMT
Any update for this?
Comment by Morten Linderud (Foxboron) - Thursday, 28 May 2020, 13:08 GMT
Have you tested a package with the applied upstream commit?

https://gitlab.com/m2crypto/m2crypto/-/commit/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a
Comment by Oleksandr Natalenko (post-factum) - Thursday, 28 May 2020, 13:10 GMT
I have tested it on 2 machines, and it works fine for me.
Comment by Morten Linderud (Foxboron) - Thursday, 28 May 2020, 13:12 GMT
Did you use the commit in the merge request or the rebased upstream commit?
Comment by Oleksandr Natalenko (post-factum) - Thursday, 28 May 2020, 13:18 GMT
I used [1].

[1] https://gitlab.com/m2crypto/m2crypto/-/commit/d3a43ffe1bfe4c128d6ab7c390419dee68f4ca5a
Comment by Giovanni Santini (ItachiSan) - Thursday, 28 May 2020, 13:32 GMT
I actually have applied the diff in [1] and it worked fine.

[1]: https://gitlab.com/m2crypto/m2crypto/-/merge_requests/242.diff
Comment by Morten Linderud (Foxboron) - Thursday, 28 May 2020, 13:34 GMT
We are not applying the unmerged diff. So check with the commited patch and verify if it works please.
Comment by Oleksandr Natalenko (post-factum) - Thursday, 28 May 2020, 13:36 GMT
FWIW, both are the same except of type annotation change.

Loading...