You are not logged in.
* If you used https:// before, please change to http://.
Noted. I changed my sources.list from HTTPS to HTTP and I confirm package updates work correctly now with deb.devuan.org URL.
This, to a degree, is not secure/private.
Is there any plan to ever make HTTPS round-robin work with all mirrors?
Why is pkgmaster.devuan.org allowing connections from non-mirrors (e.g. clients)?
Isn't there or shouldn't be a kind of mirror registration process that would additionally check the quality of mirror configuration (e.g. certificate)?
I get an error when I switch to deb.devuan.org. It seems besides country codes not working properly so do some of the mirrors...
That was the reason I switched back to pkgmaster.devuan.org at some point in the past.
My sources.list entries:
# Devuan repositories
deb https://deb.devuan.org/merged ascii main
deb https://deb.devuan.org/merged ascii-security main
deb https://deb.devuan.org/merged ascii-updates main
#deb https://deb.devuan.org/merged ascii-backports main
# Devuan sources
deb-src https://deb.devuan.org/merged ascii main
deb-src https://deb.devuan.org/merged ascii-security main
deb-src https://deb.devuan.org/merged ascii-updates main
#deb-src https://deb.devuan.org/merged ascii-backports main
Result of apt-get update:
Ign:28 https://deb.devuan.org/merged ascii-security i386 Contents (deb)
Err:29 https://deb.devuan.org/merged ascii-updates/main Sources
SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
Ign:30 https://deb.devuan.org/merged ascii-updates/main i386 Packages
Ign:31 https://deb.devuan.org/merged ascii-updates/main all Packages
Ign:32 https://deb.devuan.org/merged ascii-updates/main amd64 Packages
Ign:33 https://deb.devuan.org/merged ascii-updates/main Translation-en
Ign:34 https://deb.devuan.org/merged ascii-updates/main i386 Contents (deb)
Ign:35 https://deb.devuan.org/merged ascii-updates/main all Contents (deb)
Ign:36 https://deb.devuan.org/merged ascii-updates/main amd64 Contents (deb)
Ign:37 https://deb.devuan.org/merged ascii-updates i386 Contents (deb)
Ign:38 https://deb.devuan.org/merged ascii-updates amd64 Contents (deb)
Ign:39 https://deb.devuan.org/merged ascii-updates all Contents (deb)
Reading package lists... Done
W: The repository 'https://deb.devuan.org/merged ascii Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://deb.devuan.org/merged ascii-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://deb.devuan.org/merged ascii-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii/main/source/Sources SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii-security/main/source/Sources SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii-updates/main/source/Sources SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Some index files failed to download. They have been ignored, or old ones used instead.
How did you conclude these printers showing up are Bluetooth and not WiFi printers?
Without bluez installed, I do not think any user-space utility will pick up any bluetooth device.
Try reconfiguring avahi or uninstalling the
avahi-daemon
package or disabling the service..
Hi both.
Please also take a look at this thread in this forum for guidance:
https://dev1galaxy.org/viewtopic.php?id=589
It all depends on your skills and desires. Contributing to documentation is a good idea for a newbie without any technical/programming skills.
@mmaglis
I thought I made it clear that I was not using Bluetooth and wanted to keep it that way.
What you made clear is that you did not want to use Bluetooth but did not succeed.
That is why I asked how you try to control/switch off your Bluetooth devices among other things.
My main point is that if you do not provide exact details of your setup, you can only expect vague suggestions.
If you want to permanently disable Bluetooth, you either do it by disabling (e.g. in BIOS) or removing the hardware or by removing Bluetooth kernel module, or by removing service packages like bluez and dependencies, or by reconfiguring your user-space utility that tries to control all the above.
Removing the bluez packages might work for you.
I suggest you monitor your system logs for attempts to activate or access the Bluetooth device.
For someone to help, you need to provide specific information:
Basic hardware specification. E.g. laptop model, Bluetooth device models
Devuan version installed, with install options
List of running services and how you control your Bluetooth devices
Any modifications to default configuration of any software
i would love a little tutorial for dbus-free devuan.
These may be of help:
https://devuan.org/os/documentation/dev … thout-dbus
https://devuan.org/os/documentation/dev … e-software
I followed them and I am dbus free, happily using either console, Openbox, EXWM or Stumpwm on my aged laptop.
I cannot recall in which order I have purged various packages.
I do know xserver-xorg-legacy was purged last.
I do not think the order is important though.
I startx from console as a normal user.
xinit and Xorg processes run with that normal user.
I have currently the below packages installed; no polkit, no logind, only libdbus:
- libpam0g
- libpam-runtime
- libpam-modules
- libpam-modules-bin
- xorg
- xserver-xorg
- xserver-xorg-core
- xserver-xorg-input-libinput
- xserver-xorg-input-void
- xserver-xorg-video-dummy
- xserver-xorg-video-intel
- xserver-xorg-video-vesa
- x11-xserver-utils
- xserver-common
- login
- eudev
- libdbus-1-3
My apt sources.list point to ASCII:
# Devuan repositories
deb https://pkgmaster.devuan.org/merged ascii main
deb https://pkgmaster.devuan.org/merged ascii-updates main
deb https://pkgmaster.devuan.org/merged ascii-security main
deb https://pkgmaster.devuan.org/merged ascii-backports main
I am running Devuan ASCII. I had the xserver-xorg-legacy installed so far, but decided to remove it and see if things work without it.
They do! I startx from console as normal user. xinit & Xorg run as normal user.
No elogind, no polkit, no dbus here.
No issue.
I have not tried it with a display manager (e.g. slim) yet.
Have things changed recently?