pool/virtualbox
SHA256
17
0
Fork 2
Code Issues Pull Requests Activity

VirtualBox-python3.13.patch #1

New Issue
Closed
opened 2025-02-26 14:25:14 +01:00 by sergiomb · 10 comments
sergiomb commented 2025-02-26 14:25:14 +01:00
Copy Link

here is how I fix the support python3.13 I just replace python3.11 by python3.13 , is quick fix !
but fails to compile on Fedora because use of PyObject_AsCharBuffer(), PyObject_AsReadBuffer() and PyObject_AsWriteBuffer()

HTH

references:
https://bugzilla.redhat.com/show_bug.cgi?id=1927146
https://docs.python.org/3.12/c-api/objbuffer.html
https://github.com/protocolbuffers/protobuf/pull/8339/files

here is how I fix the support python3.13 I just replace python3.11 by python3.13 , is quick fix ! but fails to compile on Fedora because use of PyObject_AsCharBuffer(), PyObject_AsReadBuffer() and PyObject_AsWriteBuffer() HTH references: https://bugzilla.redhat.com/show_bug.cgi?id=1927146 https://docs.python.org/3.12/c-api/objbuffer.html https://github.com/protocolbuffers/protobuf/pull/8339/files
VirtualBox-python3.13.patch
3.5 KiB
sergiomb commented 2025-02-26 14:27:18 +01:00
Author
Copy Link

@jengelh and @dgarcia ^

@jengelh and @dgarcia ^
dgarcia commented 2025-02-26 14:40:14 +01:00
Copy Link

@sergiomb yes, I started to try to build for python 3.13 but at some point the patch was getting bigger and bigger, so I decided to do not spent more time on this and wait for upstream to do it.

@sergiomb yes, I started to try to build for python 3.13 but at some point the patch was getting bigger and bigger, so I decided to do not spent more time on this and wait for upstream to do it.
python313.patch
8.9 KiB
jengelh commented 2025-03-31 12:56:53 +02:00
Copy Link

So with both patches being effectively incomplete, I don't see any action here. (I also cannot close the report because it was opened for the wrong git repo…)

So with both patches being effectively incomplete, I don't see any action here. (I also cannot close the report because it was opened for the wrong git repo…)
sergiomb commented 2025-03-31 14:45:17 +02:00
Author
Copy Link

what is the correct git repo ? , just now I notice dgarcia patch have some parts that are new

what is the correct git repo ? , just now I notice dgarcia patch have some parts that are new
jengelh commented 2025-03-31 14:55:10 +02:00
Copy Link
$ osc meta pkg openSUSE:Factory/virtualbox
<package name="virtualbox" project="openSUSE:Factory">
  <title>VirtualBox is an Emulator</title>
  <description></description>
  <devel project="Virtualization" package="virtualbox"/>
</package>

$ osc meta pkg Virtualization/virtualbox
<package name="virtualbox" project="Virtualization">
  <title/>
  <description/>
  <scmsync>https://src.opensuse.org/jengelh/virtualbox#master</scmsync>    <---
  <person userid="jengelh" role="maintainer"/>
  <debuginfo>
    <enable/>
  </debuginfo>
</package>
``` $ osc meta pkg openSUSE:Factory/virtualbox <package name="virtualbox" project="openSUSE:Factory"> <title>VirtualBox is an Emulator</title> <description></description> <devel project="Virtualization" package="virtualbox"/> </package> $ osc meta pkg Virtualization/virtualbox <package name="virtualbox" project="Virtualization"> <title/> <description/> <scmsync>https://src.opensuse.org/jengelh/virtualbox#master</scmsync> <--- <person userid="jengelh" role="maintainer"/> <debuginfo> <enable/> </debuginfo> </package> ```
sergiomb commented 2025-03-31 15:06:43 +02:00
Author
Copy Link

Hi,
https://src.opensuse.org/jengelh/virtualbox , don't have issues tab !
I'm Fedora/RPMFusion packager , I'd like work together with you to build better packages and to all test the same sources etc
I see you finally update Vbox to 7.1.6

Hi, https://src.opensuse.org/jengelh/virtualbox , don't have issues tab ! I'm Fedora/RPMFusion packager , I'd like work together with you to build better packages and to all test the same sources etc I see you finally update Vbox to 7.1.6
jengelh commented 2025-04-01 12:12:54 +02:00
Copy Link

Indeed the issues tab is not configured by default for any gitea project, but it is for /pool. That seems inside out IMO.

31/16:19 < adamm> issue tracker is enabled in Gitea in devel projects {{unverifiable}}. This may be a better place for TW bugs than Factory to be honest. I haven't tried to see the integration with Bugzilla as we do not track packages there very well at all. As for pool issue tracker, we'll have to discuss that a later. For official bugs, we still need Bugzilla... and we don't use /pool yet for anything.

In other words, the jury is still out and Bugzilla is best because /pool "isn't used yet for anything".

Indeed the issues tab is not configured by default for any gitea project, but it is for /pool. That seems inside out IMO. 31/16:19 < adamm> issue tracker is enabled in Gitea in devel projects {{unverifiable}}. This may be a better place for TW bugs than Factory to be honest. I haven't tried to see the integration with Bugzilla as we do not track packages there very well at all. As for pool issue tracker, we'll have to discuss that a later. For official bugs, we still need Bugzilla... and we don't use /pool yet for anything. In other words, the jury is still out and Bugzilla is best because /pool "isn't used yet for anything".
adamm commented 2025-04-01 12:14:20 +02:00
Copy Link

I wouldn't say jury is still out -- I would say situation is fluid 😆

I wouldn't say jury is still out -- I would say situation is fluid 😆
jengelh commented 2025-04-01 12:25:45 +02:00
Copy Link

it's a pretty a non-newtonian fluid tho 🥴

it's a pretty a non-newtonian fluid tho 🥴
😆 1
dirkmueller commented 2025-04-02 09:56:15 +02:00
Owner
Copy Link

I also cannot close the report because it was opened for the wrong git repo…

@jengelh you have permissions to close the issue but not permissions to write the repository. can you confirm?

> I also cannot close the report because it was opened for the wrong git repo… @jengelh you have permissions to close the issue but not permissions to write the repository. can you confirm?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
legaldb
Critical Priority
Critical legaldb priority
Archived
legaldb
High Priority
2
High legaldb priority
legaldb
Normal Priority
1
Normal legaldb priority
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
adamm_super adrianSuSE autobuild-owner autobuild-review autogits_workflow_pr_bot bigironman dirkmueller eroca factory_bot gitea_test legaldb lkocman-factory maxlin_factory opensuse-review packagehub-review smithfarm
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pool/virtualbox#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?