- This topic has 320 replies, 28 voices, and was last updated May 11-8:42 pm by Wallon.
-
Posts
-
Brian Masinick
I installed and performed basic tests on all of the applications in the Children’s Category, which shows up in “Education” on the menu. All of the programs install and all of them start up. I did not check every possible action in each program, but having learned from just starting and removing apps that there’s more needed, I made sure they all execute and I tried one or two capabilities in each game. One of them took me a minute or two to navigate, so that one got a medium level of testing! 😉 That category passes beta testing.
Hopefully as we test we’ll find a few people who regularly use the programs in various categories and every app will ultimately get much more in depth test coverage in addition to install, enable, disable and remove. The apps I use every day I’m definitely testing and I always do. They tend to be close to defect free because when I find defects in an app that I use daily, I report and provide feedback, and retest when the defect is fixed, so I definitely do functionality, performance and usability testing on quite a few apps throughout their lifecycle.
Anyway, Check off the Children’s category for installation tests in this cycle.
--
Brian Masinickcalciumsodium
Please check whether the devices
/dev/ttyS0 /dev/ttyUSB0are present for you.
The ttyS0 device is present, even though there is no getty-ttyS0 startup is not present.
Please see attached screenshot.Attachments:
Brian Masinick
I have also installed SeaMonkey, Chromium, and Vivaldi in the Browser category; only a couple of browsers I haven’t installed during Beta 1.
--
Brian MasinickQwerty
Dynamic persistence, semi-automatic, restart initiated from the console:
/usr/local/lib/antiX/antiX-gui-cli.sh: line 523: read: read error: 0: Bad file descriptor
Synchronization proceeds with the default answer automatically.live-umount:
`pgrep: pattern that searches for process name longer than 15 characters will result in zero matches
Trypgrep -f' option to match against the complete command line.I didn’t notice any consequences, but it seems that some processes can be killed when they shouldn’t or vice versa.
(What’s the right way to escape backticks inside code blocks here?..)- This reply was modified 1 month, 2 weeks ago by Qwerty.
- This reply was modified 1 month, 2 weeks ago by Qwerty.
- This reply was modified 1 month, 2 weeks ago by Qwerty.
Brian Masinick
Back on my HP-14 where I can test faster, I was able to test 3 of the 4 entries in the LaTeX category, all except for LaTeX-Kile; the other editor works fine, LaTeX-Texmaker. I went into the editor and clicked on a few items to make sure it’s working.
--
Brian Masinick
marcelocripe
Package “snes9x_1.53-1_amd64.deb” is not an official Debian, antiX or MX Linux package, it has been repackaged from PCLinuxOS package “snes9x-1.53-1pclos2015.x86_64.rpm”. It depends on the libxml2 (>= 2.0) and libpng12-0 (>= 1.2) packages and works perfectly fine on antiX 21/22, as can be seen with the “$ apt show snes9x” command:
demo@antix1:~/Downloads
$ apt show snes9x
Package: snes9x
Version: 1.53-1
Status: install ok installed
Priority: optional
Section: game
Maintainer: Brandon Wright (bearoso) <bearoso@gmail.com>
Original-Maintainer: Gary Henderson <gary@snes9x.com>
Installed-Size: 6.767 kB
Depends: libxml2 (>= 2.0), libpng12-0 (>= 1.2)
Homepage: https://sites.google.com/site/bearoso/ and https://www.snes9x.com/
Packager: marcelocripe <marcelocripe@gmail.com>
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Super Nintendo Emulator or Super NES Emulator or Super Famicom Emulator
Snes9X is a portable, freeware Super Nintendo Entertainment System (SNES)
emulator. It basically allows you to play most games designed for the SNES
and Super Famicom Nintendo game systems on your PC or Workstation.
.
Note: The ‘snes9x_1.53-1_amd64.deb’ package was based on the ‘snes9x-1.53-
1pclos2015.x86_64.rpm’ package from the PCLinuxOS BR community that can be
downloaded from the website:
.
https://ftp.sjtu.edu.cn/sites/www.pclinuxos.com/pclinuxos/apt/pclinuxos/
64bit/RPMS.x86_64/snes9x-1.53-1pclos2015.x86_64.rpm.demo@antix1:~/Downloads
$The “libxml2” package is already available in the “antiX-23-beta1-runit_x64-full.iso” ISO, but apparently the “libpng12-0” package cannot be installed.
demo@antix1:~/Downloads
$ sudo apt install ‘/home/demo/Downloads/snes9x_1.53-1_amd64.deb’
Reading package lists… Done
Building dependency tree… Done
Reading status information… Done
Note, selecting ‘snes9x’ instead of ‘/home/demo/Downloads/snes9x_1.53-1_amd64.deb’
Some packages could not be installed. This could mean that
you requested an impossible situation or, if you are using the
unstable distribution, that some required packages were not
created yet or removed from “Incoming”.
The following information may help resolve the situation:The following packages have mismatched dependencies:
usr-is-merged : Conflicts: libpng12-0 (< 1.2.54-6~) but 1.2.54-1.0antix1 is to be installed
usrmerge : Conflicts: libpng12-0 (< 1.2.54-6~) but 1.2.54-1.0antix1 is to be installed
E: Error, pkgProblemResolver::Resolve failed, this could be caused by packages being held.
demo@antix1:~/Downloads
$Where am I going with this story?
The “libpng12-0” package is a dependency for several other programs and not just for Snes9x. Would it be a problem if “usr-is-merged” and “usrmerge” conflict with “libpng12-0”?
I have some totally out of context questions regarding testing antiX 23:
How can I describe in the package name the version of antiX that the package supports?
Would it be like this: would “snes9x_1.53-1_amd64.deb” become “snes9x_1.53-1_antiX-22_amd64.deb” or “snes9x_1.53-1_antiX-23_amd64.deb”?
– – – – –
O pacote “snes9x_1.53-1_amd64.deb” não é um pacote oficial do Debian, antiX ou MX Linux, foi reempacotado a partir do pacote “snes9x-1.53-1pclos2015.x86_64.rpm” do PCLinuxOS. Ele depende dos pacotes libxml2 (>= 2.0) e libpng12-0 (>= 1.2) e funciona perfeitamente bem no antiX 21/22, como pode ser observado com o comando “$ apt show snes9x”:
demo@antix1:~/Downloads
$ apt show snes9x
Package: snes9x
Version: 1.53-1
Status: install ok installed
Priority: optional
Section: game
Maintainer: Brandon Wright (bearoso) <bearoso@gmail.com>
Original-Maintainer: Gary Henderson <gary@snes9x.com>
Installed-Size: 6.767 kB
Depends: libxml2 (>= 2.0), libpng12-0 (>= 1.2)
Homepage: https://sites.google.com/site/bearoso/ and https://www.snes9x.com/
Packager: marcelocripe <marcelocripe@gmail.com>
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Super Nintendo Emulator or Super NES Emulator or Super Famicom Emulator
Snes9X is a portable, freeware Super Nintendo Entertainment System (SNES)
emulator. It basically allows you to play most games designed for the SNES
and Super Famicom Nintendo game systems on your PC or Workstation.
.
Note: The ‘snes9x_1.53-1_amd64.deb’ package was based on the ‘snes9x-1.53-
1pclos2015.x86_64.rpm’ package from the PCLinuxOS BR community that can be
downloaded from the website:
.
https://ftp.sjtu.edu.cn/sites/www.pclinuxos.com/pclinuxos/apt/pclinuxos/
64bit/RPMS.x86_64/snes9x-1.53-1pclos2015.x86_64.rpm.demo@antix1:~/Downloads
$O pacote “libxml2” já está disponível na ISO “antiX-23-beta1-runit_x64-full.iso”, mas ao que parece o pacote “libpng12-0” não pode ser instalado.
demo@antix1:~/Downloads
$ sudo apt install ‘/home/demo/Downloads/snes9x_1.53-1_amd64.deb’
Lendo listas de pacotes… Pronto
Construindo árvore de dependências… Pronto
Lendo informação de estado… Pronto
Note, a seleccionar ‘snes9x’ em vez de ‘/home/demo/Downloads/snes9x_1.53-1_amd64.deb’
Alguns pacotes não puderam ser instalados. Isto pode significar que
você solicitou uma situação impossível ou, se você está usando a
distribuição instável, que alguns pacotes requeridos não foram
criados ainda ou foram retirados da “Incoming”.
A informação a seguir pode ajudar a resolver a situação:Os pacotes a seguir têm dependências desencontradas:
usr-is-merged : Conflita: libpng12-0 (< 1.2.54-6~) mas 1.2.54-1.0antix1 está para ser instalado
usrmerge : Conflita: libpng12-0 (< 1.2.54-6~) mas 1.2.54-1.0antix1 está para ser instalado
E: Erro, pkgProblemResolver::Resolve gerou falhas, isto pode ser causado por pacotes mantidos (hold).
demo@antix1:~/Downloads
$Onde eu quero chegar com este relato?
O pacote “libpng12-0” é uma dependência para vários outros programas e não somente para o Snes9x. Isso seria um problema o “usr-is-merged” e o “usrmerge” conflitarem com o “libpng12-0”?
Eu tenho algumas perguntas totalmente fora do contexto referentes aos testes do antiX 23:
Como eu posso descrever no nome do pacote a versão do antiX que o pacote é compatível?
Seria assim: “snes9x_1.53-1_amd64.deb” passaria para “snes9x_1.53-1_antiX-22_amd64.deb” ou “snes9x_1.53-1_antiX-23_amd64.deb”?
christophe
My observations so far:
I installed to a Core2Duo from 2007 – will boot the 6.1 kernel, but it still suffers from the two-minute blank screen wait, during the kernel loading (and the live usb still loads that same kernel in about 5 seconds total). The 5.10 kernel boots normally on the installed system & live.
No trash can on default desktop after install.
The number of icewm desktops can be changed from the icewm manager, but they aren’t permanent. (Brian mentioned this earlier, too).
I lose conky at odd times on the zzz-icewm desktop. I can restart it by hitting conky on/off toggle from the menu twice, but on this desktop session, closing a terminal (for example) would kill (or perhaps hide) it again. If I switch to rox-icewm, conky behaves normally in that desktop session.
So far, everything else has been working perfectly (except some package-installer issues, which you mentioned most-likely would exist).
confirmed antiX frugaler, since 2019
Robin
Hello Marcelo,
How can I describe in the package name the version of antiX that the package supports?
I’m not familiar with packaging at all, but the architecture is set within the package /DEBIAN/control file rather than by appending it to the package name. You can allow two different versions of a package in the depends line by adding a logical or condition making it work for both antiX versions.
Example from hexchat-encrypt-translate package:
… Depends: openssl (>= 1.1.1d-0), pwgen (>= 2.0.8-1), hexchat (>= 2.14.2-4), hexchat-python2 (>= 2.14.2-4) | hexchat-python3 (>= 2.14.2-4), hexchat-plugins (>= 2.14.2-4), translate-shell (>= 0.9.6.11) …As you can see, for this package either the hexchat-python3 package or hexchat-python2 package, both in versions starting from 2.14.2.4 will meet the dependency, so it the package can get installed on antiX 17/19 as well as on 21/22/23. Hexchat itself supports python2 on antiX 17/19 versions and python3 on antiX 21/22/23 versions, so this differenciation in the depends line is needed here.
As this is all I know about that by now, hopefully somebody experienced with packaging will append some more enlightening words about this which will solve your case.
Many greetings
RobinWindows is like a submarine. Open a window and serious problems will start.
Obs: Automatic switching from normal time to summertime (you call it daylight saving time / BST or DST) works properly on antiX 23. Clock in lower right corner shows now 6:18 (would have been 5:18 in normal time) in the morning, while I’ll have to move my analog clocks manually. (fine also on antiX 22), while the forum time is 4:18 UTC.
Windows is like a submarine. Open a window and serious problems will start.
Brian Masinick
Obs: Automatic switching from normal time to summertime (you call it daylight saving time / BST or DST) works properly on antiX 23. Clock in lower right corner shows now 6:18 (would have been 5:18 in normal time) in the morning, while I’ll have to move my analog clocks manually. (fine also on antiX 22), while the forum time is 4:18 UTC.
Good point, one I’ve apparently taken for granted. Any time I want or need to correct the time, our handy date/time update tool corrects any inconsistencies between local time, UTC, DST, EST, EDT, etc. That’s never been an issue in any build of antiX I’ve ever noticed; still, it’s a good point; it works properly.
--
Brian Masinickchristophe
I lose conky at odd times on the zzz-icewm desktop. I can restart it by hitting conky on/off toggle from the menu twice, but on this desktop session, closing a terminal (for example) would kill (or perhaps hide) it again. If I switch to rox-icewm, conky behaves normally in that desktop session.
Switching to zzz-jwm desktop, I assumed I would see the same behavior with conky. But it is normal (no issues).
confirmed antiX frugaler, since 2019
vitforlinux
I’m using Antix runit 23 alpha1 on a recent computer, but on other partitions I have other Gnu/Linux distros, and I must say that Antix runit 23 is the best, it will be out of habit, but I’m happy with it.
Some programs don’t work, but mostly because it’s not compiled for Debian 12, and it doesn’t have the right dependencies.
A big thank you.
Sorry for my spaghetti english, i'm italian.
Brian Masinick
I’m using Antix runit 23 alpha1 on a recent computer, but on other partitions I have other Gnu/Linux distros, and I must say that Antix runit 23 is the best, it will be out of habit, but I’m happy with it.
Some programs don’t work, but mostly because it’s not compiled for Debian 12, and it doesn’t have the right dependencies.
A big thank you.
I can’t lose; I put antiX 23 Beta 1 on four different systems of various ages and types and it worked well on all of them. What also made me happy was that the Version 6.1.18 kernel worked well on all of them.
Today I’m taking a break from testing the Beta 1 release and I’m back with my stable antiX 22 system on my HP-14. The only difference is that I have a combination of different kernels here, ranging from the antiX kernel to the Liquorix and xanmod1 kernels.
Our antiX kernels are great; between the older ones that can truly support ancient systems, at least up to our antiX 22 release, all the way up to our newest Version 6 kernels, they are all very solid and work fine.
I will say that they are general purpose, every day kernels, particularly intended for lean efficiency in every way.
I have found on newer, higher performance systems that it’s possible to gain some small performance gains due to the way that a few modern kernels retain more cache memory, making it possible to retain a pretty sizable workload, including Web browsers, active in memory. That’s the only area where the “high performance” stuff uses more resources to provide increased speed. Frankly it’s not very large, but it provides just a little extra “snappiness” in systems 1-3 years old. That’s the only “advantage” I see of one thing over another. What antiX very clearly gains with it’s approach is efficient memory utilization, regardless of the age of the equipment, and conservation of space whenever possible.--
Brian MasinickBrian Masinick
I lose conky at odd times on the zzz-icewm desktop. I can restart it by hitting conky on/off toggle from the menu twice, but on this desktop session, closing a terminal (for example) would kill (or perhaps hide) it again. If I switch to rox-icewm, conky behaves normally in that desktop session.
Switching to zzz-jwm desktop, I assumed I would see the same behavior with conky. But it is normal (no issues).
I did not exercise all of the tools when I switched to the different window managers, but I did run enough of each of them to verify that each of them still perform their essential service as a window manager.
I did modify the workspaces a bit when I worked with Fluxbox and I did a few similar things with jwm; I was using herbs WM near the end of my work and didn’t check out many capabilities, (I figure that anticapitalista has that one well covered because I think he prefers it).
I’ve been quite pleased with the majority of things I have tested; while there are a few fixes and some minor defects the core functionality is already pretty solid.
--
Brian MasinickThat’s never been an issue in any build of antiX I’ve ever noticed
I had issues with this in antiX 17.4.1 live, the system clock was moved an hour more than once on each next reboot, causing the clock showing 2, 3, 4, 5 hours wrong after some reboots on the switching day. But neither on 19, 21/22 nor on 23 I’ve seen this issue anymore.
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
