iTunes/iTunes.Wine
Watch
1
0
Fork
You've already forked iTunes.Wine
 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Build × Wine grid: which iTunes build installs, launches and renders #4

New issue
Closed
opened 2026-10-28 09:58:06 +01:00 by The_Void · 0 comments
The_Void commented 2026-10-28 09:58:06 +01:00
Owner
Copy link

This settles which build for #1, by running each candidate rather than trusting the 2016–2020 bug reports. Those report 64-bit 12.x crashes during install or at startup (WineHQ 46719, 42878) and a black UI from 12.9.4 on.

For each installer × Wine (stable, then staging only where stable fails), in a fresh prefix:

  1. Does it install? Run the bundled setup first; if it fails, the individual MSIs via msiexec.
  2. Does it launch?
  3. Does the main window render, judged from a screenshot?
  4. Note the winetricks verbs, DLL overrides and Windows version needed.

Record each cell in KNOWLEDGE.md with its tier, build and Wine version, with the screenshot as the control. If a cell needs a fix that is more than a setting, file it as its own issue.

Done when KNOWLEDGE.md names one build + Wine pair that installs and renders, and the setup that reproduces it.

This settles *which build* for #1, by running each candidate rather than trusting the 2016–2020 bug reports. Those report 64-bit 12.x crashes during install or at startup (WineHQ 46719, 42878) and a black UI from 12.9.4 on. For each installer × Wine (stable, then staging only where stable fails), in a fresh prefix: 1. Does it install? Run the bundled setup first; if it fails, the individual MSIs via `msiexec`. 2. Does it launch? 3. Does the main window render, judged from a screenshot? 4. Note the winetricks verbs, DLL overrides and Windows version needed. Record each cell in `KNOWLEDGE.md` with its tier, build and Wine version, with the screenshot as the control. If a cell needs a fix that is more than a setting, file it as its own issue. Done when `KNOWLEDGE.md` names one build + Wine pair that installs and renders, and the setup that reproduces it.
The_Void added this to the Blocked milestone 2026-10-28 09:58:13 +01:00
The_Void modified the milestone from Blocked to Ready to work 2026-10-28 10:19:49 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug
An actual problem found in the code or the data

  
Claude
Filed by Claude

  
deferred
Intentionally parked - not on the critical path. Do not work unless asked

  
enhancement
An improvement to something that already works

  
epic
Tracking issue - closes only when its children do. Body indexes them

  
implementation
New implementation - a tool, script or feature that does not exist yet

  
priority/high
Do first among unblocked issues

  
priority/low
Nice to have; defer

  
priority/med
Normal priority

  
research
Reverse-engineering / an open question; 'confirmed unknown' is a legitimate outcome

  
verification
Needs a run against the real consumer - a structural check cannot close it

No labels
bug
Claude
deferred
enhancement
epic
implementation
priority/high
priority/low
priority/med
research
verification
Milestone
Clear milestone
No items
No milestone
Ready to work
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#1 Settle the target: iTunes build, Wine source and the features that must work
iTunes/iTunes.Wine
#6 Library and playback: add own MP3s from a mounted folder and play them
iTunes/iTunes.Wine
#8 Local bridge: socat 127.0.0.1:27015 to the desktop's usbmuxd, as a systemd user unit
iTunes/iTunes.Wine
Depends on
#2 Wine Docker image with Xvfb and a launch-and-screenshot script
iTunes/iTunes.Wine
#3 Fetch candidate iTunes installers into resources/ with source and sha1
iTunes/iTunes.Wine
Reference
iTunes/iTunes.Wine#4
No description provided.