-
Notifications
You must be signed in to change notification settings - Fork 58
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
Python package version conflicts #267
Comments
Last time I checked we use 4 python versions. |
Looks like installing LMMS installed a newer Python version but this did not trigger all Python packages to be also updated at the same time? Is this a conceptual problem with how FreeBSD packages work? In Debian, when you update Python to a version that requires other packages to be updated as well, it would also update those packages. At least if I am not mistaken. How could we solve this? |
My first reaction to the error was to 'sudo pkg update'
But the response to this was 'pkg update is not yet supported in
helloSystem'
Could that also be blocking any auto-updating?
…On Mon, Aug 2, 2021 at 4:28 PM probonopd ***@***.***> wrote:
Looks like installing LMMS installed a newer Python version but this did
not trigger all Python packages to be also updated at the same time?
Is this a conceptual problem with how FreeBSD packages work?
In Debian, when you update Python to a version that requires other
packages to be updated as well, it would also update those packages. At
least if I am not mistaken.
How could we solve this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#267 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4VZWCS5AI73BW4OSKDT235XDANCNFSM5BLRPPVA>
.
--
Bruce Davidson
|
sudo pkg.real update but it screws with helloSystem components. |
Yes. All that updating stuff can screw with the system in unexpected ways, like producing version conflicts. This ticket is a proof of it. It seems like installing an application in FreeBSD can cause it to update packages that in ways that render other applications non-functioning, without updating those other packages as well. Coming from Debian and Ubuntu, I am not used to this. I don't know yet how to handle this better. Any help from more experienced FreeBSD users and/or developers is appreciated. |
I understand – you are pre-alpha. It just doesn’t seem like it most of the
time. I have another laptop that I use.
I’ve experienced a lot of breakage in the past using the FreeBSD repo. They
seem a bit antagonistic toward desktop users – for example they’ve also now
removed VSCode. To me, that is the main advantage to using GhostBSD, the
repo is desktop friendly.
…On Tue, Aug 10, 2021 at 9:40 AM probonopd ***@***.***> wrote:
Yes. All that updating stuff can screw with the system in unexpected ways,
like producing version conflicts. This ticket is a proof of it. I don't
know yet how to handle this better.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#267 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4TUJGDCONP34UFDFNDT4ET6NANCNFSM5BLRPPVA>
.
--
Bruce Davidson
|
False.
|
Not in my experience. Edge cases may exist, but they're rare. |
Thanks for clarifying that. I was using pkg install, which still works in
GhostBSD. The last time I tried building vscode from ports, it took over
24 hrs to build...
…On Sat, Aug 21, 2021 at 11:11 AM Graham Perrin ***@***.***> wrote:
removed VSCode.
False.
% file /usr/ports/editors/vscode
/usr/ports/editors/vscode: directory
% grep vscode /usr/ports/MOVED
%
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#267 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4URIR7ZGDQUITUDHDDT57T3HANCNFSM5BLRPPVA>
.
--
Bruce Davidson
|
ports-mgmt/poudriere-devel is our friend. Use option Without using poudriere: |
See #51 (comment); if the essence of helloSystem can be ported (and ideally packaged) then, in the context of a repo, it should be easier to identify and fix dependency-related issues. |
I installed poudriere:
I'm guessing I don't use a jail for this, so the dependencies will save to my installation?
But I get: Illegal option -b It appears that option is added in version 3.4, but the version in freshports is still 3.3.7. So I guess I'll just wait :) |
This comment has been minimized.
This comment has been minimized.
Doh! I must be getting blind. Thanks, I now have the correct version of poudriere installed. I'll play around with that. I reinstalled helloSystem, and I went ahead and ran pkg.real upgrade. This fixed Falkon and my other issues, but now these are not working (more of an FYI - they are lower importance to me): Remote Assistance More annoying is the rounded corners are now all square :( But I can live with that, too. |
Some, not all, may be fixed as suggested at #267 (comment) |
I instaled That fixed some of them. These are still broken: Zeroconf, StartDisk, Keyboard, Mouse
SimpleBrowser
|
This comment has been minimized.
This comment has been minimized.
As far as I can tell, none of those provides what's required by the affected applications. |
I added py38-qt5-webengine, this fixed the Simple Browser example. #!/usr/bin/env python3.7 fixed it. That just leaves square corners, which sounds like a configuration setting. |
Shouldn't we update
I wish Python version numbers were not hardcoded in package names... Besides, I thought this would have fixed that issue: |
Argh! I think I shot myself into the foot badly on my main system (FreeBSD 12.2-RELEASE based helloSystem development system roughly equiavlent to 0.6, installed to disk). Just wanted to install the Calibre application: As a result:
When I now want to launch any PyQt app, including Calibre:
So apparently "the system" decided to use Python 3.8 instead of Python 3.7. But it failed at doing this entirely worry-free. In fact, this is guaranteed to give a lot of trouble if the package manager uninstalls the Python extensions for 3.7 and installs those for 3.8 but leaves Python 3.7 the default:
Really dissatisfying. I don't know how to make my system "work" again... I can see hours and hours go to Manually doing
made at least some applications work again, and made Calibre run in the first place. But then there are things like
which apparently still tries to use the now module-less This is what I mean with "updates can break the System". It should be fixed. |
Also getting
Is If not, what makes it so?
|
Not that I can see. No mention of 37: |
@linuxkettle wrote:
I don't see this. Please provide steps to reproduce. |
Success:
Which ports? |
Strange. So possibly 0.6.0 already fixes this by specifying the package names for some Python packages differently (using the port name rather than the package name because the former does not encode the minor version, other than the latter). |
No such direct result here (with quarterly packages and an outdated base operating system):
I tried changing from quarterly to latest before an installation of Calibre. Again, the results do not include an upgrade to LibreOffice:
|
The issue I've had with updating Firefox I will describe in more detail. I have been updating Firefox with
This time, in the list of packages to be removed, was an i10n package qt depends on, Inkscape, krita, and a few core qt packages. Now, I can't launch any qt apps without shared library dependency errors. I also, on my computer, can't install any helloSystem not built on 13.0-RELEASE for missing drivers. |
Which version of helloSystem? Which version of FreeBSD?
Which repository?
Which one, for example?
Have you installed the five packages suggested above? |
https://github.com/search?q=org%3AhelloSystem+author%3Alinuxkettle+is%3Aissue&type=issues I can't find a matching issue. @linuxkettle please, did someone else raise the issue? Or is it a non-issue in the context of #198? |
I can't find StartDisk.
@darkoverlordofdata I can't find SimpleBrowser or Simple Browser at the command line, or in FreshPorts. Can you provide a link?
Without updating any header, various helloSystem applications work after:
Are the rounded corners below not as rounded as they should be? |
I don't understand the rationale for minimise buttons on modal error dialogs. |
Me neither. Do you know how to get rid of them? |
Do you mean the Error window above? It's not modal. |
Ah, well it's still an error dialog, you're unlikely to want to minimise it. |
I normally set aside an error dialogue whilst preparing to copy its content (to a bug report or whatever). This setting aside is sometimes a drag of the window but more often, I'll minimise. |
@darkoverlordofdata please, does there remain any unresolved conflict? |
There are no unresolved conflicts. Thanks!
…On Sun, Sep 26, 2021, 4:04 AM Graham Perrin ***@***.***> wrote:
Python package version conflicts
@darkoverlordofdata <https://github.com/darkoverlordofdata> please, does
there remain any unresolved conflict?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#267 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4XHFFEDQ3WANQYTNI3UD343XANCNFSM5BLRPPVA>
.
|
Close? Thanks. |
Please comment here in case the problem persists. Thanks! |
Describe the bug
python 37 conflicting with python 38
To Reproduce
Steps to reproduce the behavior:
sudo pkg install elementary-code
Expected behavioro
it should install
Screenshots
Version (please complete the following information):
cat /.url
): https://github.com/helloSystem/ISO/releases/tag/r0.5.0Computer (please complete the following information):
Additional context
It was working fine when I first installed maybe a month ago. Last week, I had to reinstall, and it seems like the FreeBSD repo has changed; VSCode is no longer available, and I got a new version of Chromium (which also broke rounded corners on windows). When I try to install apps wirh python dependencies, I get a version conflict, it is trying to isntall python38 dependencies, but the system is using python37. I think it's become out of sync with the repo.
The text was updated successfully, but these errors were encountered: