Search Results for 'core kde'

[Moderator Brian Masinick]

Anonymous wrote:

great work on the 19.3 dev team,

the only issue I had was already mentioned previously by xinomilo

– cli-installer :
1) missing partition-info package (not installed in iso)

I partition my disk and write down before running the installer so
no biggie. I am using the 64 bit 19.3 core sid-runit and built up
to run wayland with sway and kittyterm so far is working great as
I am learning sway, wayland and different ways to build up the rice
desktops. this is on a hp pavillion g6 laptop 8gb ram and amd dual core.

Good idea!

It’s been several years since I’ve worked extensively with Core. I used it often about a decade ago when MEPIS used KDE. My antiX Core custom made system was a minimal Xfce desktop environment with just the minimum Xfce packages and only the applications that I used at the time.

I’ll do something like that again using a different environment and replace one of the distros that I am tired of using.

Thanks for the”inspiration”!

--
Brian Masinick

[Member marcelocripe]

Olá PPC,

Eu agradeço por mais este importante tópico e pelas alterações e melhorias no “lixeira.desktop” ou “reciclagem.desktop”.

Apenas uma pequena alteração no diretório onde o ícone da Lixeira/Reciclagem está localizado, ambos funcionam, mas é preferível usar o Icon=/usr/share/icons/papirus-antix/48×48/apps/trashindicator.png.

Alterar: Icon=/usr/share/icons/papirus-antix/48×48/categories/trashindicator.png
Para: Icon=/usr/share/icons/papirus-antix/48×48/apps/trashindicator.png

Conforme segue abaixo:

[Desktop Entry]
Version=1.0
Name=Trash
Name[pt]=Reciclagem
Name[pt_BR]=Lixeira
Categories=System;FileTools;Utility;Core;GTK;FileManager;
Exec=spacefm ~/.local/share/Trash/files/ %F
Icon=/usr/share/icons/papirus-antix/48×48/apps/trashindicator.png
StartupNotify=true
Type=Application
Terminal=false
MimeType=inode/directory;inode/mount-point;x-scheme-handler/ssh;x-scheme-handler/smb;x-scheme-handler/nfs;x-scheme-handler/ftp;x-scheme-handler/ptp;x-scheme-handler/mtp;x-scheme-handler/webdav;x-scheme-handler/http;x-scheme-handler/https;
X-KDE-Protocols=ftp,smb,ssh,ptp,mtp,nfs,webdav,http,https
GenericName=Trash
GenericName[pt]=Reciclagem
GenericName[pt_BR]=Lixeira
Comment=Trash can
Comment[pt]=Ficheiros removidos para a Reciclagem
Comment[pt_BR]=Arquivos removidos para a Lixeira
Keywords=file;manager;file-manager;

Envio “lixeira.desktop” e “reciclagem.desktop”, os arquivos/ficheiros são idênticos, apenas o nome do ícone que são diferentes. Por tanto, quem tiver interesse em baixar/tranferir o ícone pronto precisará baixar apenas um dos arquivos.

Obrigado.

marcelocripe

[Member PPC]

Se por algum motivo a pasta trash não for criada e não fique disponível, tente isto:
1- Menu > Terminal
2-
mkdir -p ~/.local/share/Trash/files/
3- pode fechar o terminal

O Marcelocripe criou o ficheiro .desktop para a “lixeira”, que muito gentilmente me disponibilizou.
Eu adaptei-o um pouco. Uma vez criado e movido para a pasta applications, ele permite que a pasta da “lixeira” fique disponível no menu e, inclusive, seja possível de ser selecionada para surgir na barra do IceWM…

[Desktop Entry]
Version=1.0
Name=Trash
Name[pt]=Reciclagem
Name[pt_BR]=Lixeira
Categories=System;FileTools;Utility;Core;GTK;FileManager;
Exec=spacefm ~/.local/share/Trash/files/ %F
Icon=/usr/share/icons/papirus-antix/48x48/categories/trashindicator.png
StartupNotify=true
Type=Application
Terminal=false
MimeType=inode/directory;inode/mount-point;x-scheme-handler/ssh;x-scheme-handler/smb;x-scheme-handler/nfs;x-scheme-handler/ftp;x-scheme-handler/ptp;x-scheme-handler/mtp;x-scheme-handler/webdav;x-scheme-handler/http;x-scheme-handler/https;
X-KDE-Protocols=ftp,smb,ssh,ptp,mtp,nfs,webdav,http,https
GenericName=Trash
GenericName[pt]=Reciclagem
GenericName[pt_BR]=Lixeira
Comment=Trash can
Comment[pt]=Ficheiros removidos para a Reciclagem
Comment[pt_BR]=Arquivos removidos para a Lixeira
Keywords=file;manager;file-manager;

Para usar o ficheiro simplesmente abra um um editor de texto ( como o featherpad) copie o texto acima e cole-o lá, gravando-o com um nome como “lixeira.desktop”, directamente na sua pasta Home, e faça o seguinte procedimento:

1- Menu > Terminal
2-

sudo cp ~/lixeira.desktop  /usr/share/applications/
[introduza a password, se tal lhe for pedido]
sudo desktop-menu --write-out-global

(explicação: o primeiro comando copia o ficheiro para a pasta applications, onde são guardados os ficheiros .desktop de praticamente tudo o que tem no seu sistema e o segundo comando actualiza o menu, para surgir de imediato o ícone lá).
3- Poderá fechar o Terminal

P.

• This reply was modified 2 years, 7 months ago by PPC.
• This reply was modified 2 years, 7 months ago by PPC.
• This reply was modified 2 years, 7 months ago by PPC.

[Member Xecure]

antiX core has no GUI (it is all terminal).
You must first decide what you want to install and start building from there.

Look at this thread, for example, to learn how to build antix+fluxbox from scratch using core.
https://www.antixforum.com/forums/topic/dolphin-oracle-antix-core-custom-install-videos/
Or antix core + KDE:
https://www.antixforum.com/forums/topic/antix-19-1-core-kde-plasma-build-series/

Decide for yourself what you want to build and go step by step.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

marcelocripe wrote:

Test with Google Chrome, using the default settings of “my-offline-repo0103-1.zip”, 52 downloaded “.deb” packages, failed right after I selected REPO google_chrome and clicked Ok, RoxTerm opens and closes quickly.

Please read my previous post:

Xecure wrote:

There was a problem downloading google-chrome […] the main culprit is the exclude.list file (it excluded libcups2 package, and it seems chrome and gimp need it).
If you change the contents of the exclude.list for the one in 19.2core-exclude (delete all text inside exclude.list, copy all content from 19.2core-exclude file, and paste it inside exclude.list and then save the file), the number of dependencies becomes larger but there are no install problems.

About your other errors:

marcelocripe wrote:

kget
kdenlive
kodi

You forgot to Remove repo from list (Remover o repo da lista) before starting to download again.
Tomorrow i think I will have the next version available.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator Brian Masinick]

While true “unstable” rolling release distributions really are not for the beginner, they are not anywhere near as “unstable”, in terms of entire system failures as you may think, based on the name. They are “unstable” because there is nearly continual change.

In the early 2000s, right after I finished a graduate degree, I went into Linux system testing wholeheartedly, grabbed some Debian systems and really went at it.
By mid to late 2001 I had a solid implementation of Debian Sid. One of my earliest Sid implementations came from a Debian derivative featuring Sid – sidux, and another one I used, either in Testing or Sid mode was Libranet, plus I also had a pure Debian Sid instance. I took the time and effort to learn their packaging well and to update them on an almost daily basis. Chances are this is NOT what a “casual” user would do whether they have prior Linux experience or not.

When MEPIS came out in the 2003 timeframe I added it to my regular mix. In 2004 Simply MEPIS, a stable, easy to use KDE-based desktop system was introduced. I used that as my every day “stable” system. Within another 1-2 years antiX came out, and by 2006 it was a distribution with it’s own release cycle. As mentioned earlier, at first antiX used Testing repositories in order to get more frequent software updates.

I did NOT have ANY issues with any of these systems, even the “unstable” Sid-based versions. I ran several of them for years without reinstalling them.
Later, antiX came out with a Core version. I built mine from scratch and I chose Sid repos. Until I tore down and disposed of all of my 32-bit laptops, antiX ran on all of them. It was one of only a few distributions that continued to work because 32-bit support gradually eroded and by then I had my 64-bit Dell Inspiron 5558. If I didn’t clean house in order to move to a smaller home, I may still have those old boxes; they worked fine.

What I am getting at is this:
1. Running Testing or Sid is for those who want more current software.
2. The technique of changing to Testing or Sid is not particularly difficult; those who do not understand should either choose to learn or stick with something they can easily handle.
3. Testing and Sid don’t contain junk software. The software works. In the Debian way of doing things, packages in Debian Stable have undergone three cycles of testing – early testing in Sid, rigorous testing with metrics and defect resolution measures to determine readiness, and final release testing, where only minor, non-critical defects are allowed to remain. So the designations in Debian pertain to the testing cycles. The applications included have already been released by their application teams. In Debian, because of the many hardware architectures it supports. packages in certain hardware groups build readily, but are challenging in others, hence the levels of testing.

Veteran software builders can happily use any of these software build streams. People who just want something to click, install and work are welcome to experiment, but most will prefer to use something either easily understood that is a drop in installation, or even a pre-built system.

--
Brian Masinick

[Moderator Brian Masinick]

I can understand the variations between GNOME, KDE, and Xfce – three of the original major desktop environments.
The first versions of these started under THREE completely different licenses. KDE and Xfce actually got a slight start before GNOME really got off the ground, and so neither of them initially used the GPL, the GNU General Public License (all three now have provisions through that license. Xfce switched midway through its third major release to use Gtk, the same toolkit that GNOME uses, but it does things differently, a bit simpler and lighter than GNOME.

Both GNOME and KDE use a reasonably full-featured object-oriented architecture – at least the originals did – and the current versions are quite different than the very first ones. KDE got really big for a while, and it is still fairly large, but the most recent implementation does not “consume” all resources unless they are used by the objects and programs that are invoked. I’ve really not looked at GNOME at all in recent years. I’ve generally used either a light implementation of Xfce, and often I do without that; simple cut and paste is enough “value” for me, so I can use light stuff like IceWM.

Interestingly enough, I am playing with KDE today – first with a recent release of KDE Neon, and now with the recent MX Linux KDE 19.2. With KDE and the Chromium Web browser and two tabs open, plus konsole to display htop, I’m consuming 1.37 GB, a whopping amount, given my modest needs, and that’s why I don’t use these powerful desktop environments much. Though I have 8 GB of available memory that does not mean I have to try to use it every time I’m logged in, only if I am doing memory intensive or CPU intensive work do I ever “tax” my system with my resource usage.

More directly to the topic you raised, yes, it may be worth having 3-5, or perhaps even ten varieties of browsers, desktop or window managers, and a few variations to allow experimentation. We see that we actually have four current variations of antiX at the packaging level: net, core, base, and full, plus we offer variations with Sid, Testing, and the current release. It’s not difficult to see how we end up with so much variation across distributions, but you do make a point: with a bit of coordination, perhaps we could have three or four desktop variations, three or four window managers, three or four packaging styles, and then collaborate a bit so that, yes, we could have hundreds of variations and permutations, just with a few of these in different combinations.

I doubt that we could cut the number of distributions WAY down, but it would be nice if more development teams either contributed to one or more of these areas: application software, system configuration tools, desktop widgets or window management infrastructure, or packaging. I’m sure that there is some sharing that already takes place – we receive code from Debian and Devuan at the distro level, and we have used a variety of applications from various sources over the years. I hope that we have shared feedback, defect reports, and possibly bug fixes or new modules of code. Maybe there is more of that going on than the average person realizes. Most distributions are 90% packaging as far as each team’s effort, but an equal 90% of the stuff going into the software is common code that hundreds of distributions already share – such as Firefox or Chromium code, Thunar or Rox file manager, etc.

So there IS a lot of application and infrastructure sharing, and the kernel code is most definitely shared too.

--
Brian Masinick

Was hoping to get some help with this here.

A MX-KDE install I am unable to adjust the display brightness. And the brightness app crashes when I try to launch it.

However, with MX-Xfce the brightness app does launch and does control the display brightness.

The computer is a old MacBook Pro with a Nvidia graphics card
CPU: Core2 Duo
Graphics module is nouveau
Interesting note is that /sys/class/backlight is empty for both Xfce and KDE.

Thanks for the help

[Moderator Brian Masinick]

fatmac wrote:

I think that was my first experience of Linux, Zipslack 8, … Debian won, been with it in various forms ever since, mainly #! (Crunchbang), then AntiX, when #! demised. 🙂

I’ve tried a few other distros along the way, especially when I started back in 1999, but the ease of apt-get kept me with a Debian based distro.

I didn’t do much with Debian for the first five years or so that I used Linux. At first I didn’t have a high speed network. I got high speed in 1999 and started graduate school (WAY after undergraduate degree). So I didn’t start with Debian until 2001. A friend named Ralph Glanz got me a copy of Libranet (Debian) and that got me going because it was better configured than the stock Debian of that time.

Once I learned how to do it I could get any Debian distribution set up any way I wanted.

I found Kanotix and Xandros, and also Corel Linux to also provide helpful Debian features. Sidux was also a great Debian Sid variation.

In 2003 Warren Woodford started to work on MEPIS. The first one was similar to what antiX is today. A year later he came out with Simply MEPIS with the lightest, cleanest KDE implementation I have ever seen.

A few years later Paul, a.k.a. anticapitalista, asked Warren if he could distribute antiX as a child of MEPIS. The rest is history. antiX is the basis for both antiX and MX Linux, the successor of MEPIS.

--
Brian Masinick

[Member olsztyn]

anilkagi wrote:

And in that Antix-core VM, I will install GSconnect. Then connect it to the KDEconnect on my Android phone. There too, to further harden the VM system to make it secure during a session, I will make the “vital parts of VM OS” read-only. And then I will edit the /etc/sudoers file of the VM to restrict the abilities of all other users/applications. And then I will remaster Antix-core VM. I will start the VB in firejail, to isolate the VM.

I am not familiar with KDEconnect, GSconnect and firejail, so perhaps someone else will be able to comment on whether such nested design will work. Question would be one of communication capabilities of KDEconnect and GSconnect, whether from VB VM inside firejail it will be able to talk to KDEconnect on phone connected to USB. It seems a lot depends on protocols being used and firejail sandbox restrictions.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member anilkagi]

olsztyn wrote:

So if e.g. you chose No Persistence (for maximum security of your antiX) then after running system updates and other changes you want to keep, you just run Remaster from the Control Center to permanently burn such updates and changes into antiX Frugal instance.

Olsztyn, this is probably, the most suitable for me and best setup for security. Thanks for taking all the pains to share your knowledge.

Now I will do this.

I will do a no-persistence-frugal install of Antix-base on a HD partition, then update, upgrade and customize it. To further harden the system to make it secure DURING a session, I will make the “vital parts of OS” read-only. And then I will edit the /etc/sudoers file to restrict the abilities of all other users/applications. I will also install firejail.

Then, I will install VirtualBox in it. Next, I will create a no-persistence-frugal-Antix-core VM on the VirtualBox. And in that Antix-core VM, I will install GSconnect. Then connect it to the KDEconnect on my Android phone. There too, to further harden the VM system to make it secure during a session, I will make the “vital parts of VM OS” read-only. And then I will edit the /etc/sudoers file of the VM to restrict the abilities of all other users/applications. And then I will remaster Antix-core VM. I will start the VB in firejail, to isolate the VM.

Though all the above description seems complex it is just a simple “Antix-VB-Antix” non-persistant-frugal-secured setup.

Will this be feasible? I am thinking of putting this to test, …hoping for it to work.

olsztyn wrote:

And just to clarify, I am not one of antiX team. I am just an average user.

I thought so, but you are not an average user, you are an expert user… you have got yourself acquainted with so much of Antix.

Edit: Edited after properly understanding the frugal install inside a running install.

• This reply was modified 2 years, 9 months ago by anilkagi.
• This reply was modified 2 years, 9 months ago by anilkagi.
• This reply was modified 2 years, 9 months ago by anilkagi.

[Member anilkagi]

Thank you Xecure, Sybok and Rockytnji for coming. I was calmly going through all the interesting discussions going on between you knowledgeable guys. Now I thought, I should perhaps post.

Xecure wrote:

stay away from fear and paranoia. Privacy is important, but obsession is worse

That’s a sound piece of advice. It made me relax too.

However actually, I am not paranoid or obsessed, but I am entering the danger zone I suppose, by trying to integrate my Android phone with my Computer. So I am venturing into learning to create secure environment to do such risky activities. This question popped up during that discussion and I started this thread.

I consider integrating an Android phone with my computer risky because, the Android phone that I paid for plus the data plan that I paid for, is used by Google and other Android apps, more than me, for their corporate goals, without me knowing it. Their opaque affairs, which I can’t see through, gives them immense power, to do what they choose to do with me and my data and lifestyle. (Do they own all that, just because they give me those free services?) We know the risks involved and we handle it accordingly. However integrating an Android phone with computer, opens up the computer too, to all that. I want to minimize if not annul the risks there.

I find that the suggestions offered by Seaken64, Dave, Moddit, Olsztyn, Sybok, Rockytnji and yourself are great. And Xecure, thanks for the link. I read further also.

And Sybok’s;

sybok wrote:

you can do a lot of the requirements by properly selecting groups to which the user belongs to (a current user can list the group they belong to using the command ‘groups’).
E.g. definitely remove the restricted-user from ‘sudo’.
READ-ONLY ROOT:
Also, it seems that Debian (and hence I guess that also antiX) allows to mount parts of the filesystem, e.g. root as read-only

Though I didn’t understand much of the link Sybok provided, Olsztyn’s reply…

olsztyn wrote:

So after the entire system is finalized in terms of installed applications and fully configured, there is no need for further changes to these vital parts of OS and these folders can be made read-only.

… gave an idea. That’s really interesting.

I didn’t understand most of Rockytnji’s post, what I could make out. if I am right, from it is, by editing the /etc/sudoers file we can restrict the abilities of users. It was apparent from the last line;

rokytnji wrote:

works fine. My wife can only shutdown and reboot.

Now I feel, I can get to where I want to, almost effectively. So finally I decided to come down to this; I will adopt the best of all the worlds.

For affairs like Banking, where significant security is necessary, I could adopt Olsztyn’s model of having a live USB, easily. And for my daily work I will do the following, with the guidance from you knowledgeable guys. I am afraid I would need a bit of hand-holding too. So I would require a lot of compassion from you guys too. I hope Rockytnji, won’t hate me for this.

First I will install Antix on the computer, which I already have done. After the system is totally ready, I will make the “vital parts of OS” read-only as suggested by Sybok. And then I will edit the /etc/sudoers file to restrict the abilities of all other users except me as suggested by Rockytnji.

Next, I will create an underprivileged user account. This underprivileged user account, is for doing all my work. Then, I will install VirtualBox on this same underprivileged account. I will also install firejail in this same user account. Next, I will create an Antix-core VM on the VirtualBox. And in that Antix-core VM, I will install GSconnect and connect it to the KDEconnect on my Android phone. I will start the VirtualBox / Antix-core VM in firejail.

Can this setup be created?

Would it not provide sufficient security for integrating my Android phone with my Computer, through KDEconnect & GSconnect?

If this is sufficient; to achieve this, to begin with, I will have to first create an underprivileged user account. I don’t find an option to create an underprivileged user account through the, Control center > Maintenance > User Manager. How do I do it?

By underprivileged user account, I mean, one where the user cannot install any software, does not have access to root, sudo, admin etc. I shall remove the privilege to install software after installing VB, Fire jail and Antix-core VM, GS-connect in the VM and any other necessary applications. How do I make this underprivileged user account?

[Member Xecure]

They are built by debian. They call to install a metapackage that brings all needed packages for the DE to work. They are included in the antiX Package Installer for people who don’t know how to install a DE/WM on their system from terminal and really want to use them. antiX doesn’t manage them directly (some, like fluxbox and icewm, are).

Example:
Package name: KDE Standard
Packages installed by Package Installer: kde-standard, virtuoso-minimal
As this is a metapackage (a package that is really a list of packages that will be downloaded as dependencies, and does not contain any “real files” inside), one would have to look at the package named plasma-desktop, for example, to see how updated it is:
In Debian Buster: plasma-desktop (4:5.14.5.1-1) – Wed, 13 Feb 2019

So installing it on your system is like installing it from Debian. Before, like in antiX 17, I think anticapitalista had to build specific versions that were systemd free (so updates would be up to antiX devs), but debian changed a bit its policy and buster is more init friendly (who know how long this will last). If I am mistaken, please forgive me. My history with antiX is very recent, so I may be mixing thing up.

WMs work great when installing from the package installer, but installing any DEs is a different story. The installation is so minimal that, as a non-expert, I find myself lost and don’t know what other packages I need to complement the DE and make everything work. When I installed KDE or Mate, I did it from core and installing the recommended packages. For example, for KDE:
sudo apt install --install-recommends kde-standard
The recommended packages (no included by default, as they are NOT true dependencies) complement very well what is needed for us “simple humans” to get the DE to work.

In summary: Desktop Environments are managed by Debian. When important bugs are discovered, they are usually patched by someone from the Debian team. The default Window Managers are handled by the antiX devs, and have been heavily customized by them.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

My simple setup of antiX19.2-core+kde.

[Forum Admin rokytnji]

Oh yeah. Earlier readout was while running the script. This is total for Kate in repo folder

