+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone Pro (https://forum.pine64.org/forumdisplay.php?fid=177)
+--- Forum: PinePhone Pro Software (https://forum.pine64.org/forumdisplay.php?fid=179)
+--- Thread: bookworm vs trixie discussion for mobian in pinephone pro. (/showthread.php?tid=18839)
Pages:
1
2
RE: bookworm vs trixie discussion for mobian in pinephone pro. - mburns - 04-23-2024
(02-20-2024, 12:40 PM)mburns Wrote:(11-18-2023, 07:58 AM)mburns Wrote: The Camera and Megapixel apps in Trixie are not working. So, I copied the Megapixel files and my customizations from an older installation of Mobian.
The Tootle app is no longer in the repositories, so I copied the files from an older installation and then did a schema compile to get the app working. The desktop file needs a complete pointer to the location of the icon.
A capabilities problem with the Bubblewrap package prevents the Web app from starting. There is also an incompatibility of Mobian setup with Google Accounts that can prevent the Web app from starting. The app can be started from the command line, though; epiphany-browser is the executable name.
Someone could comment on getting the PinePhone Keyboard working in Trixie. But a Bluetooth mouse and keyboard work in Trixie.
The Web application is now working in Trixie Mobian, but not with Google approval.
Drivers for the cameras, or their invocation, have been dropped in the most recent update of Trixie Mobian. I am not sure if restoring the specific PinePhone Pro support package will work for this issue.
Support for the camera has been restored in Mobian Trixie as of Tuesday, April 23. But only the older version of megapixels that I saved works.
RE: bookworm vs trixie discussion for mobian in pinephone pro. - mburns - 04-25-2024
(04-23-2024, 07:34 AM)mburns Wrote:(02-20-2024, 12:40 PM)mburns Wrote:(11-18-2023, 07:58 AM)mburns Wrote: The Camera and Megapixel apps in Trixie are not working. So, I copied the Megapixel files and my customizations from an older installation of Mobian.
The Tootle app is no longer in the repositories, so I copied the files from an older installation and then did a schema compile to get the app working. The desktop file needs a complete pointer to the location of the icon.
A capabilities problem with the Bubblewrap package prevents the Web app from starting. There is also an incompatibility of Mobian setup with Google Accounts that can prevent the Web app from starting. The app can be started from the command line, though; epiphany-browser is the executable name.
Someone could comment on getting the PinePhone Keyboard working in Trixie. But a Bluetooth mouse and keyboard work in Trixie.
The Web application is now working in Trixie Mobian, but not with Google approval.
Drivers for the cameras, or their invocation, have been dropped in the most recent update of Trixie Mobian. I am not sure if restoring the specific PinePhone Pro support package will work for this issue.
Support for the camera has been restored in Mobian Trixie as of Tuesday, April 23. But only the older version of megapixels that I saved works.
On Thursday, April 25, there is a dangerous dist-upgrade available for Mobian Trixie. Don't do it!
RE: bookworm vs trixie discussion for mobian in pinephone pro. - zetabeta - 04-25-2024
(04-25-2024, 12:24 PM)mburns Wrote: On Thursday, April 25, there is a dangerous dist-upgrade available for Mobian Trixie. Don't do it!
it seems that it is related to t64 transition, and it is a mess.
https://micronews.debian.org/2024/1709031141.html
i updated mobian on pinephone regular, and it seems that t64 packages has started to roll down into testing/trixie. well, trixie is more or less unstable anyway, but this is more complicated mess. i don't have any good advises beyond manually selecting t64 packages.
i already have experience of this mess, because i updated unstable debian somewhat recently on one of my x86-64 machines.
RE: bookworm vs trixie discussion for mobian in pinephone pro. - Kevin Kofler - 04-26-2024
The 64-bit time_t transition should be entirely irrelevant for 64-bit platforms such as aarch64, time_t has always been 64-bit on 64-bit platforms.
RE: bookworm vs trixie discussion for mobian in pinephone pro. - diederik - 04-26-2024
(04-26-2024, 03:44 AM)Kevin Kofler Wrote: The 64-bit time_t transition should be entirely irrelevant for 64-bit platforms such as aarch64, time_t has always been 64-bit on 64-bit platforms.
It would be unwise to underestimate the impact on ANY platform, including all 64-bit platforms.
This is likely the biggest transition I've seen in my ~15 years of using Debian.
Do NOT underestimate its impact.
Some tips:
- Do NOT use full-/dist-upgrade. People should generally not use it, but that's especially true now
- Waiting is a virtue. Forcing things (which is what full-upgrade does) is generally a bad idea. Even more now. All the issues will be fixed/resolved over time.
- Do NOT use the '-y' parameter to apt and READ all that APT is telling you it's about to do. Responding 'N(o)' has always been a valid response and even more now.
HTH
RE: bookworm vs trixie discussion for mobian in pinephone pro. - Kevin Kofler - 04-27-2024
Then the Debian packaging is really messed up, because the transition is clearly a no-op on 64-bit platforms and should be (but apparently is not) treated as such.
RE: bookworm vs trixie discussion for mobian in pinephone pro. - diederik - 04-28-2024
(04-26-2024, 05:40 AM)diederik Wrote: Some tips:
- Do NOT use full-/dist-upgrade. People should generally not use it, but that's especially true now
- Waiting is a virtue. Forcing things (which is what full-upgrade does) is generally a bad idea. Even more now. All the issues will be fixed/resolved over time.
- Do NOT use the '-y' parameter to apt and READ all that APT is telling you it's about to do. Responding 'N(o)' has always been a valid response and even more now.
It turns out that with "apt" you actually do need to use dist-upgrade to remove packages so they can be replaced with their time64/t64 successor.
source: the Debian apt maintainer and they should know
That's apparently one of the differences with aptitude, which is what I always use, which just removes packages that are no longer needed or are replaced by another package.