why not updating to GNU-Bash-5.3 ?

Message
Author
User avatar
oops
Posts: 1963
Joined: Tue Apr 10, 2018 5:07 pm

why not updating to GNU-Bash-5.3 ?

#1 Post by oops »

Hello, why not updating to the new GNU-Bash-5.3 ? (for MX25 too)

https://www.phoronix.com/news/GNU-Bash-5.3
https://lists.gnu.org/archive/html/bug- ... 00004.html
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils MX Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19-23_x64 & antiX23_x32 runit

Nokkaelaein
Posts: 338
Joined: Fri Jul 17, 2020 10:32 am

Re: why not updating to GNU-Bash-5.3 ?

#2 Post by Nokkaelaein »

That's a good idea; however, saying it like that sounds like you are wondering... why it isn't updated already. Can you name many distros that have, at the time of writing, updated their bash to 5.3? It came out just a few days ago :)

User avatar
oops
Posts: 1963
Joined: Tue Apr 10, 2018 5:07 pm

Re: why not updating to GNU-Bash-5.3 ?

#3 Post by oops »

... It is mostly a suggestion. (and I have already intalled it into MX19, an old eepc, bash v5.3.0 from V5.0.3 ... and SysVinit v: 3.14 too)

Code: Select all

Snapshot created on: 20230501_0204
System:
  Kernel: 6.6.87-amd64-i386-x86-32--486dx arch: i686 bits: 32 compiler: gcc
    v: 8.3.0 clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6.87-amd64-i386-x86-32--486dx
    root=UUID=<filter> ro audit=0
    mitigations=auto ipv6.disable=1 selinux=0 zswap.enabled=1
    zswap.compressor=zstd zswap.max_pool_percent=25 zswap.zpool=zsmalloc
    quiet
  Desktop: IceWM v: 3.8.0 tools: xautolock,xfce4-screensaver
    avail: i3lock,slock,xscreensaver vt: 7 dm: LightDM v: 1.26.0
    Distro: MX-TOF-19.4_386 patito feo mai 01 2023 base: Debian GNU/Linux 10
    (buster)
Machine:
  Type: Laptop System: MICRO-STAR product: MS-N033 v: Ver.001
    serial: <superuser required>
  Mobo: MICRO-STAR model: U-123 v: Ver.001 serial: <superuser required>
    uuid: <superuser required> BIOS: American Megatrends v: 4.6.3
    date: 05/06/2010
CPU:
  Info: model: Intel Atom N280 bits: 32 type: MT arch: Bonnell built: 2008-13
    process: Intel 45nm family: 6 model-id: 0x1C (28) stepping: 2
    microcode: 0x218
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 1 threads: 2 tpc: 2
    smt: enabled cache: L1: 56 KiB desc: d-1x24 KiB; i-1x32 KiB L2: 512 KiB
    desc: 1x512 KiB
  Speed (MHz): avg: 1000 min/max: 1000/1667 scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 1000 2: 1000 bogomips: 6668
  Flags: ht nx pae sse sse2 sse3 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 status: Not affected
  Type: spectre_v2 status: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Mobile 945GSE Express Integrated Graphics
    vendor: Micro-Star MSI driver: i915 v: kernel alternate: intelfb
    arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports: active: LVDS-1
    empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:27ae class-ID: 0300
  Display: x11 server: X.Org v: 1.20.10 driver: X: loaded: intel
    unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1024x600 s-dpi: 96 s-size: 270x158mm (10.63x6.22")
    s-diag: 313mm (12.32")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Chungwa Picture Tubes 0x04c4
    built: 2009 res: mode: 1024x600 hz: 60 scale: 100% (1) dpi: 113 gamma: 1.2
    size: 230x140mm (9.06x5.51") diag: 269mm (10.6") ratio: 15:9, 16:9
    modes: 1024x600
  API: OpenGL v: 1.4 vendor: intel mesa v: 20.3.5 glx-v: 1.4 es-v: 2.0
    direct-render: yes renderer: Mesa DRI Intel 945GME x86/MMX/SSE2
    device-ID: 8086:27ae memory: 187.5 MiB unified: yes
  Info: Tools: api: clinfo,glxinfo de: xfce4-display-settings x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:27d8 class-ID: 0403
  API: ALSA v: k6.6.87-amd64-i386-x86-32--486dx status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PulseAudio v: 12.2 status: active
    tools: pacat,pactl,pamixer,pavucontrol
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros AR928X Wireless Network Adapter
    vendor: AzureWave AW-NE771 802.11bgn driver: ath9k v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 168c:002a class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IF-ID-2: virbr0-nic state: down mac: <filter>
  Info: services: NetworkManager,ntpd,smbd,sshd
Drives:
  Local Storage: total: 111.79 GiB used: 37.18 GiB (33.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: 120GB SATA SSD
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s
    tech: SSD serial: <filter> fw-rev: 8A0 scheme: MBR
Partition:
  ID-1: / raw-size: 108.78 GiB size: 106.51 GiB (97.92%)
    used: 37.18 GiB (34.9%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 5 (default 60) cache-pressure: 50 (default 100)
    zswap: yes compressor: zstd max-pool: 25%
  ID-1: swap-1 type: partition size: 2.81 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: dpkg pkgs: 2901 libs: 1346
    tools: apt,apt-get,aptitude,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/antix-kernel-tmp.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian buster main contrib non-free
    2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/extended-lts.list
    1: deb http://deb.freexian.com/extended-lts buster-lts main contrib non-free
    2: deb http://deb.freexian.com/extended-lts buster main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mozilla.list
    1: deb [signed-by=/etc/apt/keyrings/packages.mozilla.org.asc] https://packages.mozilla.org/apt mozilla main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ buster main non-free
    2: deb http://mxrepo.com/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
  Memory: total: N/A available: 1.94 GiB used: 645.8 MiB (32.4%)
  Processes: 215 Power: uptime: 2h 42m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 3 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 757.3 MiB
    services: upowerd,xfce4-power-manager Init: SysVinit v: 3.14 runlevel: 5
    default: graphical tool: systemctl
  Compilers: gcc: 8.3.0 Shell: quick-system-in default: Bash v: 5.3.0
    running-in: quick-system-in inxi: 3.3.38
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils MX Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19-23_x64 & antiX23_x32 runit

User avatar
siamhie
Global Moderator
Posts: 3462
Joined: Fri Aug 20, 2021 5:45 pm

Re: why not updating to GNU-Bash-5.3 ?

#4 Post by siamhie »

Bash is packaged by Debian.

Code: Select all

Package: bash
Version: 5.2.15-2+b8
Essential: yes
State: installed
Automatically installed: no
Multi-Arch: foreign
Priority: required
Section: shells
Maintainer: Matthias Klose <doko@debian.org>
Trixie looks to be releasing Bash with version 5.2.37-2. https://packages.debian.org/trixie/bash
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

User avatar
oops
Posts: 1963
Joined: Tue Apr 10, 2018 5:07 pm

Re: why not updating to GNU-Bash-5.3 ?

#5 Post by oops »

I guess than trixie will have the v5.3 now.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils MX Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19-23_x64 & antiX23_x32 runit

User avatar
Adrian
Developer
Posts: 9071
Joined: Wed Jul 12, 2006 1:42 am

Re: why not updating to GNU-Bash-5.3 ?

#6 Post by Adrian »

That kind of sucks, but that's what we have if we based our distro on Debian Stable... there are plusses and minuses. It would be a good question for Debian people but there's nothing they can do either: https://release.debian.org/trixie/freeze_policy.html

User avatar
oops
Posts: 1963
Joined: Tue Apr 10, 2018 5:07 pm

Re: why not updating to GNU-Bash-5.3 ?

#7 Post by oops »

... Yes, it mostly depends of Debian in fact.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils MX Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19-23_x64 & antiX23_x32 runit

User avatar
Adrian
Developer
Posts: 9071
Joined: Wed Jul 12, 2006 1:42 am

Re: why not updating to GNU-Bash-5.3 ?

#8 Post by Adrian »

oops wrote: Mon Jul 07, 2025 3:38 pm ... Yes, it mostly depends of Debian in fact.
I would not go and ask our packagers to package and put it in the repo, we don't know in what subtle ways things would break. Although... I am not entirely sure bash is foundational, I don't even see it as a dependency to many packages, I'm just afraid many packages just assume bash exists and behaves in a specific way.

User avatar
oops
Posts: 1963
Joined: Tue Apr 10, 2018 5:07 pm

Re: why not updating to GNU-Bash-5.3 ?

#9 Post by oops »

Adrian wrote: Mon Jul 07, 2025 4:07 pm
oops wrote: Mon Jul 07, 2025 3:38 pm ... Yes, it mostly depends of Debian in fact.
I would not go and ask our packagers to package and put it in the repo, we don't know in what subtle ways things would break. Although... I am not entirely sure bash is foundational, I don't even see it as a dependency to many packages, I'm just afraid many packages just assume bash exists and behaves in a specific way.
Until now, I use the bash v5.3.0 into MX19 without issue. (with some adaptations, the root prompt, etc)
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils MX Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19-23_x64 & antiX23_x32 runit

User avatar
Stevo
Developer
Posts: 14712
Joined: Fri Dec 15, 2006 7:07 pm

Re: why not updating to GNU-Bash-5.3 ?

#10 Post by Stevo »

Maybe a quick "elevator pitch" as to why we could need it instead of the tried-and-true Debian bashes could persuade a packager.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

Post Reply

Return to “Package Requests - MX-23”