harry@biker:~
$ cd repo
harry@biker:~/repo
$ ls
adduser_3.118_all.deb
cdebconf_0.249_i386.deb
coreutils_8.30-3_i386.deb
dbus_1.12.16-1_i386.deb
debconf_1.5.71_all.deb
dirmngr_2.2.12-1+deb10u1_i386.deb
dmsetup_2%3a1.02.155-3_i386.deb
dpkg_1.19.7_i386.deb
errors.log
fdisk_2.33.1-0.1_i386.deb
fontconfig_2.13.1-2_i386.deb
fontconfig-config_2.13.1-2_all.deb
fonts-dejavu-core_2.37-1_all.deb
fonts-liberation_1%3a1.07.4-9_all.deb
gcc-8-base_8.3.0-6_i386.deb
gnupg_2.2.12-1+deb10u1_all.deb
gnupg-l10n_2.2.12-1+deb10u1_all.deb
gnupg-utils_2.2.12-1+deb10u1_i386.deb
gpg_2.2.12-1+deb10u1_i386.deb
gpg-agent_2.2.12-1+deb10u1_i386.deb
gpgconf_2.2.12-1+deb10u1_i386.deb
gpgsm_2.2.12-1+deb10u1_i386.deb
gpgv_2.2.12-1+deb10u1_i386.deb
gpg-wks-client_2.2.12-1+deb10u1_i386.deb
gpg-wks-server_2.2.12-1+deb10u1_i386.deb
init-system-helpers_1.56+nmu1_all.deb
install-info_6.5.0.dfsg.1-4+b1_i386.deb
kate_4%3a18.08.0-1_i386.deb
kate5-data_4%3a18.08.0-1_all.deb
kate_i386.repo
kio_5.54.1-1_i386.deb
kpackagetool5_5.54.0-1_i386.deb
ktexteditor-data_5.54.0-1_all.deb
ktexteditor-katepart_5.54.0-1_i386.deb
kwayland-data_4%3a5.54.0-1_all.deb
liba52-0.7.4_0.7.4-19_i386.deb
libaa1_1.4p5-46_i386.deb
libacl1_2.2.53-4_i386.deb
libaom0_1.0.0-3_i386.deb
libapparmor1_2.13.2-10_i386.deb
libarchive13_3.3.3-4+deb10u1_i386.deb
libargon2-1_0~20171227-0.2_i386.deb
libaribb24-0_1.0.3-2_i386.deb
libasound2_1.1.8-1_i386.deb
libasound2-data_1.1.8-1_all.deb
libass9_1%3a0.14.0-2_i386.deb
libassuan0_2.5.2-1_i386.deb
libasyncns0_0.8-6_i386.deb
libatomic1_8.3.0-6_i386.deb
libattr1_1%3a2.4.48-4_i386.deb
libaudit1_1%3a2.8.4-3_i386.deb
libaudit-common_1%3a2.8.4-3_all.deb
libavahi-client3_0.7-4+b1_i386.deb
libavahi-common3_0.7-4+b1_i386.deb
libavahi-common-data_0.7-4+b1_i386.deb
libavc1394-0_0.5.4-5_i386.deb
libavcodec58_7%3a4.1.6-1~deb10u1_i386.deb
libavformat58_7%3a4.1.6-1~deb10u1_i386.deb
libavutil56_7%3a4.1.6-1~deb10u1_i386.deb
libbasicusageenvironment1_2018.11.26-1.1_i386.deb
libblkid1_2.33.1-0.1_i386.deb
libbluray2_1%3a1.1.0-1_i386.deb
libbsd0_0.9.1-2_i386.deb
libbz2-1.0_1.0.6-9.2~deb10u1_i386.deb
libc6_2.28-10_i386.deb
libcaca0_0.99.beta19-2.1_i386.deb
libcairo2_1.16.0-4_i386.deb
libcap2_1%3a2.25-2_i386.deb
libcap-ng0_0.7.9-2_i386.deb
libcddb2_1.3.2-6_i386.deb
libchromaprint1_1.4.3-3_i386.deb
libcodec2-0.8.1_0.8.1-2_i386.deb
libcom-err2_1.44.5-1+deb10u3_i386.deb
libcroco3_0.6.12-3_i386.deb
libcryptsetup12_2%3a2.1.0-5+deb10u2_i386.deb
libcrystalhd3_1%3a0.0~git20110715.fdd2f19-13_i386.deb
libcups2_2.2.10-6+deb10u3_i386.deb
libdatrie1_0.2.12-2_i386.deb
libdb5.3_5.3.28+dfsg1-0.5_i386.deb
libdbus-1-3_1.12.16-1_i386.deb
libdbusmenu-qt5-2_0.9.3+16.04.20160218-1_i386.deb
libdc1394-22_2.2.5-1_i386.deb
libdca0_0.0.6-1_i386.deb
libdebian-installer4_0.119_i386.deb
libdevmapper1.02.1_2%3a1.02.155-3_i386.deb
libdouble-conversion1_3.1.0-3_i386.deb
libdrm2_2.4.97-1_i386.deb
libdrm-amdgpu1_2.4.97-1_i386.deb
libdrm-common_2.4.97-1_all.deb
libdrm-intel1_2.4.97-1_i386.deb
libdrm-nouveau2_2.4.97-1_i386.deb
libdrm-radeon1_2.4.97-1_i386.deb
libdvbpsi10_1.3.2-1_i386.deb
libdvdnav4_6.0.0-1_i386.deb
libdvdread4_6.0.1-1_i386.deb
libebml4v5_1.3.6-2_i386.deb
libedit2_3.1-20181209-1_i386.deb
libeditorconfig0_0.12.1-1.1_i386.deb
libegl1_1.1.0-1_i386.deb
libegl-mesa0_18.3.6-2+deb10u1_i386.deb
libelf1_0.176-1.1_i386.deb
libelogind0_243.7-1.0antix1_i386.deb
libepoxy0_1.5.3-0.1_i386.deb
libevdev2_1.6.0+dfsg-1_i386.deb
libexpat1_2.2.6-2+deb10u1_i386.deb
libfaad2_2.8.8-3_i386.deb
libfam0_2.7.0-17.3_i386.deb
libfdisk1_2.33.1-0.1_i386.deb
libffi6_3.2.1-9_i386.deb
libflac8_1.3.2-3_i386.deb
libfontconfig1_2.13.1-2_i386.deb
libfreetype6_2.9.1-3+deb10u1_i386.deb
libfribidi0_1.0.5-3.1+deb10u1_i386.deb
libgbm1_18.3.6-2+deb10u1_i386.deb
libgcc1_1%3a8.3.0-6_i386.deb
libgcrypt20_1.8.4-5_i386.deb
libgdbm6_1.18.1-4_i386.deb
libgdbm-compat4_1.18.1-4_i386.deb
libgdk-pixbuf2.0-0_2.38.1+dfsg-1_i386.deb
libgdk-pixbuf2.0-common_2.38.1+dfsg-1_all.deb
libgit2-27_0.27.7+dfsg.1-0.2_i386.deb
libgl1_1.1.0-1_i386.deb
libgl1-mesa-dri_18.3.6-2+deb10u1_i386.deb
libglapi-mesa_18.3.6-2+deb10u1_i386.deb
libgles2_1.1.0-1_i386.deb
libglib2.0-0_2.58.3-2+deb10u2_i386.deb
libglvnd0_1.1.0-1_i386.deb
libglx0_1.1.0-1_i386.deb
libglx-mesa0_18.3.6-2+deb10u1_i386.deb
libgme0_0.6.2-1_i386.deb
libgmp10_2%3a6.1.2+dfsg-4_i386.deb
libgnutls30_3.6.7-4+deb10u4_i386.deb
libgomp1_8.3.0-6_i386.deb
libgpg-error0_1.35-1_i386.deb
libgpgme11_1.12.0-6_i386.deb
libgpgmepp6_1.12.0-6_i386.deb
libgpm2_1.20.7-5_i386.deb
libgraphite2-3_1.3.13-7_i386.deb
libgroupsock8_2018.11.26-1.1_i386.deb
libgsm1_1.0.18-2_i386.deb
libgssapi-krb5-2_1.17-3_i386.deb
libgudev-1.0-0_232-2_i386.deb
libharfbuzz0b_2.3.1-1_i386.deb
libhogweed4_3.4.1-1_i386.deb
libhttp-parser2.8_2.8.1-1_i386.deb
libice6_2%3a1.0.9-2_i386.deb
libicu63_63.1-6+deb10u1_i386.deb
libidn11_1.33-2.2_i386.deb
libidn2-0_2.0.5-1+deb10u1_i386.deb
libinput10_1.12.6-2_i386.deb
libinput-bin_1.12.6-2_i386.deb
libip4tc0_1.8.2-4_i386.deb
libixml10_1%3a1.8.4-2_i386.deb
libjbig0_2.1-3.1+b2_i386.deb
libjpeg62-turbo_1%3a1.5.2-2+b1_i386.deb
libjson-c3_0.12.1+ds-2_i386.deb
libjs-underscore_1.9.1~dfsg-1_all.deb
libk5crypto3_1.17-3_i386.deb
libkate1_0.4.1-9_i386.deb
libkeyutils1_1.6-6_i386.deb
libkf5activities5_5.54.0-1_i386.deb
libkf5archive5_5.54.0-1_i386.deb
libkf5attica5_5.54.0-1_i386.deb
libkf5auth5_5.54.0-2_i386.deb
libkf5auth-data_5.54.0-2_all.deb
libkf5bookmarks5_5.54.0-1_i386.deb
libkf5bookmarks-data_5.54.0-1_all.deb
libkf5calendarevents5_5.54.0-1_i386.deb
libkf5codecs5_5.54.0-1_i386.deb
libkf5codecs-data_5.54.0-1_all.deb
libkf5completion5_5.54.0-1_i386.deb
libkf5completion-data_5.54.0-1_all.deb
libkf5configcore5_5.54.0-1+deb10u1_i386.deb
libkf5config-data_5.54.0-1+deb10u1_all.deb
libkf5configgui5_5.54.0-1+deb10u1_i386.deb
libkf5configwidgets5_5.54.0-1_i386.deb
libkf5configwidgets-data_5.54.0-1_all.deb
libkf5coreaddons5_5.54.0-1_i386.deb
libkf5coreaddons-data_5.54.0-1_all.deb
libkf5crash5_5.54.0-1_i386.deb
libkf5dbusaddons5_5.54.0-1_i386.deb
libkf5dbusaddons-data_5.54.0-1_all.deb
libkf5declarative5_5.54.0-1_i386.deb
libkf5declarative-data_5.54.0-1_all.deb
libkf5doctools5_5.54.0-1_i386.deb
libkf5globalaccel5_5.54.0-1_i386.deb
libkf5globalaccel-bin_5.54.0-1_i386.deb
libkf5globalaccel-data_5.54.0-1_all.deb
libkf5globalaccelprivate5_5.54.0-1_i386.deb
libkf5guiaddons5_5.54.0-1_i386.deb
libkf5i18n5_5.54.0-1_i386.deb
libkf5i18n-data_5.54.0-1_all.deb
libkf5iconthemes5_5.54.0-1_i386.deb
libkf5iconthemes-data_5.54.0-1_all.deb
libkf5itemmodels5_5.54.0-1_i386.deb
libkf5itemviews5_5.54.0-1_i386.deb
libkf5itemviews-data_5.54.0-1_all.deb
libkf5jobwidgets5_5.54.0-1_i386.deb
libkf5jobwidgets-data_5.54.0-1_all.deb
libkf5kiocore5_5.54.1-1_i386.deb
libkf5kiofilewidgets5_5.54.1-1_i386.deb
libkf5kiontlm5_5.54.1-1_i386.deb
libkf5kiowidgets5_5.54.1-1_i386.deb
libkf5newstuff5_5.54.0-2_i386.deb
libkf5newstuffcore5_5.54.0-2_i386.deb
libkf5newstuff-data_5.54.0-2_all.deb
libkf5notifications5_5.54.0-1_i386.deb
libkf5notifications-data_5.54.0-1_all.deb
libkf5package5_5.54.0-1_i386.deb
libkf5package-data_5.54.0-1_all.deb
libkf5parts5_5.54.0-1_i386.deb
libkf5parts-data_5.54.0-1_all.deb
libkf5plasma5_5.54.0-1_i386.deb
libkf5plasmaquick5_5.54.0-1_i386.deb
libkf5quickaddons5_5.54.0-1_i386.deb
libkf5service5_5.54.0-1_i386.deb
libkf5service-bin_5.54.0-1_i386.deb
libkf5service-data_5.54.0-1_all.deb
libkf5solid5_5.54.0-1_i386.deb
libkf5solid5-data_5.54.0-1_all.deb
libkf5sonnet5-data_5.54.0-1_all.deb
libkf5sonnetcore5_5.54.0-1_i386.deb
libkf5sonnetui5_5.54.0-1_i386.deb
libkf5syntaxhighlighting5_5.54.0-1_i386.deb
libkf5syntaxhighlighting-data_5.54.0-1_all.deb
libkf5texteditor5_5.54.0-1_i386.deb
libkf5texteditor-bin_5.54.0-1_i386.deb
libkf5textwidgets5_5.54.0-1_i386.deb
libkf5textwidgets-data_5.54.0-1_all.deb
libkf5threadweaver5_5.54.0-1_i386.deb
libkf5wallet5_5.54.0-1_i386.deb
libkf5wallet-bin_5.54.0-1_i386.deb
libkf5wallet-data_5.54.0-1_all.deb
libkf5waylandclient5_4%3a5.54.0-1_i386.deb
libkf5widgetsaddons5_5.54.0-1_i386.deb
libkf5widgetsaddons-data_5.54.0-1_all.deb
libkf5windowsystem5_5.54.0-1_i386.deb
libkf5windowsystem-data_5.54.0-1_all.deb
libkf5xmlgui5_5.54.0-1_i386.deb
libkf5xmlgui-data_5.54.0-1_all.deb
libkmod2_26-1_i386.deb
libkrb5-3_1.17-3_i386.deb
libkrb5support0_1.17-3_i386.deb
libksba8_1.3.5-2_i386.deb
libkwalletbackend5-5_5.54.0-1_i386.deb
liblcms2-2_2.9-3_i386.deb
libldap-2.4-2_2.4.47+dfsg-3+deb10u2_i386.deb
libldap-common_2.4.47+dfsg-3+deb10u2_all.deb
liblirc-client0_0.10.1-5.2_i386.deb
liblivemedia64_2018.11.26-1.1_i386.deb
libllvm7_1%3a7.0.1-8_i386.deb
liblua5.2-0_5.2.4-1.1+b2_i386.deb
liblz4-1_1.8.3-1_i386.deb
liblzma5_5.2.4-1_i386.deb
libmad0_0.15.1b-10_i386.deb
libmatroska6v5_1.4.9-1+deb10u1_i386.deb
libmbedcrypto3_2.16.0-1_i386.deb
libmbedtls12_2.16.0-1_i386.deb
libmbedx509-0_2.16.0-1_i386.deb
libmount1_2.33.1-0.1_i386.deb
libmp3lame0_3.100-2+b1_i386.deb
libmpcdec6_2%3a0.1~r495-1+b2_i386.deb
libmpeg2-4_0.5.1-8_i386.deb
libmpg123-0_1.25.10-2_i386.deb
libmtdev1_1.1.5-1+b1_i386.deb
libmtp9_1.1.16-2_i386.deb
libmtp-common_1.1.16-2_all.deb
libmysofa0_0.6~dfsg0-3+deb10u1_i386.deb
libncurses6_6.1+20181013-2+deb10u2_i386.deb
libncursesw6_6.1+20181013-2+deb10u2_i386.deb
libnettle6_3.4.1-1_i386.deb
libnewt0.52_0.52.20-8_i386.deb
libnfs12_3.0.0-2_i386.deb
libnpth0_1.6-1_i386.deb
libnuma1_2.0.12-1_i386.deb
libogg0_1.3.2-1+b1_i386.deb
libopenjp2-7_2.3.0-2+deb10u1_i386.deb
libopenmpt0_0.4.3-1+deb10u1_i386.deb
libopenmpt-modplug1_0.4.3-1+deb10u1_i386.deb
libopus0_1.3-1_i386.deb
libp11-kit0_0.23.15-2_i386.deb
libpam0g_1.3.1-5_i386.deb
libpam-modules_1.3.1-5_i386.deb
libpam-modules-bin_1.3.1-5_i386.deb
libpam-runtime_1.3.1-5_all.deb
libpam-systemd_241-7~deb10u4_i386.deb
libpango-1.0-0_1.42.4-8~deb10u1_i386.deb
libpangocairo-1.0-0_1.42.4-8~deb10u1_i386.deb
libpangoft2-1.0-0_1.42.4-8~deb10u1_i386.deb
libpciaccess0_0.14-1_i386.deb
libpcre2-16-0_10.32-5_i386.deb
libpcre2-8-0_10.32-5_i386.deb
libpcre3_2%3a8.39-12_i386.deb
libperl5.28_5.28.1-6_i386.deb
libphonon4qt5-4_4%3a4.10.2-1_i386.deb
libpixman-1-0_0.36.0-1_i386.deb
libplacebo7_1.7.0-2_i386.deb
libpng16-16_1.6.36-6_i386.deb
libpolkit-agent-1-0_0.105-26+antix1_i386.deb
libpolkit-gobject-1-0_0.105-26+antix1_all.deb
libpolkit-gobject-consolekit-1-0_0.105-26+antix1_i386.deb
libpolkit-gobject-elogind-1-0_0.105-26+antix1_i386.deb
libpolkit-qt5-1-1_0.112.0-6_i386.deb
libpostproc55_7%3a4.1.6-1~deb10u1_i386.deb
libprotobuf-lite17_3.6.1.3-2_i386.deb
libpulse0_12.2-4+deb10u1_i386.deb
libpulse-mainloop-glib0_12.2-4+deb10u1_i386.deb
libqt5core5a_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5dbus5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5gui5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5network5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5printsupport5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5qml5_5.11.3-4_i386.deb
libqt5quick5_5.11.3-4_i386.deb
libqt5quickcontrols2-5_5.11.3+dfsg-2_i386.deb
libqt5quicktemplates2-5_5.11.3+dfsg-2_i386.deb
libqt5script5_5.11.3+dfsg-3_i386.deb
libqt5sql5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5svg5_5.11.3-2_i386.deb
libqt5texttospeech5_5.11.3-3_i386.deb
libqt5widgets5_5.11.3+dfsg1-1+deb10u3_i386.deb
libqt5x11extras5_5.11.3-2_i386.deb
libqt5xml5_5.11.3+dfsg1-1+deb10u3_i386.deb
libraw1394-11_2.1.2-1+b1_i386.deb
libreadline7_7.0-5_i386.deb
libresid-builder0c2a_2.1.1-15_i386.deb
librsvg2-2_2.44.10-2.1_i386.deb
libsamplerate0_0.1.9-2_i386.deb
libsasl2-2_2.1.27+dfsg-1+deb10u1_i386.deb
libsasl2-modules-db_2.1.27+dfsg-1+deb10u1_i386.deb
libsdl1.2debian_1.2.15+dfsg2-4_i386.deb
libsdl-image1.2_1.2.12-10+deb10u1_i386.deb
libseccomp2_2.3.3-4_i386.deb
libsecret-1-0_0.18.7-1_i386.deb
libsecret-common_0.18.7-1_all.deb
libselinux1_2.8-1+b1_i386.deb
libsemanage1_2.8-2_i386.deb
libsemanage-common_2.8-2_all.deb
libsensors5_1%3a3.5.0-3_i386.deb
libsensors-config_1%3a3.5.0-3_all.deb
libsepol1_2.8-1_i386.deb
libshine3_3.1.1-2_i386.deb
libshout3_2.4.1-2_i386.deb
libsidplay2_2.1.1-15_i386.deb
libslang2_2.3.2-2_i386.deb
libsm6_2%3a1.2.3-1_i386.deb
libsmartcols1_2.33.1-0.1_i386.deb
libsnappy1v5_1.1.7-1_i386.deb
libsndfile1_1.0.28-6_i386.deb
libsndio7.0_1.5.0-3_i386.deb
libsoxr0_0.1.2-3_i386.deb
libspatialaudio0_0.3.0+git20180730+dfsg1-2_i386.deb
libspeex1_1.2~rc1.2-1+b2_i386.deb
libspeexdsp1_1.2~rc1.2-1+b2_i386.deb
libsqlite3-0_3.27.2-3_i386.deb
libssh2-1_1.8.0-2.1_i386.deb
libssh-gcrypt-4_0.8.7-1+deb10u1_i386.deb
libssl1.1_1.1.1d-0+deb10u3_i386.deb
libstdc++6_8.3.0-6_i386.deb
libswresample3_7%3a4.1.6-1~deb10u1_i386.deb
libswscale5_7%3a4.1.6-1~deb10u1_i386.deb
libsystemd0_241.4+antix1_all.deb
libtag1v5_1.11.1+dfsg.1-0.3+deb10u1_i386.deb
libtag1v5-vanilla_1.11.1+dfsg.1-0.3+deb10u1_i386.deb
libtasn1-6_4.13-3_i386.deb
libtextwrap1_0.1-14.2_i386.deb
libthai0_0.1.28-2_i386.deb
libthai-data_0.1.28-2_all.deb
libtheora0_1.1.1+dfsg.1-15_i386.deb
libtiff5_4.1.0+git191117-2~deb10u1_i386.deb
libtinfo6_6.1+20181013-2+deb10u2_i386.deb
libtwolame0_0.3.13-4_i386.deb
libudev1_241-7~deb10u4_i386.deb
libunistring2_0.9.10-1_i386.deb
libupnp13_1%3a1.8.4-2_i386.deb
libusageenvironment3_2018.11.26-1.1_i386.deb
libusb-1.0-0_2%3a1.0.22-2_i386.deb
libuuid1_2.33.1-0.1_i386.deb
libva2_2.4.0-1_i386.deb
libva-drm2_2.4.0-1_i386.deb
libva-wayland2_2.4.0-1_i386.deb
libva-x11-2_2.4.0-1_i386.deb
libvdpau1_1.1.1-10_i386.deb
libvlc5_3.0.11-0+deb10u1_i386.deb
libvlccore9_3.0.11-0+deb10u1_i386.deb
libvorbis0a_1.3.6-2_i386.deb
libvorbisenc2_1.3.6-2_i386.deb
libvorbisfile3_1.3.6-2_i386.deb
libvpx5_1.7.0-3+deb10u1_i386.deb
libvulkan1_1.1.97-2_i386.deb
libwacom2_0.32-1_i386.deb
libwacom-common_0.32-1_all.deb
libwavpack1_5.1.0-6_i386.deb
libwayland-client0_1.16.0-1_i386.deb
libwayland-egl1_1.16.0-1_i386.deb
libwayland-server0_1.16.0-1_i386.deb
libwebp6_0.6.1-2_i386.deb
libwebpmux3_0.6.1-2_i386.deb
libwrap0_7.6.q-28_i386.deb
libx11-6_2%3a1.6.7-1_i386.deb
libx11-data_2%3a1.6.7-1_all.deb
libx11-xcb1_2%3a1.6.7-1_i386.deb
libx264-155_2%3a0.155.2917+git0a84d98-2_i386.deb
libx265-165_2.9-4_i386.deb
libxau6_1%3a1.0.8-1+b2_i386.deb
libxcb1_1.13.1-2_i386.deb
libxcb-composite0_1.13.1-2_i386.deb
libxcb-damage0_1.13.1-2_i386.deb
libxcb-dri2-0_1.13.1-2_i386.deb
libxcb-dri3-0_1.13.1-2_i386.deb
libxcb-glx0_1.13.1-2_i386.deb
libxcb-icccm4_0.4.1-1.1_i386.deb
libxcb-image0_0.4.0-1+b2_i386.deb
libxcb-keysyms1_0.4.0-1+b2_i386.deb
libxcb-present0_1.13.1-2_i386.deb
libxcb-randr0_1.13.1-2_i386.deb
libxcb-render0_1.13.1-2_i386.deb
libxcb-render-util0_0.3.9-1+b1_i386.deb
libxcb-shape0_1.13.1-2_i386.deb
libxcb-shm0_1.13.1-2_i386.deb
libxcb-sync1_1.13.1-2_i386.deb
libxcb-util0_0.3.8-3+b2_i386.deb
libxcb-xfixes0_1.13.1-2_i386.deb
libxcb-xinerama0_1.13.1-2_i386.deb
libxcb-xkb1_1.13.1-2_i386.deb
libxcb-xv0_1.13.1-2_i386.deb
libxdamage1_1%3a1.1.4-3+b3_i386.deb
libxdmcp6_1%3a1.1.2-3_i386.deb
libxext6_2%3a1.3.3-1+b2_i386.deb
libxfixes3_1%3a5.0.3-1_i386.deb
libxi6_2%3a1.7.9-1_i386.deb
libxkbcommon0_0.8.2-1_i386.deb
libxkbcommon-x11-0_0.8.2-1_i386.deb
libxml2_2.9.4+dfsg1-7+b3_i386.deb
libxrender1_1%3a0.9.10-1_i386.deb
libxshmfence1_1.3-1_i386.deb
libxslt1.1_1.1.32-2.2~deb10u1_i386.deb
libxtst6_2%3a1.2.3-1_i386.deb
libxvidcore4_2%3a1.3.5-1_i386.deb
libxxf86vm1_1%3a1.1.4-1+b2_i386.deb
libzstd1_1.3.8+dfsg-3_i386.deb
libzvbi0_0.2.35-16_i386.deb
libzvbi-common_0.2.35-16_all.deb
login_1%3a4.5-1.1_i386.deb
lsb-base_10.2019051400_all.deb
mount_2.33.1-0.1_i386.deb
myAPTOfflineRepo.sh
Packages.gz
passwd_1%3a4.5-1.1_i386.deb
perl_5.28.1-6_i386.deb
perl-base_5.28.1-6_i386.deb
perl-modules-5.28_5.28.1-6_all.deb
phonon4qt5_4%3a4.10.2-1_i386.deb
phonon4qt5-backend-vlc_0.10.2-1_i386.deb
pinentry-curses_1.1.0-2_i386.deb
plasma-framework_5.54.0-1_i386.deb
qml-module-org-kde-kconfig_5.54.0-1_i386.deb
qml-module-org-kde-kquickcontrols_5.54.0-1_i386.deb
qml-module-org-kde-kquickcontrolsaddons_5.54.0-1_i386.deb
qml-module-qtgraphicaleffects_5.11.3-2_i386.deb
qml-module-qtqml-models2_5.11.3-4_i386.deb
qml-module-qtquick2_5.11.3-4_i386.deb
qml-module-qtquick-controls2_5.11.3+dfsg-2_i386.deb
qml-module-qtquick-controls_5.11.3-2_i386.deb
qml-module-qtquick-dialogs_5.11.3-2_i386.deb
qml-module-qtquick-layouts_5.11.3-4_i386.deb
qml-module-qtquick-privatewidgets_5.11.3-2_i386.deb
qml-module-qtquick-templates2_5.11.3+dfsg-2_i386.deb
qml-module-qtquick-window2_5.11.3-4_i386.deb
readline-common_7.0-5_all.deb
sensible-utils_0.0.12_all.deb
shared-mime-info_1.10-1_i386.deb
systemd_241-7~deb10u4_i386.deb
systemd-sysv_241-7~deb10u4_i386.deb
systemd-timesyncd_245.6-1~bpo10+1_i386.deb
tar_1.30+dfsg-6_i386.deb
ttf-bitstream-vera_1.10-8_all.deb
ucf_3.0038+nmu1_all.deb
util-linux_2.33.1-0.1_i386.deb
vlc-data_3.0.11-0+deb10u1_all.deb
vlc-plugin-base_3.0.11-0+deb10u1_i386.deb
vlc-plugin-video-output_3.0.11-0+deb10u1_i386.deb
x11-common_1%3a7.7+19_all.deb
xecure_post
xkb-data_2.26-2_all.deb
zlib1g_1%3a1.2.11.dfsg-1_i386.deb
harry@biker:~/repo
$ 

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems