You are not logged in.
Pages: 1
Dear Init Freedom Lovers,
Once again the Veteran Unix Admins salute you on this day commemorating six years since the first Devuan pre-alpha Valentine's Day release in 2015!
Devuan Beowulf 3.1.0 point release installer ISOs, desktop-live, and minimal-live isos are now available. Note that ARM and virtual images are not updated in this release.
## What’s new in this point release
### Installation
The installer now offers a choice of three init systems. runit has been added, along with sysvinit and openrc.
If you would like to select an alternate bootloader (lilo) or exclude non-free firmware, you must select one of the Expert install options.
The recommended default mirror is now deb.devuan.org. If you would like to use a country code mirror, please check the mirror list to see if there is one suitable for your needs.
### Security updates and bug fixes
linux-image-4.19.0-14 Debian 4.19.171-2 (2021-01-30)
firefox-esr 78.7.0esr-1~deb10u1
lightdm 1.26.0-4+devuan1 (fixes bugs related to power buttons and accessibility features)
New package, debian-pulseaudio-config-override corrects problem of pulseaudio being off by default
And many more. (See https://www.debian.org/security/2020/ and https://www.debian.org/security/2021/)
## Documentation
Please read the Release Notes carefully:
https://files.devuan.org/devuan_beowulf … _notes.txt
Beowulf 3.0.0 announcement:
https://www.devuan.org/os/announce/beow … 60120.html
## Download
https://files.devuan.org/devuan_beowulf/
https://www.devuan.org/get-devuan (mirrors)
The latter URL also includes information about the official Devuan package repositories, an ISO selection guide and links to installation guides.
## What about ARM and virtual images?
ARM and Virtual Machine images are provided by the greater Devuan community rather than as part of official releases. Users are being encouraged to build and contribute ARM images for their particular hardware. This will increase the variety of images available and allow the release schedule of the installer ISOs to move forward more quickly.
Images can be built using using arm-sdk and vm-sdk:
https://www.devuan.org/os/distro-kit
Arm-related discussion happens at #devuan-arm (Freenode) and the Dev1Galaxy forum
## Resource Channels
Mailing list: https://mailinglists.dyne.org/cgi-bin/m … stinfo/dng
IRC: #devuan #devuan-dev (Freenode)
Forum: https://dev1galaxy.org
Source code: https://git.devuan.org
Bug tracker: https://bugs.devuan.org
Popularity contest: https://popcon.devuan.org
Package information: https://pkginfo.devuan.org
Press contact: freedom@devuan.org
## Chimaera coming soon
The Devuan development team will now focus on polishing our fourth release, codename “Chimaera”, minor planet no. 623.
## Appreciation
We wish to thank all of you for the incredible support given to this development effort, which continues to make Devuan a useful and reliable base distribution.
To support the Devuan project you can donate at:
https://www.devuan.org/donate (includes financial reports)
or take up one of the tasks listed at:
https://dev1galaxy.org/viewtopic.php?pid=1380#p1380
Happy hacking ;^)
Offline
Great work! Thanks for making another excellent release available.
Offline
Does it include a patch package to undo the horrible change in su behaviour introduced in the 3.0 release?
Online
Yes, thank you very much to all you hard workers at Devuan. An amazing, functional and free operating system!
I had to boot my USB installer in legacy (BIOS) mode rather than UEFI, on my particular PC. If I installed through UEFI, the post-installation boot would end up at the GRUB2 command line.
I installed using ethernet, with the runit init software, and configured wifi after the first reboot. To avoid subsequent slow booting ("ifup: waiting for lock on /run/network/interfaces/ifstate.eth0"), I had to comment out the following lines in /etc/network/interfaces:
# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
#iface eth0 inet6 auto
Offline
Fantastic! Updated and running as smooth as ever.
Big thanks for all the hard work that everyone has put into making this great distro
ruenoak.
"Has cat, eats cheese, drinks coffee, Chaotic Neutral "
Offline
Great, many thanks to the VUA.
Will a simple apt update/upgrade do the job and bring my systems up to 3.1?
Regards
Berni
The good ol' days will not return, and the rocks might smelt and the sea may burn.
Offline
Does it include a patch package to undo the horrible change in su behaviour introduced in the 3.0 release?
What change is that?
Is su, more messed up then before?
Freedom is never more than one generation away from extinction. Feelings are not facts
If you wish to be humbled, try to exalt yourself long term If you wish to be exalted, try to humble yourself long term
Favourite operating systems: Hyperbola Devuan OpenBSD
Peace Be With us All!
Offline
Dutch_Master wrote:Does it include a patch package to undo the horrible change in su behaviour introduced in the 3.0 release?
What change is that?
Is su, more messed up then before?
Have a quick read, including the replies I got.
https://dev1galaxy.org/viewtopic.php?pid=21042#p21042
Online
The path issue with su is not a Devuan topic but coming down from the Debian side of things. Get used to this. Also there are hints in the Release Notes how to handle the issue on your own.
Rolfie
Offline
Will a simple apt update/upgrade do the job and bring my systems up to 3.1?
Yes. Regular update/upgrade will get you there. We made a new set of isos to include all the updates, so if you install without a network mirror, you will get the new stuff.
Offline
Yes. Regular update/upgrade will get you there. We made a new set of isos to include all the updates, so if you install without a network mirror, you will get the new stuff.
Great job, thanks again.
Maybe it's time to say Goodbye to my last Debian machine - only to see, how the new iso will work during installation.
Regards
Berni
The good ol' days will not return, and the rocks might smelt and the sea may burn.
Offline
Where is the torrent for this? When I try to find a torrent for Devuan Beowulf I can only find the old one for 3.0, not this current one.
Offline
The new torrent is on the main page at files.devuan.org and it's linked from the main site on the page that lists the mirrors. Note the date on the file: Feb 15
https://files.devuan.org/
Also note that the 3.0.0 installer isos are still in the download directory, so they are included in the torrent file. If you don't want them, there's a way to select only the files you want. Or if you choose the same directory that already has the old isos as your target, it should just add the new ones.
Offline
Nice to see the installer lets you choose a different init now. Congrats!
Offline
berni51 wrote:Will a simple apt update/upgrade do the job and bring my systems up to 3.1?
Yes. Regular update/upgrade will get you there.
Unfortunately not on my system.
Each day I use:
sudo apt update && sudo apt install -f && sudo apt upgrade
Today that got me kernel 4.19.0-17 + an odd message about a potential 28 further upgrades. Re-running the commands now produces zero result. I'm still on beowulf-3.
Searching then showed this page & the possibility for beowulf-3.1.0 - but not for me.
This is sources:
$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged/ beowulf main non-free contrib
## package repositories
deb http://deb.devuan.org/merged/ beowulf-updates main non-free contrib
deb http://deb.devuan.org/merged/ beowulf-security main non-free contrib
deb http://deb.devuan.org/devuan/ beowulf-proposed main non-free contrib
deb http://deb.devuan.org/merged/ beowulf-backports main non-free contrib
Is this a clue?:
$ sudo apt-get update && apt-get dist-upgrade
Hit:1 http://deb.devuan.org/merged beowulf InRelease
Hit:2 http://deb.devuan.org/merged beowulf-updates InRelease
Hit:3 http://deb.devuan.org/merged beowulf-security InRelease
Hit:4 http://deb.devuan.org/devuan beowulf-proposed InRelease
Hit:5 http://deb.devuan.org/merged beowulf-backports InRelease
Hit:6 https://josm.openstreetmap.de/apt alldist InRelease
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
Those are zero-byte dpkg/lock + dpkg/lock-frontend files, but they appear to be long-established. Removing them made zero difference.
The final item is that I've tried editing 20auto-upgrades (first line from 1 to 0):
$ cat /etc/apt/apt.conf.d/20auto-upgrades
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "1";
That seems to have made zero difference.
I'm out of ideas. All help appreciated.
Offline
fsmithred wrote:berni51 wrote:Will a simple apt update/upgrade do the job and bring my systems up to 3.1?
Yes. Regular update/upgrade will get you there.
Unfortunately not on my system.
Each day I use:
sudo apt update && sudo apt install -f && sudo apt upgrade
Today that got me kernel 4.19.0-17 + an odd message about a potential 28 further upgrades. Re-running the commands now produces zero result. I'm still on beowulf-3.
Searching then showed this page & the possibility for beowulf-3.1.0 - but not for me.
This is sources:
$ cat /etc/apt/sources.list deb http://deb.devuan.org/merged/ beowulf main non-free contrib ## package repositories deb http://deb.devuan.org/merged/ beowulf-updates main non-free contrib deb http://deb.devuan.org/merged/ beowulf-security main non-free contrib deb http://deb.devuan.org/devuan/ beowulf-proposed main non-free contrib deb http://deb.devuan.org/merged/ beowulf-backports main non-free contrib
Is this a clue?:
$ sudo apt-get update && apt-get dist-upgrade Hit:1 http://deb.devuan.org/merged beowulf InRelease Hit:2 http://deb.devuan.org/merged beowulf-updates InRelease Hit:3 http://deb.devuan.org/merged beowulf-security InRelease Hit:4 http://deb.devuan.org/devuan beowulf-proposed InRelease Hit:5 http://deb.devuan.org/merged beowulf-backports InRelease Hit:6 https://josm.openstreetmap.de/apt alldist InRelease Reading package lists... Done E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
Those are zero-byte dpkg/lock + dpkg/lock-frontend files, but they appear to be long-established. Removing them made zero difference.
The final item is that I've tried editing 20auto-upgrades (first line from 1 to 0):
$ cat /etc/apt/apt.conf.d/20auto-upgrades APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Unattended-Upgrade "1";
That seems to have made zero difference.
I'm out of ideas. All help appreciated.
Those "lock file" messages appear to me to be saying that you're running your commands as a normal user, not as root. Since you're using sudo, my guess is that something is wrong with -- or has changed --- in your sudo configuration.
Last edited by ComputerBob (2021-06-23 11:45:31)
ComputerBob - Making Geek-Speak Chic (TM)
ComputerBob.com - Nearly 6,000 Posts and 22 Million Views since 1998
My Massive Stroke
Help! (off-topic)
Offline
Is this a clue?:
$ sudo apt-get update && apt-get dist-upgrade Hit:1 http://deb.devuan.org/merged beowulf InRelease Hit:2 http://deb.devuan.org/merged beowulf-updates InRelease Hit:3 http://deb.devuan.org/merged beowulf-security InRelease Hit:4 http://deb.devuan.org/devuan beowulf-proposed InRelease Hit:5 http://deb.devuan.org/merged beowulf-backports InRelease Hit:6 https://josm.openstreetmap.de/apt alldist InRelease Reading package lists... Done E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
Those are zero-byte dpkg/lock + dpkg/lock-frontend files, but they appear to be long-established. Removing them made zero difference.
Hi alexkemp
I can't really address the main complaint/question, but perhaps I could address this clue? I have the idea that the "apt-get dist-upgrade" after the && needs its own sudo ? That might explain the "are you root" response.
Offline
sudo apt update && sudo apt install -f && sudo apt upgrade
Today that got me kernel 4.19.0-17 + an odd message about a potential 28 further upgrades. Re-running the commands now produces zero result. I'm still on beowulf-3.
If those commands completed without error, then it's correct that there are no more upgrades, because you already got them, and your beowulf is fully updated and current. You can check to see what got upgraded or installed by looking in /var/log/apt/history.log.
Offline
sudo apt update && sudo apt install -f && sudo apt upgrade
…I'm still on beowulf-3.
…You can check to see what got upgraded or installed by looking in /var/log/apt/history.log.
Many thanks to all those that responded.
It seems that I *am* on beowulf-3.1.0, but that the release info was not updated.
I see from the Release Announcement that Beowulf-3.1 was released with linux-image-4.19.0-14. The upgrade obtained 24 hours ago was linux-image-4.19.0-17. The command-line shown is for "upgrade". That strongly suggest that yes, I did get a 3.1 upgrade. However, what I did NOT get was an upgraded /etc/os-release, which has led me astray.
The remarks that some 'sudo's were missed from some commands are also obviously accurate.
Sorry about the size of the code that follows. This is the tail of /var/log/apt/history.log:
Start-Date: 2021-06-23 00:12:23
Commandline: apt upgrade
Requested-By: alexk (1000)
Install: linux-image-4.19.0-17-amd64:amd64 (4.19.194-1, automatic)
Upgrade: linux-libc-dev:amd64 (4.19.181-1, 4.19.194-1),
libxml2-utils:amd64 (2.9.4+dfsg1-7+deb10u1, 2.9.4+dfsg1-7+deb10u2),
libgnutls-openssl27:amd64 (3.6.7-4+deb10u6, 3.6.7-4+deb10u7),
fig2dev:amd64 (1:3.2.7a-5+deb10u3, 1:3.2.7a-5+deb10u4),
mariadb-common:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1),
libklibc:amd64 (2.0.6-1, 2.0.6-1+deb10u1),
isc-dhcp-common:amd64 (4.4.1-2, 4.4.1-2+deb10u1),
libfluidsynth1:amd64 (1.1.11-1, 1.1.11-1+deb10u1),
shim-helpers-amd64-signed:amd64 (1+15+1533136590.3beb971+7+deb10u1, 1+15.4+5~deb10u1),
linux-image-amd64:amd64 (4.19+105+deb10u11, 4.19+105+deb10u12),
libgcrypt20:amd64 (1.8.4-5, 1.8.4-5+deb10u1),
libglib2.0-bin:amd64 (2.58.3-2+deb10u2, 2.58.3-2+deb10u3),
libhogweed4:amd64 (3.4.1-1, 3.4.1-1+deb10u1),
shim-unsigned:amd64 (15+1533136590.3beb971-7+deb10u1, 15.4-5~deb10u1),
python-libxml2:amd64 (2.9.4+dfsg1-7+deb10u1, 2.9.4+dfsg1-7+deb10u2),
shim-signed:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+15.4-5~deb10u1),
libglib2.0-data:amd64 (2.58.3-2+deb10u2, 2.58.3-2+deb10u3),
libnettle6:amd64 (3.4.1-1, 3.4.1-1+deb10u1),
libxml2:amd64 (2.9.4+dfsg1-7+deb10u1, 2.9.4+dfsg1-7+deb10u2),
libmariadb3:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1),
libgnutls30:amd64 (3.6.7-4+deb10u6, 3.6.7-4+deb10u7),
xfce4-weather-plugin:amd64 (0.8.10-1, 0.8.10-1+deb10u1),
josm-latest:amd64 (1.5.svn17921, 1.5.svn17938),
libgnutls-dane0:amd64 (3.6.7-4+deb10u6, 3.6.7-4+deb10u7),
isc-dhcp-client:amd64 (4.4.1-2, 4.4.1-2+deb10u1),
klibc-utils:amd64 (2.0.6-1, 2.0.6-1+deb10u1),
libglib2.0-0:amd64 (2.58.3-2+deb10u2, 2.58.3-2+deb10u3),
shim-signed-common:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+15.4-5~deb10u1)
End-Date: 2021-06-23 00:15:03
Last edited by alexkemp (2021-06-23 23:21:26)
Offline
Congratulations to the whole team and keep it going!
I jumped to Chimaera some time ago and its surprisingly stable
soystemd-free diet
Offline
Pages: 1