You are not logged in.
Thank you for the suggestion to delete i586 (and i686) and have only i386 as a foreign architecture. That worked, the i386 library packages installed, and Applix works again (needed the libraries).
If that's the case, then why are there i386 ISOs here?
https://files.devuan.org/devuan_daedalus/installer-iso/
Running Devuan Daedalus and apt-cacher-ng, I'm not able to install 32-bit library packages (libx11-6:i586 for example).
Doing "dpkg --print-architecture" returns
amd64
Doing "dpkg --print-foreign-architectures" returns
i386
i586
These are the non-comment lines in /etc/apt/sources.list:
deb http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmware
Doing "apt-get update" returns
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' doesn't support architecture 'i586'
N: Skipping acquire of configured file 'contrib/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' doesn't support architecture 'i586'
N: Skipping acquire of configured file 'contrib/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' doesn't support architecture 'i586'
N: Skipping acquire of configured file 'non-free/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' doesn't support architecture 'i586'
doesn't support architecture 'i586'
N: Skipping acquire of configured file 'non-free/binary-i586/Packages' as repository 'http://127.0.0.1:3142/us.deb.devuan.org/merged daedalus InRelease' doesn't support architecture 'i586'
...
Any suggestions? Thanks in advance.
In case anyone with a similar question/problem finds this, there is another solution. I commented out the "tos minclock 4 minsane 3" line, and it appears to work fine now. I suspect if I had four individual servers declared in the file, I could have kept the "tos ..." line.
Since switching from Chimaera to Daedalus ~10 days ago, ntpsec shows it's contacting the servers, but the offset grows by a fraction of a second per day. It appears it's contacting the servers but not managing the drift, not controlling the clock.
The only changes I made from the Daedalus factory-supplied /etc/ntpsec/ntp.conf file is to comment out the pool entries and add two server entries in order to have consistency from one boot to the next. These are my server entries:
server time.cloudflare.com nts
server oregon.time.system76.com nts
Doing "ntpq -p" shows this about 3 days after running "ntpdig -S" and restarting ntpsec::
remote refid st t when poll reach delay offset jitter
===============================================================================
+time.cloudflare 10.119.8.155 3 8 33 64 377 10.5348 623.7458 0.5835
+oregon.time.sys 128.138.141.177 2 8 17 64 377 15.7338 627.3030 0.7425
Any suggestions to get ntpsec to put its hands on the steering wheel and drive?
Thanks for the suggestions. Environment variable $MORE is not set, and there is no alias set. If I do "date | /bin/more" (without the quotation marks), it clears the screen, prints one line of text at the top, and prints reverse-video "(END)" at the bottom. "dpkg -S /bin/more" says it comes from util-linux. "/bin/more --version" says, "more from util-linux 2.38.1".
Does 'more' have an antidote option to negate -p (and/or -c) in case that has (perhaps unintentionally) been made the default? No syntax for negating an option shows up in the man page or via "--help".
In daedalus, with util-linux 2.38.1, /bin/more with no options initially clears the screen before starting to print text. Based on over 40 years of using 'more', that is incorrect behavior--unless the -p or -c options had been supplied. If the binary is called as 'page' or if the -p option is supplied, it's supposed to clear the screen. In comparison, in chimaera, with util-linux 2.36.1, /bin/more with no options behaves correctly and does not initially clear the screen. A web search did not reveal any discussion of how to work around this broken behavior.
Is there an (undocumented) option to nix the initial clearing of the screen?
As a side note, there's also a bug introduced probably over a decade ago now where 'more' quit showing one overlapping line of text. If the binary is called as 'page', it's supposed to initially clear the screen and show zero overlap. If the binary is called as 'more' with no options, it is supposed to _NOT_ initially clear the screen and is supposed to show one line of overlap as it scrolls.
On Devuan 4 chimaera on amd64, using Firefox ESR, last night one of the pages to pay a Waste Management bill flashed/thrashed and did not load, and I was not able to pay the bill. Today, there was an update to 102.15.1esr-1~deb11u1. Just now, running the updated Firefox version, an Ebay page to show an order I had just placed flashed/thrashed several times and then sent me to a Captcha page. After correctly selecting the specified pages, the browser went back to flashing/thrashing and then to Captcha--rinse, repeat. Which combination of the following hypotheses is closer to correct:
- Firefox ESR has gone buggy and is no longer reliable
- Websites are (via malice or incompetence) punishing Firefox by making the sites not work with Firefox
- My social credit score is too low, so Firefox and/or the websites are punishing me
- (other)
Well, it looks like the system accepted the second report:
https://bugs.devuan.org/cgi/bugreport.cgi?bug=734
Thanks.
Tried to use the reportbug tool to send the bug report. The tool refused to send it. (I should submit bug reports against reportbug.) In the end, I manually edited the saved draft report and emailed it manually. After at least one automated rejection, I hope I can find a way to get the bug report filed.
Thanks for the replies/help. The full package list for testing shows 6.21.00-1.1, the same as I'm using on Chimaera. Oddly, the full package list for Chimaera doesn't show either csh or tcsh.
What would be the method to request a fixed version or a patch fix be considered to include in the next release? Would that have to go through Debian's wish-list request system?
Where should a serious tcsh globbing bug be reported? I'm running Devuan Chimaera with tcsh version 6.21.00-1.1.
In an empty directory, do these three commands:
touch {a,b,c,d,2}{1,2,3}
echo [a-d]*
echo [a-d]?
Each of the echo commands prints this (modulo indentation):
21 22 23 a1 a2 a3 b1 b2 b3 c1 c2 c3 d1 d2 d3
Each of the echo commands SHOULD print this (modulo indentation):
a1 a2 a3 b1 b2 b3 c1 c2 c3 d1 d2 d3
The man page says this about a hyphen between square brackets:
Within `[...]', a pair of characters separated by `-' matches any character lexically between the two.
"2" is _NOT_ lexically between "a" and "d". Therefore, the filenames that start with "2" should not be in the glob expansion.
This bug can result in files being deleted that should not have been deleted.
Thanks for the extremely quick reply! That appears to work for me, too.
Oh, as far as I'm aware, I'm using IPv4 exclusively. I disabled IPv6 during post-installation tuning.
It appears pkgmaster.devuan.org has quit serving chimaera updates. What is the recommended replacement?
When I installed chimaera last December, this line in the original /etc/apt/sources.list referred to pkgmaster:
deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
I'm using apt-cacher-ng, so I adapted it to this:
deb http://127.0.0.1:3142/pkgmaster.devuan.org/merged chimaera-security main contrib non-free
That had been working great through May 7. On May 14, 21, and 28 (today), I get this when attempting "apt-get update":
Hit:1 http://127.0.0.1:3142/deb.devuan.org/merged chimaera InRelease
Err:2 http://127.0.0.1:3142/pkgmaster.devuan.org/merged chimaera-security InRelease
Connection failed [IP: 127.0.0.1 3142]
Hit:3 http://127.0.0.1:3142/deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://127.0.0.1:3142/deb.devuan.org/merged chimaera-backports InRelease
Reading package lists... Done
W: Failed to fetch http://127.0.0.1:3142/pkgmaster.devuan. … /InRelease Connection failed [IP: 127.0.0.1 3142]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Is deb.devuan.org the recommended replacement for pkgmaster.devuan.org? Or, is there a different recommended replacement?
By way of follow-up, the Beowulf installation worked very well. Even with adding the MX AHS packages and then migrating at least some of them to backports (when backports had the newer versions available), I did not see any serious problems from mixing distribution packages. There was only one time in about 7 months that the machine crashed, apparently a GPU crash, and that was in August, 2021.
A few days ago, I installed Chimaera without any packages coming from MX or even backports. So far, everything appears to be working very well (modulo migrating all my home-grown Python code to Python 3). Graphics performance is excellent. At shadertoy.com, the 'tempting the mariner' page (with a warning, apparently about overheating systems) runs full 60fps in the small window and appears to do 20-30fps at full screen (1920x1200).
Thank you for all the help. After working through some odd issues (and a bug report about BIOS corrupting disk data), the machine just went into "production" use with a 5800 CPU, an ASUS Pro WS X570-ACE motherboard, a MSI Radeon RX 5500 XT GAMING X graphics card, Devuan Beowulf, the kernel from backports, AMD graphics and Realtek firmware from backports, some other packages from backports that apparently got pulled in as dependencies, and the Mesa and related libraries from MX AHS. The MX AHS packages were mentioned in these linkded pages: https://dev1galaxy.org/viewtopic.php?id=3913 and http://forums.debian.net/viewtopic.php?f=16&t=146083 So far, everything appears to be working well.
It appears when I installed the backports 5.10 kernel that I used the meta package. This is what 'dpkg -l' says for it:
ii linux-image-amd64 5.10.13-1~bpo10+1 amd64 Linux for 64-bit PCs (meta-package)
Again, thank you both for the very helpful guidance.
Thanks for the great info about the meta package. During installation, I just followed the default path. Now that I know about the meta package structure, I'll make sure to install the meta package from backports.
Excellent! Thank you very much!
That's a very good point. Thank you for suggesting the 5.10 LTS branch from the beowulf-backports repository. So far, today's current 5.10 kernel from beowulf-backports appears to be working well. I partitioned the big HDDs and created the RAIDs. The big RAID is doing its initial sync as I type (and for the next ~4+ hours).
I did a web search or two about how to add a backports repository. One thing was not clear from the relevant web pages those searches found. Does apt-get pick up updated kernel packages from backports automagically? When I tried "apt-get -d -t beowulf-backports update", it wanted to update an enormous boatload of things, which I immediately rejected. (Packages from the stable, non-backports repositories had already been fully updated.)
Thank you both for those very helpful answers. In case it might help someone else who might happen upon this thread:
After a long wait for the CPU (and some problems with a now-EOL SAS/SATA card) the machine is running. (I had wanted a 5900X CPU, but it's still not in stock anywhere at a price even close to list.) With a temporary (2200G) CPU, I upgraded the motherboard's BIOS to a version that supports the 5800X CPU. That temporary CPU also allowed testing of some other issues. I installed Beowulf with the temporary CPU.
For the kernel, I downloaded the 5.11.2 source from kernel.org to my old machine, ran "make oldconfig" based on the config file from the stock Beowulf kernel (accepting the defult for all questions), cleared the value of CONFIG__SYSTEM_TRUSTED_KEYS, ran "make -j 6 bindeb-pkg", waited an hour for the build to finish, installed three DEBs (not the one with "dbg" in its name), installed the 5800X CPU, and booted it up. So far, so good on the kernel.
Getting the GPU up to speed is still pending--one step at a time.
What AMD graphics card (up to US$250 price) will work with Beowulf?
I'm preparing to build a new system with an Asus Pro WS X570-ACE motherboard and either a 9 5900X or a 7 5800X CPU, with Devuan Beowulf as its first OS. I plan to use open-source drivers, so I'm avoiding the 'PRO' cards. After considerable searching, I have yet to find a cross-reference that says what AMD GPUs work with what version of kernel, xorg, etc. Any pointers or suggestions?
Thanks,
Robert
On a Devuan Ascii system, what is the package that installs the /etc/init.d script for libvirtd? Is it libvirt-daemon-system, or is it libvirt-daemon-system-sysv?
Thanks,
Robert
I found the reason for my case of not getting updates. My /etc/apt/sources.list had originally only listed the cdrom (well, actually DVD to be more precise) as sources. That's likely a side effect of not configuring the network in the installer. When I noticed a Raspberry Pi 3 running Devuan Ascii was getting updates that my main X86 system was not getting, investigation yielded that the Raspberry Pi's /etc/apt/sources.list had separate lines for "ascii", "ascii-updates", and "ascii-security" (along with a commented-out line for "ascii-backports"). After changing my /etc/apt/sources.list to mimic the one on the Raspberry Pi, I had ~164MB of updates to download, including Firefox 60.6.1esr.