Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downstream changes needed to build version 3.11.1 #9881

Open
1 task done
theamericanaccount opened this issue Nov 14, 2024 · 2 comments
Open
1 task done

Downstream changes needed to build version 3.11.1 #9881

theamericanaccount opened this issue Nov 14, 2024 · 2 comments
Labels

Comments

@theamericanaccount
Copy link

theamericanaccount commented Nov 14, 2024

Describe the bug

Hello,
Im currently building live latest version of aiohttp for Life / DogeOS and I think there's a path finding issue in the file gen.py.
I'm currently fixing the build downstream on the ur.

To Reproduce

I'm using the aforementioned ur build recipe. Exact details of the commands run are provided in that source andfurther details can be examined on stream.

Expected behavior

Well it should build.

Logs/tracebacks

I'll probably post them if it keeps failing.

Python Version

I'm using Python 3.12.

aiohttp Version

I'm building aiohttp 3.11.1

multidict Version

I'm using multidict 6.0.5

propcache Version

0.2.0

yarl Version

I'm using yarl 1.9.4

OS

Life / DogeOS

Related component

tools/gen.py

Additional context

No response

Code of Conduct

  • I agree to follow the aio-libs Code of Conduct
@theamericanaccount theamericanaccount changed the title Downstream changeneeded to build version released a couple hours ago Downstream changes needed to build version 3.11.1 Nov 14, 2024
@theamericanaccount
Copy link
Author

theamericanaccount commented Nov 14, 2024

Well, I've written the recipe for propcache, packaged it and added it as an optional dependency for aiohttp.
Version 3.11.1 builds on Life / DogeOS (GNU) and Life / DogeOS (Android) with those seds btw.

I'm sorry if I've not opened a merge request for upstream but I don't have time.

@Dreamsorcerer
Copy link
Member

with those seds

What ones? You've not actually explained the problem and just created a bunch of links to your repositories and tweets...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants