Tranquil IT Forum

Published: **February 21, 2019 - 11:25 AM**

Good morning,

First, the client and server configuration information can be found in my signature

I'm having a strange problem: I imported the libreoffice-stable package and the vlc package into my repository.

From the console, both packages are clearly visible.

Both packages are also visible on the server via SSH.

When I try to install vlc on a machine (tested on two Win7x64 machines), the console returns a "Missing dependencies vlc" message (same message for libre office).

From the client machine, via a 127.0.0.1:8086, in "Packet List", the two packages are not visible.

From the client machine, via a wapt-get install, same error message (Critical: unavailable packages).

I tried clearing the console's local cache: same result.

I tried a debug scan of the packages using "wapt-scanpackages -f -ldebug /var/www/wapt", it does see the 2 packages though....

Code: Select all

root@wapt:/home/wapt#[b] wapt-scanpackages -f -ldebug /var/www/wapt[/b]
2019-02-21 11:18:28,328 INFO   Processing new /var/www/wapt/prefixe-vlc_3.0.6-3_x86_all.wapt
..........

An "ls -lha" command on the server:

Code: Select all

.....
-rw-r--r-- 1 wapt www-data  35M Jan 28 10:52 prefixe-thunderbird_60.4.0-36_x64_fr.wapt
-rw-r--r-- 1 wapt www-data  39M Feb 21 11:08 prefixe-vlc_3.0.6-3_x86_all.wapt
-rw-r--r-- 1 wapt www-data  22M Mar 27  2018 prefixe-waptupgrade_1.5.1.21-5_all.wapt
.....

I'm struggling to understand why these two packages (LibreOffice/VLC) remain invisible to customers... the other packages (more than 30) don't cause any problems...
I've already tried deleting them from the server and re-importing them, but no luck... :/

Any leads?

Thank you.

Published: **February 21, 2019 - 2:06 PM**

Good morning,

You have imported the VLC x86 package which is only visible to machines with a 32-bit system.

To avoid this message, import the 64-bit version of the VLC package

The thunderbird package, on the other hand, is an x64-only package, therefore invisible to 32-bit machines.

If you want a manually created package to be visible to all architectures, specify the following in the control file:

Code: Select all

architecture : all

In the documentation: https://www.wapt.fr/fr/doc/wapt-create- ... chitecture

EDIT: Starting with WAPT 1.7, display filtering in the private repository and during import is available

Sincerely,

Alexander

Published: **February 21, 2019 - 2:28 PM**

You have imported the VLC x86 package, which is only visible to machines with a 32-bit system.

To avoid this message, import the 64-bit version of the VLC package.

First of all, thank you for the reply. I just tested it with VLC:
- via the WAPT Console -> private repository
- Import from the internet (store.wapt.fr)
- The "Latest version only" box was checked
- I'm importing the "tis-vlc 3.0.6-2" package, which is labeled "x64" for Arch
- Once imported, I do "package editing": in the control file it says "architecture: x86".

- I follow exactly the same procedure with the VLC version "tis-vlc 3.0.5-3"
- Once imported, I do "package editing": in the control file it says "architecture: x64".
On the client machine, via 127.0.0.1, I can see my VLC package in version 3.0.5-3.

Problem solved then... but I wonder if there might be an issue with version 3.0.6-2 in your repository?

Thanks anyway, I learned something today about the "control" file. I'll be more careful next time

Tranquil IT Forum

[RESOLVED] 2 packages not visible to clients...?

[RESOLVED] 2 packages not visible to clients...?

Re: 2 packages not visible to customers...?

Re: 2 packages not visible to customers...?