Νέα, αλλά σε Python 3.10:
2022-06-13-python3-10
Title Python 3.10 to become the default on 2022-07-01
Author Michał Górny <mgorny@gentoo.org>
Posted 2022-06-13
Revision 1
We are planning to switch the default Python target of Gentoo systems
on 2022-07-01, from Python 3.9 to Python 3.10. If you have not changed
the values of PYTHON_TARGETS or PYTHON_SINGLE_TARGET, the change will
have immediate effect on your system and the package manager will try
to switch automatically on the next upgrade following the change.
If you did change the values, prefer a safer approach or have problems
with the update, read on.
Please note that the default upgrade method switches packages to the new
Python versions as they are rebuilt. This means that all interdependent
packages have to support the new version for the upgrade to proceed,
and that some programs may temporarily fail to find their dependencies
throughout the upgrade (although programs that are already started
are unlikely to be affected).
If you have PYTHON_TARGETS or PYTHON_SINGLE_TARGET declared
in make.conf, please remove these declarations as they will interfere
with the package.use samples provided below. Using make.conf for Python
targets is discouraged as it prevents package defaults from applying
when necessary. This news item assumes using /etc/portage/package.use
or your package manager's equivalent file for configuration.
At this point, you have a few configuration options to choose from:
1. If you wish Python upgrades to apply automatically, you can remove
PYTHON_TARGETS and PYTHON_SINGLE_TARGET declarations. When
the defaults change, your package manager should handle the upgrade
automatically. However, you may still need to run the update
commands if any problems arise.
2. If you wish to defer the upgrade for the time being, you can
explicitly set the old values in package.use.
3. If you wish to force the upgrade earlier, you can explicitly set
the new values and run the upgrade commands.
4. If you wish to use a safer approach (i.e. less likely to temporarily
break packages during the upgrade), you can perform a multi-step
upgrade as outlined below.
5. Finally, you can use an arbitrary combination of PYTHON_TARGETS
and PYTHON_SINGLE_TARGET.
Deferring the upgrade
=====================
To defer the upgrade, explicitly set the old targets:
*/* PYTHON_TARGETS: -* python3_9
*/* PYTHON_SINGLE_TARGET: -* python3_9
This will enforce Python 3.9 and block any future updates. However,
please note that this is only a temporary solution and you will
eventually need to perform the migration.
Forcing the upgrade
===================
To force the upgrade earlier, explicitly select the Python 3.10 targets:
*/* PYTHON_TARGETS: -* python3_10
*/* PYTHON_SINGLE_TARGET: -* python3_10
However, it is important to remember to remove this after the defaults
change, as it will interfere with the automatic switch to the next
Python version in the future.
Safer upgrade procedure
=======================
A safer approach is to add Python 3.10 support to your system first,
and only then remove Python 3.9. However, note that this involves two
rebuilds of all the affected packages, so it will take noticeably
longer.
First, enable both Python 3.9 and Python 3.10, and then run the upgrade
commands:
*/* PYTHON_TARGETS: -* python3_9 python3_10
*/* PYTHON_SINGLE_TARGET: -* python3_9
Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades:
*/* PYTHON_TARGETS: -* python3_9 python3_10
*/* PYTHON_SINGLE_TARGET: -* python3_10
Finally, switch to the final version and upgrade:
*/* PYTHON_TARGETS: -* python3_10
*/* PYTHON_SINGLE_TARGET: -* python3_10
You may wish to remove the target overrides after the defaults switch.
Alternatively, you can keep them to block the next automatic upgrade
to Python 3.11, and upgrade manually then.
Upgrade commands
================
The Python 3.9 cleanup requires that Python 3.9 is removed from
the complete dependency trees in batch. If some of the
installed packages using an older Python version are not triaged
for the upgrade, the package manager will throw dependency conflicts.
This makes it important that the upgrade is carried via a --deep
--changed-use @world upgrade, as well as that any stray packages
are removed prior to it, e.g.:
emerge --depclean
emerge -1vUD @world
emerge --depclean
Εμφάνιση 6.871-6.885 από 7211
-
15-06-22, 19:47 Απάντηση: Το νήμα του Gentoo, version 1.0 #6871
-
15-06-22, 23:19 Re: Απάντηση: Το νήμα του Gentoo, version 1.0 #6872
-
16-06-22, 16:06 Απάντηση: Το νήμα του Gentoo, version 1.0 #6873
Εγώ το ίδιο και χειρότερα με το qt-webengine...
-
16-06-22, 22:49 Re: Απάντηση: Το νήμα του Gentoo, version 1.0 #6874
-
17-06-22, 17:19 Απάντηση: Το νήμα του Gentoo, version 1.0 #6875
Εγώ λέω να το παίξω τολμηρός και να το βάλω από τώρα. Έβαλα το
Κώδικας:*/* PYTHON_TARGETS: -* python3_10 */* PYTHON_SINGLE_TARGET: -* python3_10
-
17-06-22, 22:06 Απάντηση: Το νήμα του Gentoo, version 1.0 #6876
Πόσο χρόνο χρειάζεστε για το qt-webengine;
-
17-06-22, 22:30 Απάντηση: Το νήμα του Gentoo, version 1.0 #6877
Σε εμένα:
Κώδικας:Thu Apr 14 21:32:26 2022 >>> dev-qt/qtwebengine-5.15.3_p20220406 merge time: 1 hour, 43 minutes and 46 seconds. Fri Jun 10 22:07:10 2022 >>> dev-qt/qtwebengine-5.15.4_p20220526 merge time: 1 hour, 40 minutes and 37 seconds.
-
11-07-22, 13:49 Re: Το νήμα του Gentoo, version 1.0 #6878
Περιμένω εδώ και πόσο καιρό να περάσει στο stable branch η 5.25 του KDE.
Υπάρχει κάποιος τρόπος να μάθουμε πιθανή ημερομηνία;
Είμαι σε 5.23.5 και όλα δουλεύουν άψογα. Όταν είχα πάει σε 5.24, μ@μήθηκε το σύμπαν.
Είχα δοκιμάσει να περάσω 5.25 unstable και έστρωσε, αλλά απ'τα πολλά ~ πακέτα, μ@μήθηκε η εγκατάσταση και αναγκάστηκα να επαναφέρω ένα πρόσφατο backup που είχα κρατημένο.
Δεν το ξαναρισκάρω, αλλά ούτε ρισκάρω να περάσω την 5.24, για τους παραπάνω λόγους
-
01-08-22, 18:50 Απάντηση: Το νήμα του Gentoo, version 1.0 #6879
Πειράζει να πω τον πόνο μου για το Tumbleweed εδώ πέρα; Συγχωρέστε με εκ των προτέρων. Το είχα βάλει κάποια στιγμή πέρσι το φθινόπωρο στο φορητό.
[rant mode on]
Άλλα configuration, άλλα group, χρήστες κτλ. σε σχέση με το Gentoo. Προσθέτω το βασικό μου χρήστη σε επιπλέον group, κάνω logout, login, δεν βλέπει το επιπλέον group. Το configuration του Apache, διάσπαρτο σε πόσα conf αρχεία. Μόνο στην PHP δεν έχει διαφορές. Στη MariaDB (για να μην σχολιάσω το γεγονός ότι δίνει την 10.7.3, πού είναι short lived barnch και θα ήθελα την 10.5 να μου δώσει), έχει ένα αρχείο configuration που κάνει include από το my.cnf.d ό,τι υπάρχει εκεί. Ο Thunderbird δεν έχει το ίδιο look όπως το έχω στο Gentoo. Πήγα να βάλω το wine και μου τράβηξε άλλα 125 πακέτα...
[rant mode off]
Καλό το binary, αλλά αν πραγματικά ξέρεις καλά αυτό που δουλεύεις χρόνια (Gentoo), σου φαίνονται όλα στραβά. Με βλέπω να ξαναπερνάω Gentoo...
-
03-08-22, 18:11 Απάντηση: Το νήμα του Gentoo, version 1.0 #6880
Ε ναι ετσι ειναι περα απο οποια ιδιοτροπια μας τραβηξε στο gentoo μετα τοσα χρονια χρησης εγω προσωπικα αν μου πεις να αλλαξω διανομη ειλικρινα θα παω windows, τοσο διαφορετικες μου φαινονται οι αλλες διανομες, κυριως κατι flatpac και παπαλαpack, παροτι διατηρω και ενα debian cloud server. Δεινοσαυρος πλεον...
-
07-08-22, 15:22 Απάντηση: Το νήμα του Gentoo, version 1.0 #6881
Κουτσομπολιά:
2022-07-29-pipewire-sound-server
Title PipeWire sound server migration
Author Sam James <sam@gentoo.org>
Posted 2022-07-29
Revision 1
PipeWire has gained a new USE flag "sound-server" for enabling/disabling its
sound server capabilities.
This change is needed to avoid PipeWire and PulseAudio conflicting over control
of audio devices. Before this change, OpenRC users were in some cases
accidentally migrated to PipeWire which was difficult to override without
manually editing launcher files.
For non-audio purposes, PipeWire is installed in many configurations as more
and more software depends on it for e.g. screensharing, sandboxing,
and window previews, so users will need to act based on their preferred
setup rather than simply avoiding installing PipeWire, as it is
increasingly required as a dependency.
Packages needing PulseAudio's APIs will be migrated from the now-meta package
media-sound/pulseaudio to depending on media-libs/libpulse. The runtime
PulseAudio server can be provided by either PipeWire (media-video/pipewire)
or the original PulseAudio (media-sound/pulseaudio-daemon).
The new sound-server USE flag for PipeWire allows easily controlling
this behavior.
There are several options available:
1. To use PipeWire for sound, users should enable USE=sound-server for PipeWire:
Place the following entries in /etc/portage/package.use:
```
media-video/pipewire sound-server
media-sound/pulseaudio -daemon
```
First, sync:
# emerge --sync
Deselect media-sound/pulseaudio-daemon:
# emerge --deselect media-sound/pulseaudio-daemon
Then perform a world upgrade with PipeWire on the command line to add
it to the world file:
# emerge --ask --update --changed-use --deep @world media-video/pipewire
Then depclean:
# emerge --ask --depclean
OpenRC users on an XDG-compliant desktop which respects autostart files
will not need to take any further action.
OpenRC users using a minimal desktop which does not respect autostart
files will need to run `gentoo-pipewire-launcher &` in e.g.
`~/.xprofile`.
Users who want to switch to PipeWire providing a PulseAudio daemon
may need to `emerge --deselect` packages in their world file which
hard-require media-sound/pulseaudio-daemon. There are only a handful
of these. A non-exhaustive list:
* media-sound/paprefs
* media-sound/pasystray
* media-sound/pulseaudio-modules-bt (shouldn't be needed anyway)
* net-misc/pulseaudio-dlna
If not using any of those packages anymore, please emerge --deselect
them. If still using these, PipeWire as a PulseAudio is not an
option at this time.
(Note that media-libs/libpulse (which PipeWire will be using, don't emerge
libpulse manually) provides 'pactl' which can be used as a replacement for
e.g. media-sound/pulseaudio-ctl, so personal scripts can be adapted to this
if desired.)
systemd users will also need to run the following commands:
$ systemctl --user --now disable pulseaudio.service pulseaudio.socket
$ systemctl --user --now enable pipewire.socket pipewire-pulse.socket
$ systemctl --user --now disable pipewire-media-session.service
$ systemctl --user --force enable wireplumber.service
Root user may replace --user with --global to change system default
configuration for all of the above commands.
2. To use PulseAudio's daemon for sound, users should disable USE=sound-server
for PipeWire, enable USE=daemon on media-sound/pulseaudio, and add
media-sound/pulseaudio-daemon to their world file:
Place the following entries in /etc/portage/package.use:
```
media-video/pipewire -sound-server
media-sound/pulseaudio daemon
```
Add media-sound/pulseaudio-daemon to @world:
# emerge --noreplace media-sound/pulseaudio-daemon
Then perform a world upgrade:
# emerge --ask --update --changed-use --deep @world
Then depclean:
# emerge --ask --depclean
OpenRC users on an XDG-compliant desktop which respects autostart files
will not need to take any further action.
OpenRC users using a minimal desktop which does not respect autostart
files should consider adding `gentoo-pipewire-launcher &` in e.g.
`~/.xprofile` but it's not strictly required in terms of audio
handling. It may be required in future for the non-audio usecases
described above.
systemd users will also need to run the following commands:
$ systemctl --user --now enable pulseaudio.service pulseaudio.socket
$ systemctl --user --now disable pipewire.socket pipewire-pulse.socket
Alternatively, systemd users can run the following commands as root to change
the default for all users:
# systemctl --global enable pulseaudio.service pulseaudio.socket
# systemctl --global --force disable pipewire.socket pipewire-pulse.socket
(If taking this option, the services must be started manually as a one-off as
a user.)
3. For users without sound on their system, those using JACK without
PipeWire, or those using pure ALSA without PipeWire, the following steps
are recommended:
Place the following entries in /etc/portage/package.use:
```
media-video/pipewire -sound-server
media-sound/pulseaudio -daemon
```
Then perform a world upgrade:
# emerge --ask --update --changed-use --deep @world
Then depclean:
# emerge --ask --depclean
OpenRC users on an XDG-compliant desktop which respects autostart files
will not need to take any further action.
OpenRC users using a minimal desktop which does not respect autostart
files will need to run `gentoo-pipewire-launcher &` in e.g.
`~/.xprofile`.
systemd users will also likely want to run the following commands as a user, again
for the purposes of non-audio PipeWire use:
$ systemctl --user --now enable pipewire.socket
$ systemctl --user --now --force enable wireplumber.service
Alternatively, systemd users can run the following commands as root to change
the default for all users, again for the purposes of non-audio PipeWire use:
# systemctl --global enable pipewire.socket
# systemctl --global --force enable wireplumber.service
(If taking this option, the services must be started manually as a one-off as
a user.)
Further resources:
* https://wiki.gentoo.org/wiki/PipeWire
-
07-08-22, 15:27 Re: Το νήμα του Gentoo, version 1.0 #6882
Ούτε pulseaudio, ούτε pipe wire. Μόνο alsa
-
09-08-22, 17:05 Απάντηση: Το νήμα του Gentoo, version 1.0 #6883
-
09-08-22, 22:31 Re: Το νήμα του Gentoo, version 1.0 #6884
Άπαξ και προσαρμοστείς στο Gentoo, δύσκολα φεύγεις.
Ένας βραχνάς υπήρχε, το compile, αλλά με τα νέα συστήματα πλέον, αυτό δεν είναι πρόβλημα.
Εδώ εγώ με επεξεργαστή i3 του 2009 και δεν έχω θέμα.
Μία φορά "πέταξα" το gentoo μου σε έναν ryzen, τον πιο απλό που υπάρχει, και το compile output "πήγαινε" σαν τρελό!
Κι επίσης, ένα πολύ δυνατό πράγμα που έχει το gentoo, είναι η επιλογή του να διατηρήσεις rc, alsa, κλπ. Χωρίς να μπλέξεις με systemd, pulseaudio, flatpacks, κλπ.
Για τον portage, τι να πούμε. Απίστευτη διαχείριση με τα flags, τα dependencies, κλπ (οκ, εξαιρούμε τα circular deps ).
-
18-08-22, 14:47 Απάντηση: Το νήμα του Gentoo, version 1.0 #6885
Για το γρηγορότερο αποτέλεσμα στην μεταγλώττιση η βέλτιστη ρύθμιση είναι πολλά μικρά πακέτα (low makeopts+ high --jobs) και λίγα μεγάλα πακέτα (highest possible makeopts no --jobs setting (defaults to 1) ;
Παρόμοια Θέματα
-
Mozilla: Διαθέσιμη η alpha version του Firefox Mobile
Από nm96027 στο φόρουμ ΕιδήσειςΜηνύματα: 24Τελευταίο Μήνυμα: 27-12-08, 17:40 -
Σχετικά με τη firmware version του router...
Από DSLaManiaC στο φόρουμ ADSLΜηνύματα: 10Τελευταίο Μήνυμα: 09-05-08, 10:34 -
Γκρινια: Νημα Υποστηριξης
Από Reef στο φόρουμ The fun section...Μηνύματα: 109Τελευταίο Μήνυμα: 19-03-07, 10:34 -
Κυκλοφόρησε η final version του Firefox 2
Από Whiteyez στο φόρουμ Software γενικάΜηνύματα: 85Τελευταίο Μήνυμα: 23-12-06, 05:52
Bookmarks