Tranquil IT Forum

Hello,


I just created my first package, and the `wapt-get build-upload` command fails to upload it to the server because the destination folder doesn't seem to exist.
On my system, it should be accessible at https://wapt.hugo.local/upload_package/.

I installed the server on Debian. Is there a command or parameter I need to use to set up the `upload_package` share?

In the meantime, I generated the package locally using `wapt-get build-package` and uploaded it via the console.

I simply misused the command. I thought this command was for creating the package and sending it immediately.

You can close the thread.

Good morning,

Now, I'd appreciate it if you could explain your last post. Indeed, after reading the documentation, it's clear to me that this command is supposed to create the package and send it immediately:
On the page: https://www.wapt.fr/fr/doc/CreationPaqu ... index.html I read:

Once the package project is created, you can launch the package build without modification from the Windows command prompt.

`wapt-get build-upload -ic:\waptdev\tis-tightvnc-wapt`

Note:

When you run this command, here's what actually happens:

The manifest file is generated with the list of files contained in the package;
The directory C:\waptdev\tis-tightvnc-wapt is compressed with a canonical name for WAPT packages;
The signature is added (requires the presence of the private key);
The WAPT file is uploaded via HTTP to the WAPT repository;
The index file http://wapt/wapt/Packages , taking into account the new package or the new version of the package if it already existed;

The package is ready to be deployed.

So, I don't understand why this directory (upload_package) doesn't exist on the server, and why I'm getting a 502 error, even though it just asks me for the login/password to connect to the server??
Especially since it's this command that initiates the upload; I didn't ask it to!

If someone can shed some light on this, I'm completely lost.

Thanks in advance

Upload package is not a directory:

https://github.com/tranquilit/WAPT/blob ... er.py#L418

To address error 502:
viewtopic.php?f=13&t=887

Without this essential information, I unfortunately cannot do anything.

Hello,

Server: Debian (Linux): Wapt 1.3.13
Development machine: Windows 10

Regarding `upload_package`, it is indeed a function, but the error message I receive refers to a directory:
FATAL ERROR: HTTPError: 502 Server Error: Bad Gateway for url: https://srvwapt.chezmoi.fr/upload_packa ... 1_all.wapt
(chezmoi is not the actual domain name, of course).
Obviously, there is no trace of this directory on the server, in /var/www/.

Regards

Further to this...

I should clarify, of course, that the directive in the wapt-get.ini file is correct:
repo_url=http://srvwapt.chezmoi.fr/wapt

Continued...

To add to that, I've just taken a closer look at the code in the link you sent me, and it seems to me that line 218 refers to this directory:

Can you explain how you're using the build-upload command?

This is the first time I've encountered this kind of problem.

Edit:

To test:

We agree that when you use the "import from file" button and select the file generated during your build upload in c:\waptdev, it works, right?

I'm using it by following this documentation to the letter:
https://www.wapt.fr/fr/doc/CreationPaqu ... index.html

First, with the command:
`wapt-get make-template c:\download\ganttproject.exe yourprefix-ganttproject`.

Then, I make a few modifications to the `control` file in pyscript (which is launched automatically by the previous command). Just the name of the package maintainer, the version number, and then I modify the `uninstallkey` in setup.py (variable and function parameter).

After saving these two files, I run the command:

`wapt-get build-upload -ic:\waptdev\yourprefix-ganttproject`.

Everything goes well. It creates the `.wapt` file, then asks me for the server username and password, but the script ends with the error I mentioned earlier.

Indeed, I can confirm that if I use "import from file" from the console on the development machine, the package is successfully imported into the repository.

The development machine on which I perform these operations is, of course, not the Windows machine used as the administration console (as specified in the documentation).

Indeed, I don't really have an explanation; I've never encountered this problem.

The error returned is a 502 error:
https://fr.wikipedia.org/wiki/Liste_des ... pplication.

The fact that it works when imported as a file means that the upload is working.


If you are in the testing phase with Wapt, we advise you to go directly to version 1.5 without going through 1.3.13.

There was a bug with package uploads that has been fixed.

This will also save you from having to migrate from 1.3 to 1.5

: https://www.wapt.fr/wapt-1.5/Installati ... nux-debian