Posts by alexkemp

alexkemp · Hardware & System Configuration

Isn't this a question of mixing amd64 & i386? Or am I missing something?

alexkemp · Other Issues

Hi Iggy64

I also run Devuan Chimaera xfce and thought that I may be able to offer help, but have only come up with a big set of negatives.

• Synaptic opens fine for me & likewise Settings > Repositories quickly opens with zero issues.
• I can get zero response for any file (using "locate") named 'UbuntuDrivers' & using just 'Ubuntu' gives nothing close.
• Searching within Synaptic for 'UbuntuDrivers' gives zero result.
• package-update-indicator is NOT installed. The help for the package says “This small utility which regularly checks for software updates … It is primarily intended for desktops which do not already have this functionality built-in, such as Xfce”.
• I do have PackageKit installed, and possibly this is the package that replaces package-update-indicator for xfce.

Sorry I could not offer any help.

alexkemp · Devuan

I'm running Chimaera with backports & kernel is 5.16:

$ grep -h ^deb /etc/apt/sources.list /etc/apt/sources.list.d/*
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

$ uname -r
5.16.0-0.bpo.4-amd64

You will notice the 'bpo' within the kernel name, which indicates that it's origin is "backports".

alexkemp · Other Issues

Shift-PageUp / Shift-PageDown works for me.

$ cat /etc/devuan_version
chimaera
$ cat ~/.bash_history

(then Shift-PageUp, etc.)

Help | About: xfce4-terminal 0.8.10

alexkemp · Installation

migf wrote:

Do you think I should change to your configuration by installing libpolkit-gobject-elogind-1-0?

Short answer: yes (but see bottom).

Long Answer: read this thread (also with a Summary of the whole process)

tl;dr: sudo apt install libpam-elogind then restart multiple times until the sun shines again.

alexkemp · Installation

migf wrote:

Can this be a problem with the new linux kernel (5.10.0-12)?

You also state that you are running Chimaera. Hmm. This is from my fully-updated system just now:

$ uname -r
5.16.0-0.bpo.3-amd64

$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

$ dpkg -l | egrep "logind|consolekit|libpam|policykit|polkit|upower"
rc  consolekit                            1.2.1-8                                amd64        framework for defining and tracking users, sessions and seats
ii  elogind                               246.10-2                               amd64        user, seat and session management daemon
ii  gir1.2-polkit-1.0                     0.105-31+devuan2                       amd64        GObject introspection data for PolicyKit
ii  libelogind0:amd64                     246.10-2                               amd64        user, seat and session management library
ii  libpam-cap:amd64                      1:2.44-1                               amd64        POSIX 1003.1e capabilities (PAM module)
ii  libpam-elogind:amd64                  246.10-2                               amd64        elogind PAM module
ii  libpam-gnome-keyring:amd64            3.36.0-1                               amd64        PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64                  1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules for PAM
ii  libpam-modules-bin                    1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime                        1.4.0-9+deb11u1                        all          Runtime support for the PAM library
ii  libpam0g:amd64                        1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules library
ii  libpolkit-agent-1-0:amd64             0.105-31+devuan2                       amd64        PolicyKit Authentication Agent API
ii  libpolkit-gobject-1-0                 0.105-31+devuan2                       all          PolicyKit Authorization API
ii  libpolkit-gobject-elogind-1-0:amd64   0.105-31+devuan2                       amd64        PolicyKit Authorization API
ii  libpolkit-qt5-1-1:amd64               0.113.0-1                              amd64        PolicyKit-qt5-1 library
ii  libupower-glib1:amd64                 1:0.9.23-2+devuan1.3                   amd64        abstraction for power management - shared library
ii  libupower-glib3:amd64                 0.99.11-2                              amd64        abstraction for power management - shared library
ii  policykit-1                           0.105-31+devuan2                       amd64        framework for managing administrative policies and privileges
ii  policykit-1-gnome                     0.105-7                                amd64        authentication agent for PolicyKit
ii  upower                                1:0.9.23-2+devuan1.3                   amd64        abstraction for power management

Something else for you to look at.

alexkemp · Other Issues

FWIW here is my sources.list:

$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

alexkemp · Off-topic

MiyoLinux wrote:

You obviously don't know anything about me...

If I got stuff wrong I apologise. I simply was reacting to what you wrote (and, it looks, got hold of completely the wrong end of it). Again, sincere apologies. It may be that I got weird-ed out by rabid antisemitism in another thread & lost my bearings.

I doubt that it will help, but here's a little story from immediately after I got my booster last Autumn (it connects with your report of eye-problems):-

I walked to town (~20 minutes) & had just bought a cheap hot-chicken sandwich on my way to the bus-stop when my eyesight unhooked. It's a bit difficult to explain, but our eyesight auto-focuses & auto-co-ordinates each eye whilst doing so. In this case, for the first time, and with no reason that I can discern, apart perhaps due to the booster jab, the latter auto-coordination unhooked and I found myself with each eye looking around independently. I had to grab a lamppost to keep my balance, then closed both eyes & the nausea which had been building rapidly backed off. Opening both eyes again it immediately restarted, so I closed them both again & wondered how the hell I was going to cross the road.

On an inspiration I opened just one eye & there was no problem. A minute or two later I opened the other & everything was back to normal. It has never reoccurred. Man, that was strange, but if the booster helps me live I'm happy to pay that price.

I hope that your wife & son do not have any ongoing complications.

alexkemp · Off-topic

MiyoLinux wrote:

alexkemp wrote:
My wife and son had Corona, were at home for 10 days, and I never caught it.
Yup. That's what Typhoid Mary said.
Dude...I was just giving my story

Typhoid Mary also refused to accept what the doctors said (with hindsight, that she was an asymptomatic carrier of Typhoid) and thus killed most of her employers (she was employed as a cook, and Typhoid is water-borne).

I simply wanted to point out that you could also be an asymptomatic carrier, this time of Covid-19, so that you could quietly do the decent thing & go get yourself tested so that (if true) you do not infect & kill hundreds of other innocent parties. Or, deploy your raging ego as a scimitar to destroy those unvaccinated around you. Such a difficult choice.

alexkemp · Off-topic

My wife and son had Corona, were at home for 10 days, and I never caught it.

Yup. That's what Typhoid Mary said. But of course you are special, are you not?

alexkemp · Devuan

walterbyrd wrote:

I used RHEL and CentOS at home, and professionally, before the dark days of gnome3/systemd. …
After "upgrading" from CentOS 6.5, I tried hard to like the new CentOS, but failed. I absolutely hated gnome3/systemd, which is why I went with Devuan and MATE.

Ditto. I began administering my own server shortly into the new millennium, just before the first version of CentOS was released (I think it was also shortly before RHEL was a thing, but it *was* RedHat). Then I got a dedicated server, built by the guys that later started CentOS. They were corrupt (I'll try to avoid the whole story, but they have worked extremely hard to make sure that Google does not retain any mention of either of them). I went with RedHat & later moved to CentOS after shifting Host when the two CentOS guys screwed me over (I was used to RH by then, and only afterwards discovered that they were leading agents in establishing CentOS).

I was also disillusioned by CentOS (or, more accurately, RH & their practices with Enterprise Linux). Specifically, it was the way that they deliberately made it impossible to do an in-place upgrade from one major version to another. IIRC they first tried to stop the in-place upgrade of RHEL/CentOS-4 to -5 but, although it was difficult, effective steps to achieve it were published (I may have the versions wrong). They then made sure that RHEL/CentOS-5 to -6 actually *was* impossible; you had to utterly wipe the server before installation. I was done with RedHat after that.

Contrast Devuan:– I started with Debian-Jessie & did an in-place upgrade to Devuan. Not easy, but it worked without too much fuss. Then in-place upgrades through 3 more versions (ASCII, Beowulf & now Chimaera). Yet another impressive difference between RH & Devuan.

alexkemp · Installation

(apt-add-repository): Ah yes, so I see, cannot even find it in a devuan repo. What a shame, looks like a useful utility, even if only used once.

I cannot recall having seen a debian url during my daily updates from command-line. Perhaps need to look more closely next time.

alexkemp · Installation

Yes. Your sources are wrong, somewhere (should be deb.devuan.org, not debian) (look at the error msg, not your sources.list).

Try $ apt-cache policy to get the full list, or (to summarise) apt-cache policy | awk '/http.*amd64/{print$2}' | sort -u. FWIW, here is my current repository list:

$ grep -h ^deb /etc/apt/sources.list /etc/apt/sources.list.d/*
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

Once you are sure of your repository list, and place it into a suitable file (eg 'current.repos.list'), the following will setup your repository for you (see stackoverflow):

apt-add-repository << current.repos.list

alexkemp · Documentation

ruenoak wrote:

Hi tempvan1,
I think you need to use the whole path
/usr/sbin/service --status-all

That certainly works. However, for me so does the bare service --status-all (as an ordinary user, under chimaera, tested just now).

alexkemp · Other Issues

I had the same problem with Beowulf. It seems that the maintainer "forgot" to update devuan_version. It is still going on (notice no number):

$ cat /etc/devuan_version
chimaera

alexkemp · Hardware & System Configuration

bitcrashr wrote:

I don't know what is meant by "persistent volume"

My assumption here, not only because I'm not the original author but also because I'm far distant in time from my original use of them. My assumption, then:-

Whenever a Read-Only storage device is used, the problem becomes how to deal with data that needs to be carried over from one session to another. The fix is (for example) to format the storage so that a small section is Read-Write, and that is designated as a "Persistent Volume" (normally on a separate partition).

Added later: (I was hoping for an authoritative definition but could not find one quickly. Here is a web-page for creating a USB-stick with Persistent Storage which may be useful for some):
Create bootable USB Flash-Drive with Persistent Storage

Note the caveats for even this one:

You can’t modify system files, like the kernel. You can’t perform major system upgrades. You also can’t install hardware drivers. However, you can install most applications.

alexkemp · Other Issues

hevidevi wrote:

i used pip to install it which should give the latest version.

The version in the Repository is identical to that currently available under GitHub (I checked before install). In addition, yt-dlp -U will auto-update (just like youtube-dl) and without any of that local-bin nonsense - I have two youtube-dl's because of delays in Jessie updates, but have fixed that in Chimaera by making use of backports.

alexkemp · Other Issues

I just used Synaptic to install yt-dlp from Devuan repository (under Chimaera, using stable-backports). Problem solved. After all, all these weeks later youtube-dl has still not fixed the slowdown-issue (yt-dlp has fixed it, as have others).

alexkemp · Desktop and Multimedia

I run Chimaera-upgraded-from-Beowulf with XFCE. However, I have not had your problem, which does not help me to help you. However, in an attempt to help I ran with your report on polkit & searched in Synaptic for it; the single installed item was gir1.2-polkit-1.0 (GObject introspection data for PolicyKit), so that seems to be the one:

GObject introspection data for PolicyKit

PolicyKit is a toolkit for defining and handling the policy that
allows unprivileged processes to speak to privileged processes.
This package contains introspection data for PolicyKit.
It can be used by packages using the GIRepository format to generate
dynamic bindings.

Added:

Taking this one step further by searching for PolicyKit, there is one further item installed: cups-pk-helper (PolicyKit helper to configure cups with fine-grained privileges):

PolicyKit helper to configure cups with fine-grained privileges

This package provides a PolicyKit helper to configure cups with
fine-grained privileges. For example, it's possible to let users
enable/disable printers without requiring a password, while still
requiring a password for editing printer settings.

alexkemp · Devuan

Hi there swarfendor437

I cannot answer for SoftMaker nor pdf Studio Pro, but my recall is that I got problems with a single installation, which was KeyMon (a python-driven utility which shows the keyboard keys pressed as you press them - very useful for YouTube videos if you are recording your desktop/terminal for YT).

The issue was the departure from Python2 to a base-standard of Python3 (all of this is off the top of my head & thus prone to errors). The repository-version of KeyMon could not run on python3 and thus KeyMon was not in Chimaera & wiped from my system on upgrade. Thankfully I found a github version by the original writer with specifically added python-3 support & it works fine.

For the rest I give the full instructions that allowed me to upgrade. So, either use that or refer to the links in the OP to bake it yourself.

alexkemp · Devuan

OK, it's official (announced yesterday), Chimera is now the STABLE release:

https://www.devuan.org/os/announce/chim … 2021-10-14

Re-running the general update again & liblibreoffice-java has been updated & is no longer held back.

alexkemp · Devuan

Backports has been uncommented, resulting in LibreOffice updating to 7.2.1. The reason for that is that I appear to have done a customary system update just now exactly as Chimaera has gone from 'testing' to 'stable' (see the terminal results below):

:~$ sudo apt update && sudo apt install -f && sudo apt upgrade && sudo /usr/local/bin/youtube-dl -U && sudo /etc/cron.daily/mlocate
Get:1 https://josm.openstreetmap.de/apt alldist InRelease [4,591 B]
Get:2 https://josm.openstreetmap.de/apt alldist/universe amd64 Packages [1,083 B]
Get:3 http://deb.devuan.org/merged chimaera InRelease [33.8 kB]    
Get:4 http://deb.devuan.org/merged chimaera-security InRelease [21.3 kB]
Get:5 http://deb.devuan.org/merged chimaera-updates InRelease [26.4 kB]
Get:6 http://deb.devuan.org/devuan chimaera-proposed-updates InRelease [24.5 kB]
Fetched 112 kB in 3s (39.5 kB/s)    
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
N: Repository 'http://deb.devuan.org/merged chimaera InRelease' changed its 'Version' value from '4.0.0' to '4.0'
N: Repository 'http://deb.devuan.org/merged chimaera InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: Repository 'http://deb.devuan.org/merged chimaera-security InRelease' changed its 'Suite' value from 'testing-security' to 'stable-security'
N: Repository 'http://deb.devuan.org/merged chimaera-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates'
N: Repository 'http://deb.devuan.org/devuan chimaera-proposed-updates InRelease' changed its 'Suite' value from 'testing-proposed-updates' to 'chimaera-proposed-updates'
Reading package lists... Done
…
Do you want to continue? [Y/n] n
Abort.

A quick `sudo nano /etc/apt/sources.list`, remove the comment ('#') from backports & run the original update again, with dramatic results:

:~$ sudo apt update && sudo apt install -f && sudo apt upgrade && sudo /usr/local/bin/youtube-dl -U && sudo /etc/cron.daily/mlocate
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Get:2 http://deb.devuan.org/merged chimaera-security InRelease [21.3 kB]     
Get:3 http://deb.devuan.org/merged chimaera-updates InRelease [26.4 kB]      
Hit:4 http://deb.devuan.org/devuan chimaera-proposed-updates InRelease                   
Get:5 http://deb.devuan.org/merged chimaera-backports InRelease [19.3 kB]    
Hit:6 https://josm.openstreetmap.de/apt alldist InRelease                    
Get:7 http://deb.devuan.org/merged chimaera-security/main amd64 Packages [47.9 kB]
Get:8 http://deb.devuan.org/merged chimaera-backports/main amd64 Packages [89.5 kB]
Get:9 http://deb.devuan.org/merged chimaera-backports/non-free amd64 Packages [1,216 B]
Get:10 http://deb.devuan.org/merged chimaera-backports/contrib amd64 Packages [536 B]
Fetched 206 kB in 2s (131 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
36 packages can be upgraded. Run 'apt list --upgradable' to see them.
…
The following packages were automatically installed and are no longer required:
  libcmis-0.5-5v5 libjuh-java libjurt-java libqrcodegencpp1 libridl-java libunoil-java
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  libbox2d2.3.0 libzxingcore1 ure-java
The following packages have been kept back:
  liblibreoffice-java
The following packages will be upgraded:
  at-spi2-core fonts-opensymbol gir1.2-atspi-2.0 gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 iproute2 josm-latest libatspi2.0-0
  libjavascriptcoregtk-4.0-18 libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw
  libreoffice-gtk3 libreoffice-help-common libreoffice-help-en-us libreoffice-impress libreoffice-java-common libreoffice-math
  libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-style-colibre libreoffice-writer libuno-cppu3
  libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 libuno-salhelpergcc3-3 libunoloader-java libvulkan1
  libwebkit2gtk-4.0-37 orca uno-libs-private ure
35 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 135 MB/135 MB of archives.
After this operation, 12.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
…

Not too long, and everyone can now expect an auto-update to Chimaera as Stable!

alexkemp · Devuan

…or at least, it would be if I hadn't made a small mistake & someone in some mirror hadn't made a bigger mistake.

Reason for Upgrade:

I was backing up all my DVDs to a USB hard-disk as ISOs & then extracting as mp4 using Handbrake. There were far too many errors in the latest version supplied with Beowulf, and Chimaera offered a much later version. That proved to be fully correct after update.

Before Upgrade:

Pages consulted:

Install page: https://www.devuan.org/os/install
Packages for sources.list: https://www.devuan.org/os/packages

Since Chimaera was reported to be almost ready for transition to Stable, after consulting the above I decided that it should be possible to make a simple replacement in my existing sources.list of 'beowulf' by 'chimaera'. That was accurate except for the commented-out Chimaera line below.

Method of Upgrade:

~$ sudo nano /etc/apt/sources.list
~$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
#deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

## package repositories
#deb http://deb.devuan.org/merged/ beowulf main non-free contrib 
#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 

~$ sudo apt-get update && sudo apt-get dist-upgrade

Errors Experienced:

A single package (Libreoffice from Backports) gave a 404 File Not Accessible & the whole update collapsed in the middle. Unfortunately XFCE was in the middle of update & the GUI (including SLIM) failed after I tried restarting. Fortunately, I'm comfortable administering servers from a terminal.

The Fix:

This was easy once I got the point.

The problem was in a remote mirror connected with chimaera-backports. After commenting-out that line I did the update/dist-upgrade again (and again & again). The system complained, but gave some sensible suggestions, which I followed:

~$ sudo apt --fix-broken install
~$ sudo dpkg --configure -a

It's a heck of a business replacing a complete OS, of course, so I was patient and it finally completed.

The whole thing has gone from:

Devuan GNU/Linux 3.1 (beowulf) x86_64
to:
Devuan GNU/Linux 4 (chimaera) x86_64

Good job, veteran Admins!

(updated (speling))

alexkemp · News & Announcements

fsmithred wrote:

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

alexkemp · News & Announcements

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.

The officially official Devuan Forum!

#326 Re: Hardware & System Configuration » [SOLVED] Backported package install with unmet dependency » 2022-05-03 10:21:49

#327 Re: Other Issues » [SOLVED] Synaptic No Longer Shows Repositories » 2022-04-28 01:47:30

#328 Re: Devuan » [SOLVED] Existential doubt » 2022-04-18 09:33:53

#329 Re: Other Issues » Scrolling Output in the Console Window » 2022-04-03 11:11:10

#330 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-18 08:59:26

#331 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 19:06:49

#332 Re: Other Issues » Featured in Discover (KDE Plasma) not working » 2022-03-01 22:25:25

#333 Re: Off-topic » The seitan conundrum » 2022-02-22 23:26:31

#334 Re: Off-topic » The seitan conundrum » 2022-02-22 19:41:07

#335 Re: Off-topic » The seitan conundrum » 2022-02-22 14:22:27

#336 Re: Devuan » Devuan vs. RHEL/CentOS : my experience » 2022-02-19 02:28:52

#337 Re: Installation » Setup & Repo problem » 2022-02-10 13:46:02

#338 Re: Installation » Setup & Repo problem » 2022-02-10 13:21:25

#339 Re: Documentation » Help - list all services » 2022-02-02 09:46:03

#340 Re: Other Issues » Why isn't my beowulf being upgraded to 3.1? » 2022-01-21 15:32:35

#341 Re: Hardware & System Configuration » authorization problems possibly due to frankendevuan (attn: fsmithred) » 2022-01-20 22:23:04

#342 Re: Other Issues » [SOLVED] youtube-dl upgrade problem » 2022-01-20 12:44:20

#343 Re: Other Issues » [SOLVED] youtube-dl upgrade problem » 2022-01-20 11:22:16

#344 Re: Desktop and Multimedia » [SOLVED] Broken pkexec in Chimaera » 2022-01-13 12:34:03

#345 Re: Devuan » Updating to Chimaera - Marginally Painless » 2021-12-12 17:09:27

#346 Re: Devuan » Updating to Chimaera - Marginally Painless » 2021-10-14 23:35:52

#347 Re: Devuan » Updating to Chimaera - Marginally Painless » 2021-10-14 17:25:28

#348 Devuan » Updating to Chimaera - Marginally Painless » 2021-10-03 12:31:26

Reason for Upgrade:

Before Upgrade:

Method of Upgrade:

Errors Experienced:

The Fix:

#349 Re: News & Announcements » Devuan Beowulf 3.1.0 point release » 2021-06-23 23:12:20

#350 Re: News & Announcements » Devuan Beowulf 3.1.0 point release » 2021-06-23 01:32:28

Board footer