Updating the repositories

[swirly]

Hello,

I've installed WAPT Server (on Debian 10) and a console on a Windows 10 machine.

I'd like to know the best way to update remote repositories. If I import a package, I create a new package in my local repository. For
example, if I want to install LibreOffice on the machines on my network,
I need to import the `tis-libre-office` package, which then becomes the `test-libre-office` package on my local machine. Let's say this is version 6.3.

How can I be notified when version 6.4 is released for the `tis` package? How can I synchronize so that my local version also updates to 6.4? Is the only solution to copy the package again by importing it?

The strength of apt under Debian lies in its use of the Debian project repositories, which allow for regular updates, especially security updates.

Deploying an application is easy;
keeping a system up-to-date is more difficult. If I have to check the imports of every single piece of software, it's going to be complicated.

Have I missed something?

Sincerely,
Laurent

[sfonteneau]

Tranquilit cannot guarantee the software in its repository.

However, it is still possible to do what you want (though not recommended ).

Compatible since wapt 1.8.2.7265:

https://www.wapt.fr/fr/doc/wapt-replica ... index.html

You must therefore retrieve the Tranquilit certificate:

https://wapt.tranquil.it/wapt/catranquilit.crt and place it in wapt\ssl\ on ​​the machines.

Then add the Tranquilit repository to the agents and in your console configuration (follow the documentation).

As a bonus/addition, you can fully replicate the repository http://wapt.tranquil.it/wapt to save bandwidth.

[swirly]

Hello,
I followed your advice and the documentation.
There were no problems configuring the
wapt-get search and wapt-get install clients; they work well, and
the console is also configured
. However, I can't create a package group that has dependencies on the TIS repository. Can a package group only depend on the private repository?
Thank you in advance for your clarification.
Laurent

[sfonteneau]

Hello
, I followed your advice and the documentation.
No problem configuring the clients
; wapt-get search and wapt-get install work well, and
the console is also configured.
However, it's impossible to create a package group that has dependencies on the TIS repository. Can a package group only depend on the private repository?

No, I just tested it with version 1.8.2 and it works:
https://www.wapt.fr/fr/doc/wapt-replica ... positories

Alternatively, another simple solution is to write a small script that downloads the desired WAPT packages (https://wapt.tranquil.it/wapt/) in /var/www/wapt

and at the end you can run the command

Code: Select all

wapt-scanpackages /var/www/wapt/ 

So you have the wapt tis package directly in your repo, the difference is that you haven't re-signed it.

Note that the method still requires copying the TIS certificate onto all machines.

[swirly]

Thank you for all your replies. I'm on version 1.8.1.6756 and not 1.8.2, but that shouldn't change the behavior, right?

So I modified the files as described in the documentation. I thought there was an error in the documentation and that I needed to modify
%appdata%\local\waptconsole\waptconsole.ini,
so I added the private and tranquilit sections. But they then appear in the console as external repositories that I can import by re-signing the packages, which is what I want to avoid. Just to be

sure, I created a %appdata%..\localwaptconsole\waptconsole.ini with just the two fields (but I wasn't too sure it would work), but I still have
the same problem.

The TIS repository only appears as an external repository from which I can import packages to re-sign them.
Would screenshots be helpful?

In short, there's a difference between the documentation and how it works here.

Best regards,

Laurent C.

[sfonteneau]

Thank you for all your replies. I'm on version 1.8.1.6756 and not 1.8.2, but that shouldn't change the behavior, right?

Yes, exactly

[swirly]

Good morning
So I updated my server, my agent and my console to version 1.8.2
It still doesn't seem to be working.
I may have made a mistake in the configuration. Here is the content of the configuration file, which has three parts:

• A global part

• part wapt=temples

• a tranquil area

I'm truncating what might not be relevant
------------------------------------------------
[overall]
repo_url=https://srvwapt.eaux-claires.net/wapt
send_usage_report=1
use_hostpackages=1
wapt_server=https://srvwapt.eaux-claires.net
use_kerberos=0
check_certificates_validity=1
verify_cert=0
..........

[wapt-templates]
repo_url=https://store.wapt.fr/wapt
verify_cert=1
dnsdomain=
http_proxy=http://172.21.207.254:3128/
public_certs_dir=
client_certificate=
client_private_key=
timeout=5

[tranquility]
repo_url=https://wapt.tranquil.it/wapt
http_proxy=http://172.21.207.254:3128/
use_http_proxy_for_repo=1
verify_cert=0
public_certs_dir=
client_certificate=C:\Program Files (x86)\wapt\ssl\catranquilit.crt
client_private_key=
timeout=5
dnsdomain=
-------------------------------------------

[swirly]

So I have the Tranquility repository configured, and it also appears in the external repositories

external repository

Screenshot 2020-07-06 at 09:49:24.png (99.2 KB) Viewed 6777 times

But if I try to create a new package group or dependency, no tis package appears

new addiction

Screenshot-2020-07-06-at-09.48.11.gif (117.7 KB) Viewed 6777 times

If I'm using a wapt-get client, I can install a tis package without any problem, but at the console level, they are only accessible for import

I suspect an error in the conf file, but where?

Thank you again for all your answers

[sfonteneau]

The documentation is missing information on how to set the list of repositories in waptconsole:

Code: Select all

repositories=private,tranquilit

Attention

You seem to want to use our repository directly without replicating it. This could saturate our uplink server, especially if you have many workstations.
If that were to happen to us, we would be obliged to ban the IP address in question.

You need to replicate our repository if you really want to do this...

[swirly]

Thank you for your replies and your patience.
The files passing through the client are indeed very small files (just Python files), and with the added use of the proxy, we shouldn't be far from saturating the link, should we? A packet, in the WAPT sense, is a set of instructions; you're not including the files? So we're talking about only a few kilobytes per packet.
I can look into replication; it's another element to implement (I can use Reprepro, so we should be able to do it for Windows too!).
Best regards,
Laurent