Github messages for voidlinux
 help / color / mirror / Atom feed
From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] python3-pyside2 build fails, requires qt5 patch
Date: Tue, 04 Jun 2024 01:40:34 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50673@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

New issue by zlice on void-packages repository

https://github.com/void-linux/void-packages/issues/50673

Description:
### Is this a new report?

Yes

### System Info

Void 6.9.0 x86_64 AuthenticAMD notuptodate rFFFFFFFFFFFFFF

### Package(s) Affected

python3-pyside2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270715

### Expected behaviour

python3-pyside2 builds

### Actual behaviour

Something along the lines of

```
DragMove
/usr/local/include/qt5/QtCore/qcoreevent.h:107:9: note: 'DragMove' declared here
        DragMove = 61,                          // drag moves in 
```



### Steps to reproduce

- `./xbps-src pkg python3-pyside2`

fix in link applies to `qt5`. after rebuilding qt and dependencies, this allowed pyside2 to build. not sure if there's a way to patch pyside2 instead, or need to revbump everything for qt5

[qtbase-5.15.9-work-around-pyside2-brokenness.txt](https://github.com/user-attachments/files/15540784/qtbase-5.15.9-work-around-pyside2-brokenness.txt)


             reply	other threads:[~2024-06-03 23:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 23:40 zlice [this message]
2024-06-04  0:07 ` classabbyamp
2024-06-04  0:11 ` zlice
2024-06-04  0:12 ` classabbyamp
2024-06-04  0:16 ` zlice
2024-06-04 19:41 ` zlice
2024-06-04 19:41 ` zlice
2024-06-05  6:15 ` [ISSUE] [CLOSED] " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50673@inbox.vuxu.org \
    --to=zlice@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).