From vw at zen.net.au  Sun Jul  3 00:28:47 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Sun, 3 Jul 2022 04:28:47 +0000
Subject: [Borgbackup] init repo using keyfile
Message-ID: <SY4PR01MB5753ACC4C47EA81F9EF87E39E1BF9@SY4PR01MB5753.ausprd01.prod.outlook.com>

Hello,

I'm trying to init a repository using the keyfile option.

My understanding is that the syntax for the command is:
sudo borg init --encryption=keyfile /path to repo

However, when I try this, I am getting the following response:
borg init: error: the following arguments are required: -e/--encryption

I've had a look at the detailed help for init, and unfortunately I don't find the info helpful.

Would appreciate clarification on what I am doing wrong here.

Thank you

Regards,
Vaughan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220703/e63d7d90/attachment.html>

From clickwir at gmail.com  Sun Jul  3 01:14:08 2022
From: clickwir at gmail.com (Zack Coffey)
Date: Sat, 2 Jul 2022 23:14:08 -0600
Subject: [Borgbackup] init repo using keyfile
In-Reply-To: <SY4PR01MB5753ACC4C47EA81F9EF87E39E1BF9@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB5753ACC4C47EA81F9EF87E39E1BF9@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <CAA8KC9+N+Rt4GBbOcSpmOXFGBVU-w9U7YddLfFiYWQZvxhLV6Q@mail.gmail.com>

In your command, you are using this -? but in the document it says to use
this --

Maybe you can't see on your screen or with what font you have, but those
are 2 different things. You need to use --

On Sat, Jul 2, 2022 at 10:28 PM Vaughan Wickham <vw at zen.net.au> wrote:

> Hello,
>
>
>
> I?m trying to init a repository using the keyfile option.
>
>
>
> My understanding is that the syntax for the command is:
>
> sudo borg init -?encryption=keyfile /path to repo
>
>
>
> However, when I try this, I am getting the following response:
>
> borg init: error: the following arguments are required: -e/--encryption
>
>
>
> I?ve had a look at the detailed help for init, and unfortunately I don?t
> find the info helpful.
>
>
>
> Would appreciate clarification on what I am doing wrong here.
>
>
>
> Thank you
>
>
>
> Regards,
>
> Vaughan
>
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220702/df734273/attachment.html>

From vw at zen.net.au  Sun Jul  3 01:23:38 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Sun, 3 Jul 2022 05:23:38 +0000
Subject: [Borgbackup] init repo using keyfile
In-Reply-To: <CAA8KC9+N+Rt4GBbOcSpmOXFGBVU-w9U7YddLfFiYWQZvxhLV6Q@mail.gmail.com>
References: <SY4PR01MB5753ACC4C47EA81F9EF87E39E1BF9@SY4PR01MB5753.ausprd01.prod.outlook.com>
 <CAA8KC9+N+Rt4GBbOcSpmOXFGBVU-w9U7YddLfFiYWQZvxhLV6Q@mail.gmail.com>
Message-ID: <SY4PR01MB5753FDA3F2D62D60CA0828F6E1BF9@SY4PR01MB5753.ausprd01.prod.outlook.com>

Thanks Zack!

I new that it had to be something obvious, but I needed a fresh set of eyes.

Regards,
Vaughan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220703/cbf14247/attachment-0001.html>

From vw at zen.net.au  Sun Jul  3 21:25:02 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Mon, 4 Jul 2022 01:25:02 +0000
Subject: [Borgbackup] Trying to mount a repository
Message-ID: <SY4PR01MB575376A0A940EEFDEA3099F9E1BE9@SY4PR01MB5753.ausprd01.prod.outlook.com>

Hello,

I'm trying to mount a repository to /tmp/Borg

So, I do the following


  *   mkdir /tmp/Borg
  *   sudo borg mount  /media/zen/REAR-000/Borg /tmp/Borg
     *   Borg appears to process the command, I am prompted for the passphrase and there are no Borg errors
     *   But I can't access /tmp/Borg
        *   Permission denied
        *   The permissions of "Borg" could not be determined

I have tried the following, while the repository is mounted

  *   sudo chown -R $USER: /tmp/Borg
  *   sudo chmod 755 /tmp/Borg
     *   The files that have been mounted, are displayed while these commands are processed, but afterwards /tmp/Borg remains inaccessible

I have then tried the following, while the repository is unmounted

  *   sudo chown -R $USER: /tmp/Borg
  *   sudo chmod 755 /tmp/Borg
  *   This time the commands are successful, but after mounting the repository, /tmp/Borg becomes inaccessible, as before

Regards,
Vaughan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220704/4e6ddfe8/attachment.html>

From tschoening at am-soft.de  Mon Jul  4 03:24:58 2022
From: tschoening at am-soft.de (=?windows-1250?Q?Thorsten_Sch=F6ning?=)
Date: Mon, 4 Jul 2022 09:24:58 +0200
Subject: [Borgbackup] Trying to mount a repository
In-Reply-To: <SY4PR01MB575376A0A940EEFDEA3099F9E1BE9@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB575376A0A940EEFDEA3099F9E1BE9@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <522756259.20220704092458@am-soft.de>

Guten Tag Vaughan Wickham,
am Montag, 4. Juli 2022 um 03:25 schrieben Sie:

>   *   mkdir /tmp/Borg
>   *   sudo borg mount  /media/zen/REAR-000/Borg /tmp/Borg
>      *   Borg appears to process the command, I am prompted for the
> passphrase and there are no Borg errors
>      *   But I can't access /tmp/Borg
>         *   Permission denied
>         *   The permissions of "Borg" could not be determined

Mounts are per user, so if you use SUDO to mount, you need some SUDOed
shell to access the mounted content as well. Changing permissions on
dirs won't help, those don't forward into the BORG backups AFAIK
anyway. In the easiest case, try both MOUNT+ACCESS with real root
shells without SUDO and move forward from there.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 (0)515 94 68 - 0
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From tw at waldmann-edv.de  Mon Jul  4 16:04:30 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Mon, 4 Jul 2022 22:04:30 +0200
Subject: [Borgbackup] borgbackup 2.0.0a3 released!
Message-ID: <44b986e3-e763-a1aa-611a-be82b70b3c98@waldmann-edv.de>

borgbackup 2.0.0 alpha3 was released today, please test it carefully!

https://github.com/borgbackup/borg/releases/tag/2.0.0a3



From bkborg at kirk.de  Tue Jul 12 04:36:52 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Tue, 12 Jul 2022 10:36:52 +0200
Subject: [Borgbackup] Local Exception
Message-ID: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>

Hello,
after running borg using Vorta, I am just trying borg from the command
line in order to learn how to set up the scripts to run borg from
crontab. Yesterday, it was running well, except some errors in my
scripts. Today, I deleted all data using dolphin to begin from scratch
and tried

> borg init -e=none home/boris/Dokumente/temp/BorgBackup

and got:

> Local Exception
> Traceback (most recent call last):
>   File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5115, in main
>     exit_code = archiver.run(args)
>   File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5046, in run
>     return set_ec(func(args))
>   File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
>     with repository:
>   File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 198, in __enter__
>     self.create(self.path)
>   File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 297, in create
>     self.save_config(path, config)
>   File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 322, in save_config
>     with SaveFile(config_path) as fd:
>   File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>     os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'
> 
> Platform: Linux linux-t560b 5.14.14-1-default #1 SMP Thu Oct 21 05:05:03 UTC 2021 (2b5383f) x86_64
> Linux: Unknown Linux  
> Borg: 1.2.1  Python: CPython 3.10.5 msgpack: 1.0.4 fuse: llfuse 1.4.1 [pyfuse3,llfuse]
> PID: 3768  CWD: /home/boris
> sys.argv: ['/usr/bin/borg', 'init', '-e=none', '/home/boris/Dokumente/temp/BorgBackup/']
> SSH_ORIGINAL_COMMAND: None


What does that mean?



-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tw at waldmann-edv.de  Thu Jul 14 10:29:00 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Thu, 14 Jul 2022 16:29:00 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
Message-ID: <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>

>> Local Exception
>> Traceback (most recent call last):
>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5115, in main
>>      exit_code = archiver.run(args)
>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5046, in run
>>      return set_ec(func(args))
>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
>>      with repository:
>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 198, in __enter__
>>      self.create(self.path)
>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 297, in create
>>      self.save_config(path, config)
>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 322, in save_config
>>      with SaveFile(config_path) as fd:
>>    File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>      os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'

What filesystem is that file / that directory on?

If it is cifs / smbfs or something else that is not supporting chmod, 
then this error is known already (and fixed, but not released yet, will 
be in 1.2.2):

https://github.com/borgbackup/borg/issues/6786

Patch:

https://github.com/ThomasWaldmann/borg/commit/89e24847b96e724f88d19b0652427c558bf304ce


From bkborg at kirk.de  Thu Jul 14 12:27:46 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Thu, 14 Jul 2022 18:27:46 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
Message-ID: <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>

Hello,
/ is on BTRFS, /home is on XFS, both support chmod.

One week before, it worked on the same machine. Maybe something is
broken. If I only could find the one (?) file that is broken/missing?


Am 14.07.22 um 16:29 schrieb Thomas Waldmann:
>>> Local Exception
>>> Traceback (most recent call last):
>>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5115, in main
>>>      exit_code = archiver.run(args)
>>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5046, in run
>>>      return set_ec(func(args))
>>>    File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
>>>      with repository:
>>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 198, in __enter__
>>>      self.create(self.path)
>>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 297, in create
>>>      self.save_config(path, config)
>>>    File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 322, in save_config
>>>      with SaveFile(config_path) as fd:
>>>    File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>>      os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'
> 
> What filesystem is that file / that directory on?
> 
> If it is cifs / smbfs or something else that is not supporting chmod, 
> then this error is known already (and fixed, but not released yet, will 
> be in 1.2.2):
> 
> https://github.com/borgbackup/borg/issues/6786
> 
> Patch:
> 
> https://github.com/ThomasWaldmann/borg/commit/89e24847b96e724f88d19b0652427c558bf304ce
> 
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
> 

-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tschoening at am-soft.de  Thu Jul 14 13:07:38 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Thu, 14 Jul 2022 19:07:38 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
Message-ID: <64697895.20220714190738@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Dienstag, 12. Juli 2022 um 10:36 schrieben Sie:

>>   File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>     os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'

You should provide some additional details: The user you are executing
the command under, the umask you are exeuting under, the permissions
of the directory etc.

> woami
> umask
> ls -lisa home/boris/Dokumente/temp/BorgBackup/

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 (0)515 94 68 - 0
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From tw at waldmann-edv.de  Thu Jul 14 16:38:18 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Thu, 14 Jul 2022 22:38:18 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
Message-ID: <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>

> / is on BTRFS, /home is on XFS, both support chmod.

And the repo is not on a separate fs, but also on XFS?

> One week before, it worked on the same machine. Maybe something is
> broken. If I only could find the one (?) file that is broken/missing?

borg <= 1.2.0 had a bug (or rather "unpretty behaviour") and the fix 
introduced that chmod you see in the traceback (in borg 1.2.1).

The tmp file you see there is created by borg right before it gets 
written to, chmoded and renamed over the old config file. This is to 
avoid empty or partially written config files in case something goes 
wrong. The rename op is atomic, so you either keep the old config file 
or you will have the new config file, but other states are not possible.

And as a file owner, one is allowed to chmod ones own files.

The chmod is because the python stdlib "make a tempfile" code uses very 
strict permissions on the temp file. But in the end, we want the mode to 
look like on a normally created file (which is 666 & ~umask).

>>>> Local Exception
>>>> Traceback (most recent call last):
>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5115, in main
>>>>       exit_code = archiver.run(args)
>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5046, in run
>>>>       return set_ec(func(args))
>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
>>>>       with repository:
>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 198, in __enter__
>>>>       self.create(self.path)
>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 297, in create
>>>>       self.save_config(path, config)
>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 322, in save_config
>>>>       with SaveFile(config_path) as fd:
>>>>     File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>>>       os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>>>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'

From tw at waldmann-edv.de  Sun Jul 17 10:46:41 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Sun, 17 Jul 2022 16:46:41 +0200
Subject: [Borgbackup] borgbackup 2.0.0 alpha 4 release
Message-ID: <48838c54-8aa3-322a-bead-c4f3a567b32e@waldmann-edv.de>

see there:

https://github.com/borgbackup/borg/releases/tag/2.0.0a4

From bkborg at kirk.de  Sun Jul 17 11:19:24 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 17 Jul 2022 17:19:24 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
Message-ID: <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>

Hello,

Am 14.07.22 um 22:38 schrieb Thomas Waldmann:
>> / is on BTRFS, /home is on XFS, both support chmod.
> 
> And the repo is not on a separate fs, but also on XFS?

yes; the only filesystems used here are btrfs and xfs. I plan to use
ext4 via sshfs after my tests work reliably.


>> One week before, it worked on the same machine. Maybe something is
>> broken. If I only could find the one (?) file that is broken/missing?
> 
> borg <= 1.2.0 had a bug (or rather "unpretty behaviour") and the fix 
> introduced that chmod you see in the traceback (in borg 1.2.1).

The version installed is borgbackup-1.2.1-2.1.x86_64.


> The tmp file you see there is created by borg right before it gets 
> written to, chmoded and renamed over the old config file. This is to 
> avoid empty or partially written config files in case something goes 
> wrong. The rename op is atomic, so you either keep the old config file 
> or you will have the new config file, but other states are not possible.
> 
> And as a file owner, one is allowed to chmod ones own files.

So everything should work fine.


> The chmod is because the python stdlib "make a tempfile" code uses very 
> strict permissions on the temp file. But in the end, we want the mode to 
> look like on a normally created file (which is 666 & ~umask).

umask is 0022


>>>>> Local Exception
>>>>> Traceback (most recent call last):
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5115, in main
>>>>>       exit_code = archiver.run(args)
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 5046, in run
>>>>>       return set_ec(func(args))
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/archiver.py", line 168, in wrapper
>>>>>       with repository:
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 198, in __enter__
>>>>>       self.create(self.path)
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 297, in create
>>>>>       self.save_config(path, config)
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/repository.py", line 322, in save_config
>>>>>       with SaveFile(config_path) as fd:
>>>>>     File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>>>>       os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>>>>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
> 

-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From bkborg at kirk.de  Sun Jul 17 11:24:03 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 17 Jul 2022 17:24:03 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <64697895.20220714190738@am-soft.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <64697895.20220714190738@am-soft.de>
Message-ID: <813e7223-6eed-9309-9a12-4866beb73d38@kirk.de>

Hello,

Am 14.07.22 um 19:07 schrieb Thorsten Sch?ning:
> Guten Tag Boris Kirkorowicz,
> am Dienstag, 12. Juli 2022 um 10:36 schrieben Sie:
> 
>>>   File "/usr/lib64/python3.10/site-packages/borg/platform/base.py", line 248, in __exit__
>>>     os.chmod(self.tmp_fname, mode=0o666 & ~ umask)
>>> PermissionError: [Errno 1] Operation not permitted: '/home/boris/Dokumente/temp/BorgBackup/config-bsdwfcdw.tmp'
> 
> You should provide some additional details: The user you are executing
> the command under, the umask you are exeuting under, the permissions
> of the directory etc.
> 
>> woami
>> umask
>> ls -lisa home/boris/Dokumente/temp/BorgBackup/

Here we go:
> boris at linux-t560b:~> whoami
> boris
> boris at linux-t560b:~> umask
> 0022
> boris at linux-t560b:~> ls -lisa /home/boris/Dokumente/temp/BorgBackup/
> insgesamt 4
> 1280375379 0 drwxrwx---  2 boris users    6 16. Jul 15:59 .
> 1510334852 4 drwxrw---- 22 boris users 4096  9. Jul 23:40 ..


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From imperator at jedimail.de  Sun Jul 17 11:47:24 2022
From: imperator at jedimail.de (Sascha Ternes)
Date: Sun, 17 Jul 2022 17:47:24 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
Message-ID: <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>

Hi Boris!

Am 17.07.22 um 17:19 schrieb Boris Kirkorowicz:
> I plan to use
> ext4 via sshfs after my tests work reliably.

If you REALLY want to use SSHFS and not use Borg with a SSH repository, 
note that SSHFS has some restrictions. See here:

https://borgbackup.readthedocs.io/en/stable/deployment/pull-backup.html#sshfs

Sascha

From bkborg at kirk.de  Sun Jul 17 12:12:35 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 17 Jul 2022 18:12:35 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
Message-ID: <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>

Hello,

Am 17.07.22 um 17:47 schrieb Sascha Ternes:
> Hi Boris!
> 
> Am 17.07.22 um 17:19 schrieb Boris Kirkorowicz:
>> I plan to use
>> ext4 via sshfs after my tests work reliably.
> 
> If you REALLY want to use SSHFS and not use Borg with a SSH repository, 
> note that SSHFS has some restrictions. See here:
> 
> https://borgbackup.readthedocs.io/en/stable/deployment/pull-backup.html#sshfs
> 
> Sascha

thank You for this hint. As far as I understand, this refers to a setup
where borg is running on the remote machine pulling the original data
over sshfs from the client machine to store them in a repository on it's
local disks. This includes the risk that the client's file system
features might not be transferred completely, so the restore might fail.
Did I get it right?

If I set it up the other way, that means borg is running on the client
machine, storing it's local data to the repository at the remote host
using sshfs, is this expected to work flawlessly?


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From imperator at jedimail.de  Sun Jul 17 12:17:41 2022
From: imperator at jedimail.de (Sascha Ternes)
Date: Sun, 17 Jul 2022 18:17:41 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
 <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
Message-ID: <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>

Am 17.07.22 um 18:12 schrieb Boris Kirkorowicz:
> Am 17.07.22 um 17:47 schrieb Sascha Ternes:
>> If you REALLY want to use SSHFS and not use Borg with a SSH repository,
>> note that SSHFS has some restrictions. See here:
>>
>> https://borgbackup.readthedocs.io/en/stable/deployment/pull-backup.html#sshfs

> thank You for this hint. As far as I understand, this refers to a setup
> where borg is running on the remote machine pulling the original data
> over sshfs from the client machine to store them in a repository on it's
> local disks. This includes the risk that the client's file system
> features might not be transferred completely, so the restore might fail.
> Did I get it right?

> If I set it up the other way, that means borg is running on the client
> machine, storing it's local data to the repository at the remote host
> using sshfs, is this expected to work flawlessly?

No, I just wanted to say that SSHFS does not support all of Borg's 
features like ACL or xattrs, which is explained there. This has nothing 
to do with pull mode.

Sascha

From bkborg at kirk.de  Sun Jul 17 15:14:10 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 17 Jul 2022 21:14:10 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
 <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
 <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>
Message-ID: <6f88099b-b8e8-adbe-7588-b66001302d0a@kirk.de>

Hi Sascha,
does borg use these features for the files the repos consist of, or does
it just effect the files that er stored in these repo files?


Am 17.07.22 um 18:17 schrieb Sascha Ternes:
> Am 17.07.22 um 18:12 schrieb Boris Kirkorowicz:
>> Am 17.07.22 um 17:47 schrieb Sascha Ternes:
>>> If you REALLY want to use SSHFS and not use Borg with a SSH repository,
>>> note that SSHFS has some restrictions. See here:
>>>
>>> https://borgbackup.readthedocs.io/en/stable/deployment/pull-backup.html#sshfs
> 
>> thank You for this hint. As far as I understand, this refers to a setup
>> where borg is running on the remote machine pulling the original data
>> over sshfs from the client machine to store them in a repository on it's
>> local disks. This includes the risk that the client's file system
>> features might not be transferred completely, so the restore might fail.
>> Did I get it right?
> 
>> If I set it up the other way, that means borg is running on the client
>> machine, storing it's local data to the repository at the remote host
>> using sshfs, is this expected to work flawlessly?
> 
> No, I just wanted to say that SSHFS does not support all of Borg's 
> features like ACL or xattrs, which is explained there. This has nothing 
> to do with pull mode.
> 
> Sascha
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
> 

-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tschoening at am-soft.de  Mon Jul 18 02:11:48 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Mon, 18 Jul 2022 08:11:48 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <6f88099b-b8e8-adbe-7588-b66001302d0a@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
 <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
 <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>
 <6f88099b-b8e8-adbe-7588-b66001302d0a@kirk.de>
Message-ID: <1332429262.20220718081148@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Sonntag, 17. Juli 2022 um 21:14 schrieben Sie:

> does borg use these features for the files the repos consist of, or does
> it just effect the files that er stored in these repo files?

AFAIK ACLs, XATRRs, INODEs etc. only refer to the files being backed
up, those things might not be properly handled by SSHFS. Additionally,
SSHFS is unmaintained right now:

> This is the last release from the current maintainer. SSHFS is now
> no longer maintained or developed.[...]

https://github.com/libfuse/sshfs/releases

Therefore, with your use-case in mind, it might make sense to
reconsider using SSHFS at all. Things can easily be replaced by
installing and using BORG in serve mode at the one host you considered
consuming using SSHFS. Some hosters like HETZNER provide a similar
setup.

https://borgbackup.readthedocs.io/en/stable/usage/serve.html
https://community.hetzner.com/tutorials/install-and-configure-borgbackup/de

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 (0)515 94 68 - 0
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From lazyvirus at gmx.com  Mon Jul 18 06:33:27 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Mon, 18 Jul 2022 12:33:27 +0200
Subject: [Borgbackup] failed to build
Message-ID: <20220718123327.2e8cf141@msi.defcon1.lan>

debian bullseye
======================

Hi,

I uninstalled 1.1.18 to replace it with 1.2.1, checked all
dependencies were installed, but pip3 is failing and I don't
know why.

As it is a long output it is attached as a text file.

So, if you have a solution, I'll take it.

Jean-Yves
-------------- next part --------------
# pip3 install borgbackup
Collecting borgbackup
  Using cached borgbackup-1.2.1.tar.gz (4.0 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: packaging in /usr/lib/python3/dist-packages (from borgbackup) (20.9)
Requirement already satisfied: msgpack!=1.0.1,<=1.0.4,>=0.5.6 in /usr/lib/python3/dist-packages (from borgbackup) (1.0.0)
Building wheels for collected packages: borgbackup
  Building wheel for borgbackup (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  ?? Building wheel for borgbackup (pyproject.toml) did not run successfully.
  ??? exit code: 1
  ??????> [373 lines of output]
      Detected OpenSSL [via pkg-config]
      Detected and preferring liblz4 [via pkg-config]
      Detected and preferring libzstd [via pkg-config]
      Detected and preferring libxxhash [via pkg-config]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-39
      creating build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/__main__.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/repository.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/lrucache.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/archive.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/locking.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/fuse_impl.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/_version.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/cache.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/constants.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/nanorst.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/upgrader.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/platformflags.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/fuse.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/__init__.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/archiver.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/selftest.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/remote.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/xattr.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/patterns.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/version.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/shellpattern.py -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/logger.py -> build/lib.linux-x86_64-cpython-39/borg
      creating build/lib.linux-x86_64-cpython-39/borg/crypto
      copying src/borg/crypto/file_integrity.py -> build/lib.linux-x86_64-cpython-39/borg/crypto
      copying src/borg/crypto/__init__.py -> build/lib.linux-x86_64-cpython-39/borg/crypto
      copying src/borg/crypto/key.py -> build/lib.linux-x86_64-cpython-39/borg/crypto
      copying src/borg/crypto/nonces.py -> build/lib.linux-x86_64-cpython-39/borg/crypto
      copying src/borg/crypto/keymanager.py -> build/lib.linux-x86_64-cpython-39/borg/crypto
      creating build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/checks.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/errors.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/__init__.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/parseformat.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/manifest.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/fs.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/yes.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/time.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/misc.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/msgpack.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/datastruct.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/progress.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      copying src/borg/helpers/process.py -> build/lib.linux-x86_64-cpython-39/borg/helpers
      creating build/lib.linux-x86_64-cpython-39/borg/platform
      copying src/borg/platform/__init__.py -> build/lib.linux-x86_64-cpython-39/borg/platform
      copying src/borg/platform/xattr.py -> build/lib.linux-x86_64-cpython-39/borg/platform
      copying src/borg/platform/base.py -> build/lib.linux-x86_64-cpython-39/borg/platform
      creating build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/repository.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/lrucache.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/archive.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/item.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/locking.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/benchmark.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/file_integrity.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/cache.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/nanorst.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/hashindex.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/upgrader.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/compress.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/helpers.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/__init__.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/chunker_pytest.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/archiver.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/crypto.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/platform.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/remote.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/xattr.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/key.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/patterns.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/nonces.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/efficient_collection_queue.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/version.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/shellpattern.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/logger.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/checksums.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/chunker.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      copying src/borg/testsuite/chunker_slow.py -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      creating build/lib.linux-x86_64-cpython-39/borg/algorithms
      copying src/borg/algorithms/__init__.py -> build/lib.linux-x86_64-cpython-39/borg/algorithms
      running egg_info
      writing src/borgbackup.egg-info/PKG-INFO
      writing dependency_links to src/borgbackup.egg-info/dependency_links.txt
      writing entry points to src/borgbackup.egg-info/entry_points.txt
      writing requirements to src/borgbackup.egg-info/requires.txt
      writing top-level names to src/borgbackup.egg-info/top_level.txt
      listing git files failed - pretending there aren't any
      reading manifest file 'src/borgbackup.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      warning: no previously-included files found matching '.coafile'
      warning: no previously-included files found matching '.editorconfig'
      warning: no previously-included files found matching '.gitattributes'
      warning: no previously-included files found matching '.gitignore'
      warning: no previously-included files found matching '.mailmap'
      warning: no previously-included files found matching 'Vagrantfile'
      no previously-included directories found matching '.github'
      adding license file 'LICENSE'
      adding license file 'AUTHORS'
      writing manifest file 'src/borgbackup.egg-info/SOURCES.txt'
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.lz4.lib' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.lz4.lib' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.lz4.lib' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.lz4.lib' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.xxh64' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.xxh64' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.xxh64' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.xxh64' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.common' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.common' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.common' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.common' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.compress' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.compress' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.compress' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.compress' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.decompress' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.decompress' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.decompress' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.decompress' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.deprecated' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.deprecated' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.deprecated' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.deprecated' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.dictBuilder' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.dictBuilder' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.dictBuilder' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.dictBuilder' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.algorithms.zstd.lib.legacy' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.algorithms.zstd.lib.legacy' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.algorithms.zstd.lib.legacy' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.algorithms.zstd.lib.legacy' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      /usr/local/lib/python3.9/dist-packages/setuptools/command/build_py.py:153: SetuptoolsDeprecationWarning:     Installing 'borg.cache_sync' as data is deprecated, please list it in `packages`.
          !!
      
      
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'borg.cache_sync' as an importable package,
          but it is not listed in the `packages` configuration of setuptools.
      
          'borg.cache_sync' has been automatically added to the distribution only
          because it may contain data files, but this behavior is likely to change
          in future versions of setuptools (and therefore is considered deprecated).
      
          Please make sure that 'borg.cache_sync' is included as a package by using
          the `packages` configuration field or the proper discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
      
          You can read more about "package discovery" and "data files" on setuptools
          documentation page.
      
      
      !!
      
        check.warn(importable)
      copying src/borg/paperkey.html -> build/lib.linux-x86_64-cpython-39/borg
      copying src/borg/testsuite/attic.tar.gz -> build/lib.linux-x86_64-cpython-39/borg/testsuite
      running build_ext
      building 'borg.crypto.low_level' extension
      error: unknown file type '.pyx' (from 'src/borg/crypto/low_level.pyx')
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for borgbackup
Failed to build borgbackup
ERROR: Could not build wheels for borgbackup, which is required to install pyproject.toml-based projects

From tw at waldmann-edv.de  Mon Jul 18 06:43:40 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Mon, 18 Jul 2022 12:43:40 +0200
Subject: [Borgbackup] failed to build
In-Reply-To: <20220718123327.2e8cf141@msi.defcon1.lan>
References: <20220718123327.2e8cf141@msi.defcon1.lan>
Message-ID: <afa7de31-cca9-fc17-b2ff-56456aa64598@waldmann-edv.de>

> I uninstalled 1.1.18 to replace it with 1.2.1, checked all
> dependencies were installed, but pip3 is failing and I don't
> know why.
> 
> As it is a long output it is attached as a text file.

Never seen that kind and amount of warnings relating to borg.algorithms 
content.

But the error is close to the end of the log:

error: unknown file type '.pyx' (from 'src/borg/crypto/low_level.pyx')

This is a bit unusual also, because the corresponding .c file should be 
used for a borg release version (so a C compiler is sufficient) and thus 
the .pyx should not be needed to get processed at all (which requires to 
have Cython installed).

From lazyvirus at gmx.com  Mon Jul 18 06:57:03 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Mon, 18 Jul 2022 12:57:03 +0200
Subject: [Borgbackup] failed to build
In-Reply-To: <afa7de31-cca9-fc17-b2ff-56456aa64598@waldmann-edv.de>
References: <20220718123327.2e8cf141@msi.defcon1.lan>
 <afa7de31-cca9-fc17-b2ff-56456aa64598@waldmann-edv.de>
Message-ID: <20220718125703.52a7172e@msi.defcon1.lan>

On Mon, 18 Jul 2022 12:43:40 +0200
Thomas Waldmann <tw at waldmann-edv.de> wrote:

> > I uninstalled 1.1.18 to replace it with 1.2.1, checked all
> > dependencies were installed, but pip3 is failing and I don't
> > know why.
> >
> > As it is a long output it is attached as a text file.
>
> Never seen that kind and amount of warnings relating to
> borg.algorithms content.

Me neither, I had some errors in the past but nothing close to that.

> But the error is close to the end of the log:
>
> error: unknown file type '.pyx' (from 'src/borg/crypto/low_level.pyx')
>
> This is a bit unusual also, because the corresponding .c file should
> be used for a borg release version (so a C compiler is sufficient)
> and thus the .pyx should not be needed to get processed at all (which
> requires to have Cython installed).

That's what I thought, but the problem is :
ii  cython3        0.29.21-3+b1 amd64        C-Extensions for Python 3

Cython's installed (and to make sure there was no glitch, I reinstalled
it)

As far as I remember, nothing about Python3 was touched or tweaked since
way before BB version 1.1.18.

I also need to be able to make a backup ASAP following big changes in a
appli of mine.

Jean-Yves

From bkborg at kirk.de  Tue Jul 19 02:02:03 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Tue, 19 Jul 2022 08:02:03 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <1332429262.20220718081148@am-soft.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
 <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
 <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>
 <6f88099b-b8e8-adbe-7588-b66001302d0a@kirk.de>
 <1332429262.20220718081148@am-soft.de>
Message-ID: <765a3918-ef6c-10ca-7619-b99987bdf2af@kirk.de>

Hello,

Am 18.07.22 um 08:11 schrieb Thorsten Sch?ning:
> Guten Tag Boris Kirkorowicz,
> am Sonntag, 17. Juli 2022 um 21:14 schrieben Sie:
> 
>> does borg use these features for the files the repos consist of, or does
>> it just effect the files that er stored in these repo files?
> 
> AFAIK ACLs, XATRRs, INODEs etc. only refer to the files being backed
> up, those things might not be properly handled by SSHFS. Additionally,
> SSHFS is unmaintained right now:

as long as the backup source files are not transferred via sshfs (only
the repo files are) that should not be relevant. Or did I get something
wrong?


>> This is the last release from the current maintainer. SSHFS is now
>> no longer maintained or developed.[...]
> 
> https://github.com/libfuse/sshfs/releases
> 
> Therefore, with your use-case in mind, it might make sense to
> reconsider using SSHFS at all. Things can easily be replaced by
> installing and using BORG in serve mode at the one host you considered
> consuming using SSHFS. Some hosters like HETZNER provide a similar
> setup.

The planned target is an existing NAS device. As far as I can see, there
is no borg for this platform, but ssh and sshfs works.


> https://borgbackup.readthedocs.io/en/stable/usage/serve.html
> https://community.hetzner.com/tutorials/install-and-configure-borgbackup/de
> 
> Mit freundlichen Gr??en
> 
> Thorsten Sch?ning


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tschoening at am-soft.de  Tue Jul 19 03:19:16 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Tue, 19 Jul 2022 09:19:16 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <765a3918-ef6c-10ca-7619-b99987bdf2af@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <50747d03-788b-b55e-bb89-4f7ed98799bb@kirk.de>
 <6ceaf280-b8cd-dc6a-de4d-53c5607c38f4@waldmann-edv.de>
 <61c81332-9ce2-8883-88d8-b960b51dd6fe@kirk.de>
 <11dd6637-4e23-abaa-1352-553b0d42f41c@jedimail.de>
 <278fa1a8-26df-ccda-257b-6f62f65d506e@kirk.de>
 <6392bccb-323c-822d-0a9a-9c878efc3e88@jedimail.de>
 <6f88099b-b8e8-adbe-7588-b66001302d0a@kirk.de>
 <1332429262.20220718081148@am-soft.de>
 <765a3918-ef6c-10ca-7619-b99987bdf2af@kirk.de>
Message-ID: <2810188382.20220719091916@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Dienstag, 19. Juli 2022 um 08:02 schrieben Sie:

> as long as the backup source files are not transferred via sshfs (only
> the repo files are) that should not be relevant. Or did I get something
> wrong?

Regarding ACLs etc. you are correct. But as SSHFS is unmaintained, it
makes sense to reconsider starting new projects based on that, though.

> The planned target is an existing NAS device. As far as I can see, there
> is no borg for this platform, but ssh and sshfs works.

You did try all the various Linux and ARM-based approaches, not only
referenced in GitHub, but the other docs as well?

> ARM binaries are built by Johann Bauer, see: https://borg.bauerj.eu/
https://borgbackup.readthedocs.io/en/1.2-maint/installation.html#standalone-binary

I've e.g. was able o at least execute "borg-linuxold64" successfully
on some Synology x86_64 with DSM 6.x. So only because your concrete
system might not be linked, doesn't necessarily mean it's not working.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 (0)515 94 68 - 0
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From maurizio1018 at gmail.com  Tue Jul 19 07:46:26 2022
From: maurizio1018 at gmail.com (Maurizio Vairani)
Date: Tue, 19 Jul 2022 13:46:26 +0200
Subject: [Borgbackup] Question about saving '~/.config/borg' directory
Message-ID: <CAN0zgYWDX94SQYidN4KvxG22W+-MEdEEuzmUo0uO3COnm_tR_Q@mail.gmail.com>

Hi,


I am new to Borgbackup, I am using it via ssh on FreeBSD. I am backing up
an amd64 laptop on a old i386, it works, really.


I backup the laptop home directory an the current ZFS boot environment. The
archives aren't encrypted.


Do I need to save the laptop's '~/.config/borg' directory elsewhere as well?


It seems that I can access backups even without this directory. Is it
always true?


Thanks

--

Maurizio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220719/1583babe/attachment.html>

From lazyvirus at gmx.com  Sun Jul 24 06:41:58 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 24 Jul 2022 12:41:58 +0200
Subject: [Borgbackup] failed to build - [SOLVED]
In-Reply-To: <20220718123327.2e8cf141@msi.defcon1.lan>
References: <20220718123327.2e8cf141@msi.defcon1.lan>
Message-ID: <20220724124158.311b049d@msi.defcon1.lan>

On Mon, 18 Jul 2022 12:33:27 +0200
Bzzzz <lazyvirus at gmx.com> wrote:

Hi,

Finally, I found the reason why it was failing, it was /tmp
permissions that was triggering all these errors
(rw,nosuid,nodev,noexec,noatime), once remounted suid & exec
(rw,nodev,noatime), borgbackup installed immediately :)

Jean-Yves

> debian bullseye
> ======================
>
> Hi,
>
> I uninstalled 1.1.18 to replace it with 1.2.1, checked all
> dependencies were installed, but pip3 is failing and I don't
> know why.
>
> As it is a long output it is attached as a text file.
>
> So, if you have a solution, I'll take it.
>
> Jean-Yves


From vw at zen.net.au  Wed Jul 27 18:11:20 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Wed, 27 Jul 2022 22:11:20 +0000
Subject: [Borgbackup] init repo question
Message-ID: <SY4PR01MB57539A98CF995B49436F7898E1979@SY4PR01MB5753.ausprd01.prod.outlook.com>

Hello,

I have a Borg backup to a local repository which is working fine.

I'd like to create a second Borg backup to a remote repository.

My question relates to the Borg keys.

When I create the remote repository, do I need to specify anything in relation to the keyfile during the borg init, to ensure that the existing local repository keys are not overwritten?

Thanks

Regards,
Vaughan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220727/090fa53e/attachment.html>

From tschoening at am-soft.de  Thu Jul 28 03:28:11 2022
From: tschoening at am-soft.de (=?windows-1250?Q?Thorsten_Sch=F6ning?=)
Date: Thu, 28 Jul 2022 09:28:11 +0200
Subject: [Borgbackup] init repo question
In-Reply-To: <SY4PR01MB57539A98CF995B49436F7898E1979@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB57539A98CF995B49436F7898E1979@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <16910252158.20220728092811@am-soft.de>

Guten Tag Vaughan Wickham,
am Donnerstag, 28. Juli 2022 um 00:11 schrieben Sie:

> When I create the remote repository, do I need to specify anything
> in relation to the keyfile during the borg init, to ensure that the
> existing local repository keys are not overwritten?

Your question implies you are really storing keys using "keyfile"
inside your home directory, correct? If so, have a look at their file
names in "~/.config/borg/keys". The names depend on the path to the
repo, so in the easiest case you only need to make sure to have
different paths per repo.

There's as well the following FAQ:

> Can I back up to multiple, swapped backup targets?

> It is possible to swap your backup disks if each backup medium is
> assigned its own repository by creating a new one with borg init.

https://borgbackup.readthedocs.io/en/stable/faq.html#can-i-back-up-to-multiple-swapped-backup-targets

While "init" is documented to "create" a keyfile, other places of the
doc read to me like an existing one is kept. Otherwise a scenario with
swapped backup targets using the same path wouldn't be possible at
all.

> When initialized with the init -e keyfile command, Borg needs an
> associated file in $HOME/.config/borg/keys to read and write the
> repository.[...]

https://borgbackup.readthedocs.io/en/stable/internals/data-structures.html#key-files

It just says "needs".

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From bkborg at kirk.de  Thu Jul 28 04:11:10 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Thu, 28 Jul 2022 10:11:10 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
Message-ID: <f1194cf1-5a29-0552-d825-bb068a1a9bc7@kirk.de>

Hi,

Am 14.07.22 um 16:29 schrieb Thomas Waldmann:
> If it is cifs / smbfs or something else that is not supporting chmod, 
> then this error is known already (and fixed, but not released yet, will 
> be in 1.2.2)

is there an estimated timeline for this release?


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tw at waldmann-edv.de  Thu Jul 28 09:30:03 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Thu, 28 Jul 2022 15:30:03 +0200
Subject: [Borgbackup] Local Exception
In-Reply-To: <f1194cf1-5a29-0552-d825-bb068a1a9bc7@kirk.de>
References: <739e5df8-26cd-4e40-df7e-0f5169ccfd6e@kirk.de>
 <c6ba3e7e-2792-6858-3de5-f5bb71bfa0d5@waldmann-edv.de>
 <f1194cf1-5a29-0552-d825-bb068a1a9bc7@kirk.de>
Message-ID: <18dd0e91-1944-060b-140d-6781f5b3f004@waldmann-edv.de>

> Am 14.07.22 um 16:29 schrieb Thomas Waldmann:
>> If it is cifs / smbfs or something else that is not supporting chmod,
>> then this error is known already (and fixed, but not released yet, will
>> be in 1.2.2)
> 
> is there an estimated timeline for this release?

You can estimate it by looking at the 1.2.2 milestone on github.

If the milestone becomes empty (either by solving these tickets or by 
shifthing them to another milestone), a release will happen soon after.

I hope this will be in the near future, but it depends on how many 
people are working on fixing stuff.

From tw at waldmann-edv.de  Sun Aug  7 17:05:41 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Sun, 7 Aug 2022 23:05:41 +0200
Subject: [Borgbackup] borgbackup 2.0.0b1 released!
Message-ID: <73b59001-7599-4bb8-0d93-a5110c74adfd@waldmann-edv.de>

Just released a new borgbackup: the first borg 2 beta.

Please do not run against production repos.

https://github.com/borgbackup/borg/releases/tag/2.0.0b1

From vw at zen.net.au  Wed Aug 10 21:48:59 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Thu, 11 Aug 2022 01:48:59 +0000
Subject: [Borgbackup] borg check - Failed to create/acquire the lock
Message-ID: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>

Hello,

I'm trying to check the repo

I'm using:
sudo borg check /path_to_repo

Getting error: Failed to create/acquire the lock

Have restarted the host. There are no other borg operations running and I haven't yet tried to use borg with-lock myself

After suggestions on how to troubleshoot.

I'm using Borg 1.2.0 on Ubuntu 22.04.1

Regards,
Vaughan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220811/57bfc1bf/attachment.html>

From vw at zen.net.au  Thu Aug 11 02:05:10 2022
From: vw at zen.net.au (Vaughan Wickham)
Date: Thu, 11 Aug 2022 06:05:10 +0000
Subject: [Borgbackup] FW: borg check - Failed to create/acquire the lock
In-Reply-To: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <SY4PR01MB575311409835252504C2E4F4E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>

Possibly this is the answer, if there isn't a way to resolve via a borg command

https://itgrenade.wordpress.com/2020/09/26/borg-backup-error-failed-to-create-acquire-the-lock/

Regards,
Vaughan

From: Vaughan Wickham
Sent: Thursday, 11 August 2022 11:49 AM
To: borgbackup at python.org
Subject: borg check - Failed to create/acquire the lock

Hello,

I'm trying to check the repo

I'm using:
sudo borg check /path_to_repo

Getting error: Failed to create/acquire the lock

Have restarted the host. There are no other borg operations running and I haven't yet tried to use borg with-lock myself

After suggestions on how to troubleshoot.

I'm using Borg 1.2.0 on Ubuntu 22.04.1

Regards,
Vaughan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220811/583f4903/attachment-0001.html>

From tw at waldmann-edv.de  Thu Aug 11 07:15:25 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Thu, 11 Aug 2022 13:15:25 +0200
Subject: [Borgbackup] borg check - Failed to create/acquire the lock
In-Reply-To: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <0a2f5ea2-8e85-5132-8c84-58a549641d90@waldmann-edv.de>

> sudo borg check /path_to_repo

You always run borg that way? as root and using sudo from the same user?

You should always run it the same way, otherwise you are causing a 
permissions mixup (and also potentially using different cache/config dirs).

> Getting error: Failed to create/acquire the lock

That can happen if a borg run crashed (due to a bug, power outage, kill 
-9, disk unplugged, ...). The lock is inside your repo directory.

> Have restarted the host. There are no other borg operations running and 
> I haven?t yet tried to use borg with-lock myself

"with-lock" is for something else (see docs).

But "borg break-lock" (see docs!) is the command that can fix this.


From tw at waldmann-edv.de  Thu Aug 11 07:19:07 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Thu, 11 Aug 2022 13:19:07 +0200
Subject: [Borgbackup] FW: borg check - Failed to create/acquire the lock
In-Reply-To: <SY4PR01MB575311409835252504C2E4F4E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
References: <SY4PR01MB5753839BB8C951ABC513EFD6E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
 <SY4PR01MB575311409835252504C2E4F4E1649@SY4PR01MB5753.ausprd01.prod.outlook.com>
Message-ID: <5a9db37a-0f4f-ff54-022f-f83dcf5496b9@waldmann-edv.de>

> Possibly this is the answer, if there isn?t a way to resolve via a borg 
> command
> 
> https://itgrenade.wordpress.com/2020/09/26/borg-backup-error-failed-to-create-acquire-the-lock/ 
> <https://itgrenade.wordpress.com/2020/09/26/borg-backup-error-failed-to-create-acquire-the-lock/>

No. And there is a command.

That user likely managed to get the permissions mixed up in his 
repository, see the error msg "Permission denied".


From billk at iinet.net.au  Fri Aug 12 16:02:23 2022
From: billk at iinet.net.au (William Kenworthy)
Date: Sat, 13 Aug 2022 04:02:23 +0800
Subject: [Borgbackup] restoring the cache
Message-ID: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>

An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220813/af6727e5/attachment.html>

From lazyvirus at gmx.com  Fri Aug 12 16:21:29 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Fri, 12 Aug 2022 22:21:29 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
Message-ID: <20220812222129.4fd63680@msi.defcon1.lan>

On Sat, 13 Aug 2022 04:02:23 +0800
William Kenworthy <billk at iinet.net.au> wrote:

Hi,
 
> ??? I am taking a backup of a relatively large borg repo, its cache
> and security directory after a successful run (this backup is
> actually stored in another borgbackup repo).? I can reliably restore
> the original repo successfully without cache or security and rebuild
> the cache it if it gets corrupted - however this takes many hours so
> I would like to reuse the cache if possible.
> 
> 1. why does restoring the matching cache, security and repo not work?
> - from reading the docs its tied up with the counter/nonce reuse
> protection?

Because it is automatically tagged with a ~/.cache/borg/CACHEDIR.TAG
file that prevents its backup.
 
> 2. can this be worked around

I backup the configuration and cache DIRs to another server :
cp -a /root/.cache/borg  /SRVS/CLIENT_SAVE_BORG_machine/.cache/

This one is also backed up because the key's on the client :
cp -a /root/.config/borg /SRVS/CLIENT_SAVE_BORG_machine/.config/

Jean-Yves

From billk at iinet.net.au  Sat Aug 13 02:42:29 2022
From: billk at iinet.net.au (William Kenworthy)
Date: Sat, 13 Aug 2022 14:42:29 +0800
Subject: [Borgbackup] restoring the cache
In-Reply-To: <20220812222129.4fd63680@msi.defcon1.lan>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
Message-ID: <4a79052d-a7a9-c3ef-4290-0af161c0052f@iinet.net.au>


On 13/8/22 04:21, Bzzzz wrote:
> On Sat, 13 Aug 2022 04:02:23 +0800
> William Kenworthy <billk at iinet.net.au> wrote:
>
> Hi,
>   
>>  ??? I am taking a backup of a relatively large borg repo, its cache
>> and security directory after a successful run (this backup is
>> actually stored in another borgbackup repo).? I can reliably restore
>> the original repo successfully without cache or security and rebuild
>> the cache it if it gets corrupted - however this takes many hours so
>> I would like to reuse the cache if possible.
>>
>> 1. why does restoring the matching cache, security and repo not work?
>> - from reading the docs its tied up with the counter/nonce reuse
>> protection?
> Because it is automatically tagged with a ~/.cache/borg/CACHEDIR.TAG
> file that prevents its backup.
>   
>> 2. can this be worked around
> I backup the configuration and cache DIRs to another server :
> cp -a /root/.cache/borg  /SRVS/CLIENT_SAVE_BORG_machine/.cache/
>
> This one is also backed up because the key's on the client :
> cp -a /root/.config/borg /SRVS/CLIENT_SAVE_BORG_machine/.config/
>
> Jean-Yves
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup


Thanks, I'll look into it - seems like a solution.

BillK



From billk at iinet.net.au  Sat Aug 13 04:45:16 2022
From: billk at iinet.net.au (William Kenworthy)
Date: Sat, 13 Aug 2022 16:45:16 +0800
Subject: [Borgbackup] restoring the cache
In-Reply-To: <4a79052d-a7a9-c3ef-4290-0af161c0052f@iinet.net.au>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
 <4a79052d-a7a9-c3ef-4290-0af161c0052f@iinet.net.au>
Message-ID: <c3f0e45f-fcfd-b886-ed1f-4f05cf2bf60e@iinet.net.au>


On 13/8/22 14:42, William Kenworthy wrote:
>
> On 13/8/22 04:21, Bzzzz wrote:
>> On Sat, 13 Aug 2022 04:02:23 +0800
>> William Kenworthy <billk at iinet.net.au> wrote:
>>
>> Hi,
>>> ???? I am taking a backup of a relatively large borg repo, its cache
>>> and security directory after a successful run (this backup is
>>> actually stored in another borgbackup repo).? I can reliably restore
>>> the original repo successfully without cache or security and rebuild
>>> the cache it if it gets corrupted - however this takes many hours so
>>> I would like to reuse the cache if possible.
>>>
>>> 1. why does restoring the matching cache, security and repo not work?
>>> - from reading the docs its tied up with the counter/nonce reuse
>>> protection?
>> Because it is automatically tagged with a ~/.cache/borg/CACHEDIR.TAG
>> file that prevents its backup.
>>> 2. can this be worked around
>> I backup the configuration and cache DIRs to another server :
>> cp -a /root/.cache/borg? /SRVS/CLIENT_SAVE_BORG_machine/.cache/
>>
>> This one is also backed up because the key's on the client :
>> cp -a /root/.config/borg /SRVS/CLIENT_SAVE_BORG_machine/.config/
>>
>> Jean-Yves
>> _______________________________________________
>> Borgbackup mailing list
>> Borgbackup at python.org
>> https://mail.python.org/mailman/listinfo/borgbackup
>
>
> Thanks, I'll look into it - seems like a solution.
>
> BillK
>
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup

No luck - I am taking the backup from "/root/.cache/borg/<UUID>" so the 
CACHEDIR.TAG sits outside the root (above the UUID).? When I mount the 
repo, the contents seem complete so so I'll keep looking

BillK



From tschoening at am-soft.de  Sun Aug 14 06:30:01 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 14 Aug 2022 12:30:01 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <20220812222129.4fd63680@msi.defcon1.lan>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
Message-ID: <377574633.20220814123001@am-soft.de>

Guten Tag Bzzzz,
am Freitag, 12. August 2022 um 22:21 schrieben Sie:

> Because it is automatically tagged with a ~/.cache/borg/CACHEDIR.TAG
> file that prevents its backup.

Are you sure about that? Looking at my BorgMatic config, the docs say
that CACHEDIR.TAG is ignored by default:

> # Exclude directories that contain a CACHEDIR.TAG file. See
> # http://www.brynosaurus.com/cachedir/spec.html for details.
> # Defaults to false.
> # exclude_caches: true

Looking at the docs of BorgBackup itself, one needs to provide a
special argument:

> Exclusion options
> --exclude-caches        exclude directories that contain a
> CACHEDIR.TAG file (http://www.bford.info/cachedir/spec.html)

https://borgbackup.readthedocs.io/en/stable/usage/create.html

Looking at my logs, I see that contents of the cache directory seems
to be backed up:

> [2022-08-14 01:29:13,859] INFO: M
> /mnt/[...]/.cache/borg/d5e4f60e42afa70ac681c09ef414cabb679d897919c4ea4655c20a842c065966/config

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From tschoening at am-soft.de  Sun Aug 14 06:29:59 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 14 Aug 2022 12:29:59 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
Message-ID: <1245482186.20220814122959@am-soft.de>

Guten Tag William Kenworthy,
am Freitag, 12. August 2022 um 22:02 schrieben Sie:

> 1. why does restoring the matching cache, security and repo not
> work? - from reading the docs its tied up with the counter/nonce     reuse protection?

I'm having trouble understanding what your actual problem is. Could you
provide some error messages aboput what happens after you restored
things and what you did expect to happen instead?

Additionally, why do you backup the cache into some different repo at
all if you are interested to have it backed up? Using one and the same
repo should make backing up and restoring easier because of less
excludes and stuff.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From lazyvirus at gmx.com  Sun Aug 14 11:02:30 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 14 Aug 2022 17:02:30 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <377574633.20220814123001@am-soft.de>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
 <377574633.20220814123001@am-soft.de>
Message-ID: <20220814170230.36c67c81@msi.defcon1.lan>

On Sun, 14 Aug 2022 12:30:01 +0200
Thorsten Sch?ning <tschoening at am-soft.de> wrote:

> Guten Tag Bzzzz,
> am Freitag, 12. August 2022 um 22:21 schrieben Sie:
> 
> > Because it is automatically tagged with a ~/.cache/borg/CACHEDIR.TAG
> > file that prevents its backup.
> 
> Are you sure about that? Looking at my BorgMatic config, the docs say
> that CACHEDIR.TAG is ignored by default:

If you re-read me carefully, you'll see that it is what I wrote?

However, I'm no so sure anymore as I flipped to 1.2.1 very recently and
there's no more ~/.cache/borg/CACHEDIR.TAG file (unless it is
automatically recreated during the backup).

Jean-Yves

From lazyvirus at gmx.com  Sun Aug 14 11:20:31 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 14 Aug 2022 17:20:31 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <377574633.20220814123001@am-soft.de>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
 <377574633.20220814123001@am-soft.de>
Message-ID: <20220814172031.6e7dc900@msi.defcon1.lan>

On Sun, 14 Aug 2022 12:30:01 +0200
Thorsten Sch?ning <tschoening at am-soft.de> wrote:

[CORRECTION]

I wasn't is the right DIR (~/.config/borg) that never have had an
exclusion file, however, I just tested and there is indeed one into
~/.cache/borg that does not appear in any backup (once SSHFS mounted).

This file contains a signature and an explanation:
Signature: 8a477f037d28d172789f06886806bc99
# This file is a cache directory tag created by Borg.
# For information about cache directory tags, see:
#       http://www.bford.info/cachedir/spec.html

Jean-Yves

From tschoening at am-soft.de  Sun Aug 14 12:43:12 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 14 Aug 2022 18:43:12 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <20220814170230.36c67c81@msi.defcon1.lan>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
 <377574633.20220814123001@am-soft.de>
 <20220814170230.36c67c81@msi.defcon1.lan>
Message-ID: <332638793.20220814184312@am-soft.de>

Guten Tag Bzzzz,
am Sonntag, 14. August 2022 um 17:02 schrieben Sie:

> If you re-read me carefully, you'll see that it is what I wrote?

No, you wrote that the cache directory is NOT backed up by default
because it is tagged with CACHEDIR.TAG. I say the OPPOSITE, it IS
backed up by default and am quoting docs and logs to confirm that.

You simply misunderstood me: The TAG is ignored by default, NOT the
parent directory as you say.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From lazyvirus at gmx.com  Sun Aug 14 13:00:53 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 14 Aug 2022 19:00:53 +0200
Subject: [Borgbackup] restoring the cache
In-Reply-To: <332638793.20220814184312@am-soft.de>
References: <6147b55b-11df-9d5b-c317-d24ff1d1f095@iinet.net.au>
 <20220812222129.4fd63680@msi.defcon1.lan>
 <377574633.20220814123001@am-soft.de>
 <20220814170230.36c67c81@msi.defcon1.lan>
 <332638793.20220814184312@am-soft.de>
Message-ID: <20220814190053.5e4329f0@msi.defcon1.lan>

On Sun, 14 Aug 2022 18:43:12 +0200
Thorsten Sch?ning <tschoening at am-soft.de> wrote:

> Guten Tag Bzzzz,
> am Sonntag, 14. August 2022 um 17:02 schrieben Sie:
> 
> > If you re-read me carefully, you'll see that it is what I wrote?
> 
> No, you wrote that the cache directory is NOT backed up by default
> because it is tagged with CACHEDIR.TAG. I say the OPPOSITE, it IS
> backed up by default and am quoting docs and logs to confirm that.
> 
> You simply misunderstood me: The TAG is ignored by default, NOT the
> parent directory as you say.

My bad, I forgot one point, the backup script, that I just checked,
it has effectively a line :
	--exclude-caches

> Mit freundlichen Gr??en
> 
> Thorsten Sch?ning

Jean-Yves

From lazyvirus at gmx.com  Mon Aug 29 11:17:10 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Mon, 29 Aug 2022 17:17:10 +0200
Subject: [Borgbackup] Fail to run
Message-ID: <20220829171710.2840be12@msi.defcon1.lan>

Debian bullseye
all libs install
python pkg msgpack not installed
===================================
Hi list,

After a fresh pip3 install borgbackup (v.1.2.2), it fails on a brand
new repo with these messages :

A /SDC-PRECONVERT.gpt
Local Exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
5159, in main exit_code = archiver.run(args)
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
5090, in run return set_ec(func(args))
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
183, in wrapper return method(self, args, repository=repository,
**kwargs) File
"/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line 675, in
do_create create_inner(archive, cache, fso) File
"/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line 608, in
create_inner self._rec_walk(path=path, parent_fd=parent_fd, name=name,
File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
820, in _rec_walk self._rec_walk( File
"/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line 786, in
_rec_walk status = self._process_any(path=path, parent_fd=parent_fd,
name=name, st=st, fso=fso, cache=cache, File
"/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line 688, in
_process_any return fso.process_file(path=path, parent_fd=parent_fd,
name=name, st=st, cache=cache) File
"/usr/local/lib/python3.9/dist-packages/borg/archive.py", line 1434, in
process_file self.process_file_chunks(item, cache, self.stats,
self.show_progress, backup_io_iter(self.chunker.chunkify(None, fd)))
File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1261, in process_file_chunks item.chunks.append(chunk_processor(chunk))
File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1249, in chunk_processor chunk_entry = cache.add_chunk(chunk_id, data,
stats, wait=False) File
"/usr/local/lib/python3.9/dist-packages/borg/cache.py", line 949, in
add_chunk data = self.key.encrypt(chunk) File
"/usr/local/lib/python3.9/dist-packages/borg/crypto/key.py", line 370,
in encrypt next_iv =
self.nonce_manager.ensure_reservation(self.cipher.next_iv(), File
"/usr/local/lib/python3.9/dist-packages/borg/crypto/nonces.py", line
79, in ensure_reservation repo_free_nonce = self.get_repo_free_nonce()
File "/usr/local/lib/python3.9/dist-packages/borg/crypto/nonces.py",
line 38, in get_repo_free_nonce return self.repository.get_free_nonce()
File "/usr/local/lib/python3.9/dist-packages/borg/repository.py", line
352, in get_free_nonce return int.from_bytes(unhexlify(fd.read()),
byteorder='big') binascii.Error: Non-hexadecimal digit found

Platform: Linux msi 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1
(2022-08-13) x86_64 Linux: Unknown Linux  
Borg: 1.2.2  Python: CPython 3.9.2 msgpack: 1.0.4 fuse: pyfuse3 3.2.0
[pyfuse3,llfuse] PID: 2825473  CWD: /root
sys.argv: ['/usr/local/bin/borg', 'create', '--verbose',
'--exclude-caches', '--show-rc', '--warning', '--filter', 'AME',
'--list', '--stats', '--checkpoint-interval', '600', '--comment', ' 1er
backup apr?s RAZ (plantage repo ? cause de compact)',
'--chunker-params', '16,23,16,4095', '--compression', 'auto,zlib,6',
'--exclude-from', '/usr/local/sbin/BORG_EXCLUSIONS.list',
'::{hostname}-{utcnow}Z', '/'] SSH_ORIGINAL_COMMAND: None

terminating with error status, rc 2


My former test was a bit more successful (with msgpack from debian
package), I saw files beginning to pile into data/0/nnnn but it failed
after a while with these messages :

[?]
A /home/niff/Images/0_TMP/.thumbnails/r_899509.jpg.png
A /home/niff/Images/0_TMP/.thumbnails/r_899510.jpg.png
Repository hints file missing or corrupted, trying to recover:
unpack(b) received extra data.
Local Exception
Traceback (most recent call last):
  File
"/usr/local/lib/python3.9/dist-packages/borg/helpers/msgpack.py", line 169, in unpack
    return mp_unpack(stream, **kw)
  File "/usr/lib/python3/dist-packages/msgpack/__init__.py", line 46,
in unpack
    return unpackb(data, **kwargs)
  File "msgpack/_unpacker.pyx", line 202, in msgpack._cmsgpack.unpackb
msgpack.exceptions.ExtraData: unpack(b) received extra data.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 576, in prepare_txn
    hints = msgpack.unpack(fd)
  File
"/usr/local/lib/python3.9/dist-packages/borg/helpers/msgpack.py", line 171, in unpack
    raise UnpackException(e)
borg.helpers.msgpack.UnpackException: unpack(b) received extra data.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/usr/local/lib/python3.9/dist-packages/borg/helpers/msgpack.py", line 169, in unpack
    return mp_unpack(stream, **kw)
  File "/usr/lib/python3/dist-packages/msgpack/__init__.py", line 46,
in unpack
    return unpackb(data, **kwargs)
  File "msgpack/_unpacker.pyx", line 202, in msgpack._cmsgpack.unpackb
msgpack.exceptions.ExtraData: unpack(b) received extra data.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
5159, in main
    exit_code = archiver.run(args)
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
5090, in run
    return set_ec(func(args))
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
183, in wrapper
    return method(self, args, repository=repository, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
675, in do_create
    create_inner(archive, cache, fso)
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
608, in create_inner
    self._rec_walk(path=path, parent_fd=parent_fd, name=name,
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
820, in _rec_walk
    self._rec_walk(
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
820, in _rec_walk
    self._rec_walk(
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
820, in _rec_walk
    self._rec_walk(
  [Previous line repeated 3 more times]
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
786, in _rec_walk
    status = self._process_any(path=path, parent_fd=parent_fd,
name=name, st=st, fso=fso, cache=cache,
  File "/usr/local/lib/python3.9/dist-packages/borg/archiver.py", line
688, in _process_any
    return fso.process_file(path=path, parent_fd=parent_fd, name=name,
st=st, cache=cache)
  File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1434, in process_file
    self.process_file_chunks(item, cache, self.stats,
self.show_progress, backup_io_iter(self.chunker.chunkify(None, fd)))
  File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1264, in process_file_chunks
    from_chunk, part_number = self.maybe_checkpoint(item, from_chunk,
part_number, forced=False)
  File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1238, in maybe_checkpoint
    from_chunk, part_number = self.write_part_file(item, from_chunk,
part_number)
  File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
1229, in write_part_file
    self.write_checkpoint()
  File "/usr/local/lib/python3.9/dist-packages/borg/archive.py", line
605, in write_checkpoint
    self.cache.chunk_decref(self.id, self.stats)
  File "/usr/local/lib/python3.9/dist-packages/borg/cache.py", line
978, in chunk_decref
    self.repository.delete(id, wait=wait)
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 1246, in delete
    self.prepare_txn(self.get_transaction_id())
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 584, in prepare_txn
    self.prepare_txn(transaction_id)
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 558, in prepare_txn
    self.index = self.open_index(transaction_id, auto_recover=False)
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 523, in open_index
    integrity_data = self._read_integrity(transaction_id, b'index')
  File "/usr/local/lib/python3.9/dist-packages/borg/repository.py",
line 511, in _read_integrity
    integrity = msgpack.unpack(fd)
  File
"/usr/local/lib/python3.9/dist-packages/borg/helpers/msgpack.py", line 171, in unpack
    raise UnpackException(e)
borg.helpers.msgpack.UnpackException: unpack(b) received extra data.

Platform: Linux msi 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1
(2022-08-13) x86_64
Linux: Unknown Linux  
Borg: 1.2.2  Python: CPython 3.9.2 msgpack: 1.0.0 fuse: pyfuse3 3.2.0
[pyfuse3,llfuse]
PID: 2808327  CWD: /root
sys.argv: ['/usr/local/bin/borg', 'create', '--verbose',
'--exclude-caches', '--show-rc', '--warning', '--filter', 'AME', '--list', '--stats', '--checkpoint-interval', '600', '--comment', ' 1er backup apr?s RAZ (plantage repo ? cause de compact)', '--chunker-params', '16,23,16,4095', '--compression', 'auto,zlib,6', '--exclude-from', '/usr/local/sbin/BORG_EXCLUSIONS.list', '::{hostname}-{utcnow}Z', '/']
SSH_ORIGINAL_COMMAND: None

terminating with error status, rc 2


This a real concern, as a compaction test seems to have had clobbered
all of my repos :( so I really need to be able to make fresh backups
ASAP.

What is going wrong ?

Jean-Yves

From tw at waldmann-edv.de  Mon Aug 29 14:10:25 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Mon, 29 Aug 2022 20:10:25 +0200
Subject: [Borgbackup] Fail to run
In-Reply-To: <20220829171710.2840be12@msi.defcon1.lan>
References: <20220829171710.2840be12@msi.defcon1.lan>
Message-ID: <4e3abedc-69c3-31a9-e45f-1ca88d739020@waldmann-edv.de>

> After a fresh pip3 install borgbackup (v.1.2.2),
> it fails on a brand
> new repo with these messages :
> get_free_nonce return int.from_bytes(unhexlify(fd.read()),
> byteorder='big') binascii.Error: Non-hexadecimal digit found

That means that there is crap in the .../repo_dir/nonce file.

If that is for a brand new repo, the stability / integrity of that 
system / filesystem / disk is questionable.

> ['/usr/local/bin/borg', 'create', '--verbose',
> '--exclude-caches', '--show-rc', '--warning',

--verbose is the same as --info (because the default is --warning).

you also give --warning, so that is a contradiction.

> '--chunker-params', '16,23,16,4095',

That creates relatively many small chunks.

> '--compression', 'auto,zlib,6',

zstd is more modern.

> Repository hints file missing or corrupted, trying to recover:

Usually that does not go missing nor gets corrupted. System stability?


> '--checkpoint-interval', '600'

Don't go too low with that or at some point you will have more 
startup/checkpointing overhead than time to actually back up files.

From lazyvirus at gmx.com  Mon Aug 29 14:42:35 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Mon, 29 Aug 2022 20:42:35 +0200
Subject: [Borgbackup] Fail to run
In-Reply-To: <4e3abedc-69c3-31a9-e45f-1ca88d739020@waldmann-edv.de>
References: <20220829171710.2840be12@msi.defcon1.lan>
 <4e3abedc-69c3-31a9-e45f-1ca88d739020@waldmann-edv.de>
Message-ID: <20220829204235.01e1b8cc@msi.defcon1.lan>

On Mon, 29 Aug 2022 20:10:25 +0200
Thomas Waldmann <tw at waldmann-edv.de> wrote:

> > After a fresh pip3 install borgbackup (v.1.2.2),
> > it fails on a brand
> > new repo with these messages :
> > get_free_nonce return int.from_bytes(unhexlify(fd.read()),
> > byteorder='big') binascii.Error: Non-hexadecimal digit found
>
> That means that there is crap in the .../repo_dir/nonce file.
>
> If that is for a brand new repo, the stability / integrity of that
> system / filesystem / disk is questionable.

There was indeed some errors now corrected.

It also seems there was a confusion between python3.x into
/usr/local/lib.

I finally solved it removing old pip3 installations and returned to BB
from the debian pkg (1.1.16), backups are running ok at this time.
Next stable branch, I think I'll install it from scratch for a clean
system.

> > ['/usr/local/bin/borg', 'create', '--verbose',
> > '--exclude-caches', '--show-rc', '--warning',
>
> --verbose is the same as --info (because the default is --warning).
>
> you also give --warning, so that is a contradiction.

Thanks, corrected to --info.

> > '--chunker-params', '16,23,16,4095',
>
> That creates relatively many small chunks.

I have several big VM images on this machine, this is to avoid very
large chunks that takes long to backup with the original values.

> > '--compression', 'auto,zlib,6',
>
> zstd is more modern.

This is because the script's almost the same on every machine,
including those with an i386 CPU (tests have shown using zstd was
speeding down backups on those).

> > Repository hints file missing or corrupted, trying to recover:
>
> Usually that does not go missing nor gets corrupted. System stability?

Wild guess: due to the same mix that had stuck backups.

> > '--checkpoint-interval', '600'
>
> Don't go too low with that or at some point you will have more
> startup/checkpointing overhead than time to actually back up files.

Yup, this came after several tests (mostly to avoid losing a whole
backup when I forget to update the system before).

Thanks for your comments Thomas.

Jean-Yves

From bkborg at kirk.de  Sat Sep 10 06:09:05 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sat, 10 Sep 2022 12:09:05 +0200
Subject: [Borgbackup] pip install failed
Message-ID: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>

Hello,
first to say: I have no idea about python programming, so I do not
understand these lines. I hope you can help me.

Since borgbackup version 1.2.2 is not available as rpm packet in the
SUSE repos, I tried the following to get it installed:

> boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2> pip install pkgconfig
> Defaulting to user installation because normal site-packages is not writeable
> Requirement already satisfied: pkgconfig in /usr/lib/python3.10/site-packages (1.5.5)
> boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2> pip install "borgbackup==1.2.2"
> Defaulting to user installation because normal site-packages is not writeable
> Collecting borgbackup==1.2.2
>   Downloading borgbackup-1.2.2.tar.gz (4.0 MB)
>      ???????????????????????????????????????? 4.0/4.0 MB 7.4 MB/s eta 0:00:00
>   Installing build dependencies ... done
>   Getting requirements to build wheel ... error
>   error: subprocess-exited-with-error
>   
>   ? Getting requirements to build wheel did not run successfully.
>   ? exit code: 1
>   ??> [17 lines of output]
>       Traceback (most recent call last):
>         File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
>           main()
>         File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
>           json_out['return_val'] = hook(**hook_input['kwargs'])
>         File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
>           return hook(config_settings)
>         File "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 338, in get_requires_for_build_wheel
>           return self._get_build_requires(config_settings, requirements=['wheel'])
>         File "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 320, in _get_build_requires
>           self.run_setup()
>         File "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 335, in run_setup
>           exec(code, locals())
>         File "<string>", line 193, in <module>
>         File "/tmp/pip-install-nh_uztd6/borgbackup_2787a2604f8445dcb570a5732efbd2be/setup_crypto.py", line 32, in crypto_ext_kwargs
>           raise Exception('Could not find OpenSSL lib/headers, please set BORG_OPENSSL_PREFIX')
>       Exception: Could not find OpenSSL lib/headers, please set BORG_OPENSSL_PREFIX
>       [end of output]
>   
>   note: This error originates from a subprocess, and is likely not a problem with pip.
> error: subprocess-exited-with-error
> 
> ? Getting requirements to build wheel did not run successfully.
> ? exit code: 1
> ??> See above for output.
> 
> note: This error originates from a subprocess, and is likely not a problem with pip.

How can I find out what is broken and how to fix it?


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From ndbecker2 at gmail.com  Sat Sep 10 07:40:07 2022
From: ndbecker2 at gmail.com (Neal Becker)
Date: Sat, 10 Sep 2022 07:40:07 -0400
Subject: [Borgbackup] pip install failed
In-Reply-To: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
Message-ID: <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>

Says cannot find openssl library headers.  Probably need to install
something like openssl-devel, depending on your software distro

On Sat, Sep 10, 2022, 6:25 AM Boris Kirkorowicz <bkborg at kirk.de> wrote:

> Hello,
> first to say: I have no idea about python programming, so I do not
> understand these lines. I hope you can help me.
>
> Since borgbackup version 1.2.2 is not available as rpm packet in the
> SUSE repos, I tried the following to get it installed:
>
> > boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2>
> pip install pkgconfig
> > Defaulting to user installation because normal site-packages is not
> writeable
> > Requirement already satisfied: pkgconfig in
> /usr/lib/python3.10/site-packages (1.5.5)
> > boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2>
> pip install "borgbackup==1.2.2"
> > Defaulting to user installation because normal site-packages is not
> writeable
> > Collecting borgbackup==1.2.2
> >   Downloading borgbackup-1.2.2.tar.gz (4.0 MB)
> >      ???????????????????????????????????????? 4.0/4.0 MB 7.4 MB/s eta
> 0:00:00
> >   Installing build dependencies ... done
> >   Getting requirements to build wheel ... error
> >   error: subprocess-exited-with-error
> >
> >   ? Getting requirements to build wheel did not run successfully.
> >   ? exit code: 1
> >   ??> [17 lines of output]
> >       Traceback (most recent call last):
> >         File
> "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
> line 363, in <module>
> >           main()
> >         File
> "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
> line 345, in main
> >           json_out['return_val'] = hook(**hook_input['kwargs'])
> >         File
> "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
> line 130, in get_requires_for_build_wheel
> >           return hook(config_settings)
> >         File
> "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
> line 338, in get_requires_for_build_wheel
> >           return self._get_build_requires(config_settings,
> requirements=['wheel'])
> >         File
> "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
> line 320, in _get_build_requires
> >           self.run_setup()
> >         File
> "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
> line 335, in run_setup
> >           exec(code, locals())
> >         File "<string>", line 193, in <module>
> >         File
> "/tmp/pip-install-nh_uztd6/borgbackup_2787a2604f8445dcb570a5732efbd2be/setup_crypto.py",
> line 32, in crypto_ext_kwargs
> >           raise Exception('Could not find OpenSSL lib/headers, please
> set BORG_OPENSSL_PREFIX')
> >       Exception: Could not find OpenSSL lib/headers, please set
> BORG_OPENSSL_PREFIX
> >       [end of output]
> >
> >   note: This error originates from a subprocess, and is likely not a
> problem with pip.
> > error: subprocess-exited-with-error
> >
> > ? Getting requirements to build wheel did not run successfully.
> > ? exit code: 1
> > ??> See above for output.
> >
> > note: This error originates from a subprocess, and is likely not a
> problem with pip.
>
> How can I find out what is broken and how to fix it?
>
>
> --
> Mit freundlichem Gru?                                 Best regards
>                                  Kirkorowicz
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220910/e0f2b33e/attachment.html>

From bkborg at kirk.de  Sat Sep 10 17:31:05 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sat, 10 Sep 2022 23:31:05 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
Message-ID: <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>

Hello,
unfortunately this did not work, the messages remain the same. Step by
step, I updated everything installed with "openssl" in it's name oder
description, that would not conflict. So maybe $BORG_OPENSSL_PREFIX
might help. Do you know what content it should have (for now, it is empty)?

My distro is openSUSE tumbleweed.


Am 10.09.22 um 13:40 schrieb Neal Becker:
> Says cannot find openssl library headers.? Probably need to install
> something like openssl-devel, depending on your software distro
> 
> On Sat, Sep 10, 2022, 6:25 AM Boris Kirkorowicz <bkborg at kirk.de
> <mailto:bkborg at kirk.de>> wrote:
> 
>     Hello,
>     first to say: I have no idea about python programming, so I do not
>     understand these lines. I hope you can help me.
> 
>     Since borgbackup version 1.2.2 is not available as rpm packet in the
>     SUSE repos, I tried the following to get it installed:
> 
>     >
>     boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2>
>     pip install pkgconfig
>     > Defaulting to user installation because normal site-packages is
>     not writeable
>     > Requirement already satisfied: pkgconfig in
>     /usr/lib/python3.10/site-packages (1.5.5)
>     >
>     boris at linux-t560b:/home/groups/download/linux/install/borgbackup-1.2.2>
>     pip install "borgbackup==1.2.2"
>     > Defaulting to user installation because normal site-packages is
>     not writeable
>     > Collecting borgbackup==1.2.2
>     >? ?Downloading borgbackup-1.2.2.tar.gz (4.0 MB)
>     >? ? ? ???????????????????????????????????????? 4.0/4.0 MB 7.4 MB/s
>     eta 0:00:00
>     >? ?Installing build dependencies ... done
>     >? ?Getting requirements to build wheel ... error
>     >? ?error: subprocess-exited-with-error
>     >? ?
>     >? ?? Getting requirements to build wheel did not run successfully.
>     >? ?? exit code: 1
>     >? ???> [17 lines of output]
>     >? ? ? ?Traceback (most recent call last):
>     >? ? ? ? ?File
>     "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
>     line 363, in <module>
>     >? ? ? ? ? ?main()
>     >? ? ? ? ?File
>     "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
>     line 345, in main
>     >? ? ? ? ? ?json_out['return_val'] = hook(**hook_input['kwargs'])
>     >? ? ? ? ?File
>     "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
>     line 130, in get_requires_for_build_wheel
>     >? ? ? ? ? ?return hook(config_settings)
>     >? ? ? ? ?File
>     "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
>     line 338, in get_requires_for_build_wheel
>     >? ? ? ? ? ?return self._get_build_requires(config_settings,
>     requirements=['wheel'])
>     >? ? ? ? ?File
>     "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
>     line 320, in _get_build_requires
>     >? ? ? ? ? ?self.run_setup()
>     >? ? ? ? ?File
>     "/tmp/pip-build-env-e44g5q7r/overlay/lib/python3.10/site-packages/setuptools/build_meta.py",
>     line 335, in run_setup
>     >? ? ? ? ? ?exec(code, locals())
>     >? ? ? ? ?File "<string>", line 193, in <module>
>     >? ? ? ? ?File
>     "/tmp/pip-install-nh_uztd6/borgbackup_2787a2604f8445dcb570a5732efbd2be/setup_crypto.py",
>     line 32, in crypto_ext_kwargs
>     >? ? ? ? ? ?raise Exception('Could not find OpenSSL lib/headers,
>     please set BORG_OPENSSL_PREFIX')
>     >? ? ? ?Exception: Could not find OpenSSL lib/headers, please set
>     BORG_OPENSSL_PREFIX
>     >? ? ? ?[end of output]
>     >? ?
>     >? ?note: This error originates from a subprocess, and is likely not
>     a problem with pip.
>     > error: subprocess-exited-with-error
>     >
>     > ? Getting requirements to build wheel did not run successfully.
>     > ? exit code: 1
>     > ??> See above for output.
>     >
>     > note: This error originates from a subprocess, and is likely not a
>     problem with pip.
> 
>     How can I find out what is broken and how to fix it?
> 
> 
>     -- 
>     Mit freundlichem Gru?? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Best regards
>     ? ? ? ? ? ? ? ? ? ? ? ? ? ??? ? ?Kirkorowicz
>     _______________________________________________
>     Borgbackup mailing list
>     Borgbackup at python.org <mailto:Borgbackup at python.org>
>     https://mail.python.org/mailman/listinfo/borgbackup
>     <https://mail.python.org/mailman/listinfo/borgbackup>
> 

-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tw at waldmann-edv.de  Sat Sep 10 17:49:20 2022
From: tw at waldmann-edv.de (Thomas Waldmann)
Date: Sat, 10 Sep 2022 23:49:20 +0200
Subject: [Borgbackup] borgbackup 2.0.0b2 released!
Message-ID: <b5664c26-7bb4-216b-0cf8-e3686ed12df6@waldmann-edv.de>

Just released borgbackup 2.0.0 beta2 - please give this a good amount of 
testing:

https://github.com/borgbackup/borg/releases/tag/2.0.0b2


From tschoening at am-soft.de  Sun Sep 11 05:42:07 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 11 Sep 2022 11:42:07 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
Message-ID: <38718015.20220911114207@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Samstag, 10. September 2022 um 23:31 schrieben Sie:

> [...]I updated everything installed with "openssl" in it's name oder
> description[...]

Please provide the exact commands you issued regarding OpenSSL. Might
be nit-picking, but updating EXISTING won't solve errors about MISSING
packages, you need to install them first. Missing packages are your
problem. Makes sense ot provide a list of the currently installed
packages regarding OpenSSL as well.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From tschoening at am-soft.de  Sun Sep 11 11:32:43 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 11 Sep 2022 17:32:43 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
Message-ID: <1025115835.20220911173243@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Sonntag, 11. September 2022 um 14:12 schrieben Sie:

> ca-certificates-mozilla
> libopenssl10
> libopenssl1_0_0
> libopenssl1_1
> libopenssl1_1-32bit
> libopenssl3
> openssl
> openssl-1_1
> openssl-3
> openssl-3-doc
> php8-openssl
> python310-ctypescrypto
> python310-ndg-httpsclient
> python310-pyOpenSSL
> python310-service_identity
> python38-ndg-httpsclient
> python38-pyOpenSSL
> python38-service_identity

As said, something like a developer package is necessary most likely.
Something like this:

https://pkgs.org/download/libopenssl-devel

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From bkborg at kirk.de  Sun Sep 11 13:27:10 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 11 Sep 2022 19:27:10 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <1025115835.20220911173243@am-soft.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
Message-ID: <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>

Hi,
thank you for your patience.

Am 11.09.22 um 17:32 schrieb Thorsten Sch?ning:
> As said, something like a developer package is necessary most likely.
> Something like this:
> 
> https://pkgs.org/download/libopenssl-devel

I did so, and i had to install python310-devel as well. Now, the
installation still fails, with >500 lines output. The last few lines are


>       gcc -shared build/temp.linux-x86_64-cpython-310/src/borg/platform/posix.o -L/usr/lib64 -o build/lib.linux-x86_64-cpython-310/borg/platform/posix.cpython-310-x86_64-linux-gnu.so
>       building 'borg.platform.linux' extension
>       gcc -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv -fno-semantic-interposition -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -IVendor/ -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -IVendor/ -fPIC -I/usr/include/python3.10 -c src/borg/platform/linux.c -o build/temp.linux-x86_64-cpython-310/src/borg/platform/linux.o -Wall -Wextra -Wpointer-arith
>       In Datei, eingebunden von /usr/include/bits/libc-header-start.h:33,
>                        von /usr/include/limits.h:26,
>                        von /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:203,
>                        von /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/syslimits.h:7,
>                        von /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:34,
>                        von /usr/include/python3.10/Python.h:11,
>                        von src/borg/platform/linux.c:27:
>       /usr/include/features.h:424:5: Warnung: #warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform [-Wcpp]
>         424 | #   warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform
>             |     ^~~~~~~
>       src/borg/platform/linux.c:769:10: schwerwiegender Fehler: sys/acl.h: Datei oder Verzeichnis nicht gefunden
>         769 | #include "sys/acl.h"
>             |          ^~~~~~~~~~~
>       Kompilierung beendet.
>       error: command '/usr/bin/gcc' failed with exit code 1
>       [end of output]
>   
>   note: This error originates from a subprocess, and is likely not a problem with pip.
>   ERROR: Failed building wheel for borgbackup
> Failed to build borgbackup
> ERROR: Could not build wheels for borgbackup, which is required to install pyproject.toml-based projects

after installing gcc11-devel (including several depending pkgs), I got
180 lines output, ending like this:

>       /usr/include/features.h:424:5: Warnung: #warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform [-Wcpp]
>         424 | #   warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform
>             |     ^~~~~~~
>       gcc -shared build/temp.linux-x86_64-cpython-310/src/borg/crypto/_crypto_helpers.o build/temp.linux-x86_64-cpython-310/src/borg/crypto/low_level.o -L/usr/lib64 -lcrypto -o build/lib.linux-x86_64-cpython-310/borg/crypto/low_level.cpython-310-x86_64-linux-gnu.so
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/libc.so.6 when searching for /lib64/libc.so.6
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: cannot find /lib64/libc.so.6
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/libc.so.6 when searching for /lib64/libc.so.6
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching for /lib64/ld-linux-x86-64.so.2
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: cannot find /lib64/ld-linux-x86-64.so.2
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching for /lib64/ld-linux-x86-64.so.2
>       collect2: Fehler: ld gab 1 als Ende-Status zur?ck
>       error: command '/usr/bin/gcc' failed with exit code 1
>       [end of output]
>   
>   note: This error originates from a subprocess, and is likely not a problem with pip.
>   ERROR: Failed building wheel for borgbackup
> Failed to build borgbackup
> ERROR: Could not build wheels for borgbackup, which is required to install pyproject.toml-based projects


As a non-developer, this is too much for me, I do not understand what's
going on.



-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From tschoening at am-soft.de  Sun Sep 11 13:27:37 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 11 Sep 2022 19:27:37 +0200
Subject: [Borgbackup] Is it possible to replace SOCAT with BorgMatic?
Message-ID: <321047762.20220911192737@am-soft.de>

Hi everyone,

I'm using PULL mode backups with SSHFS currently. There are many
remote hosts top be backed up, one backup server running BorgMatic
contain all the configs, coordinating times etc. and being the only
one with access to additionally remote sotrage for the repos themself
using SSH. Am thinking about replacing SSHFS with something like the
SOCAT example from the official docs.

https://borgbackup.readthedocs.io/en/stable/deployment/pull-backup.html#socat
https://projects.torsion.org/borgmatic-collective/borgmatic/issues/584

Though, I don't like the SOCAT in that setup, because I have BorgMatic
already and have the impression that from a conceptual point of view,
it might be able replace SOCAT, acting as some write-through-proxy. To
better understand things, some questions came up for me:

1. How do Borg client and server instances communicate?

Looking at the SOCAT example and the docs of "borg serve" I have the
feeling that STDOUT of Borg client instances is forwarded to STDIN of
borg serve? Or do Borg client instances start borg serve and write
directly into STDIN of those started instances then, leaving their own
STDOUT for other purposes?

As logging is done on STDERR, it makes sense to me that STDOUT and
STDIN are free for client and server to use for their communication.

2. Who starts borg serve at all?

Looking at the logs of my existing setup, I see many commands
containing the "remote-path" argument. So Borg client instances are
running "borg serve" on their own, taking BORG_RSH etc. into account,
correct? The important point in my setup would be avoiding them doing
so, like in the SOCAT-example with a custom BORG_RSH, and instead make
BorgMatic taking care of that.

3. How does `borg serve` know about its end?

At some point the Borg client has finished. How does `borg serve`
recognized that? If BorgMatic maintains that procvess, it needs to be
able to properly stop it as well. Easiest would be if the Borg client
simply tells the process to shutdown on it's own.

Thanks!

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From lazyvirus at gmx.com  Sun Sep 11 13:34:09 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 11 Sep 2022 19:34:09 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
Message-ID: <20220911193409.53e94cc7@msi.defcon1.lan>

On Sun, 11 Sep 2022 19:27:10 +0200
Boris Kirkorowicz <bkborg at kirk.de> wrote:

> Hi,
> thank you for your patience.

Which isn't rewarded, as you have visibly did not read the doc,
especially about the installation *requirements*.

When using a package, you only need the required libs, however when
building it, you need the development libs (which also install the
regular libs that'll be used by the program in exploitation in a
normal system).

Sooo, RTFM!

Jean-Yves


> Am 11.09.22 um 17:32 schrieb Thorsten Sch?ning:
> > As said, something like a developer package is necessary most
> > likely. Something like this:
> > 
> > https://pkgs.org/download/libopenssl-devel
> 
> I did so, and i had to install python310-devel as well. Now, the
> installation still fails, with >500 lines output. The last few lines
> are
> 
> 
> >       gcc -shared
> > build/temp.linux-x86_64-cpython-310/src/borg/platform/posix.o
> > -L/usr/lib64 -o
> > build/lib.linux-x86_64-cpython-310/borg/platform/posix.cpython-310-x86_64-linux-gnu.so
> > building 'borg.platform.linux' extension gcc -Wno-unused-result
> > -Wsign-compare -DNDEBUG -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv
> > -fno-semantic-interposition -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -IVendor/ -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -IVendor/ -fPIC -I/usr/include/python3.10 -c
> > src/borg/platform/linux.c -o
> > build/temp.linux-x86_64-cpython-310/src/borg/platform/linux.o -Wall
> > -Wextra -Wpointer-arith In Datei, eingebunden von
> > /usr/include/bits/libc-header-start.h:33, von
> > /usr/include/limits.h:26, von
> > /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:203, von
> > /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/syslimits.h:7,
> > von /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:34,
> > von /usr/include/python3.10/Python.h:11, von
> > src/borg/platform/linux.c:27: /usr/include/features.h:424:5:
> > Warnung: #warning _FORTIFY_SOURCE > 2 is treated like 2 on this
> > platform [-Wcpp] 424 | #   warning _FORTIFY_SOURCE > 2 is treated
> > like 2 on this platform |     ^~~~~~~
> > src/borg/platform/linux.c:769:10: schwerwiegender Fehler:
> > sys/acl.h: Datei oder Verzeichnis nicht gefunden 769 | #include
> > "sys/acl.h" |          ^~~~~~~~~~~ Kompilierung beendet. error:
> > command '/usr/bin/gcc' failed with exit code 1 [end of output]
> > note: This error originates from a subprocess, and is likely not a
> > problem with pip. ERROR: Failed building wheel for borgbackup
> > Failed to build borgbackup ERROR: Could not build wheels for
> > borgbackup, which is required to install pyproject.toml-based
> > projects
> 
> after installing gcc11-devel (including several depending pkgs), I got
> 180 lines output, ending like this:
> 
> >       /usr/include/features.h:424:5: Warnung: #warning
> > _FORTIFY_SOURCE > 2 is treated like 2 on this platform [-Wcpp] 424
> > | #   warning _FORTIFY_SOURCE > 2 is treated like 2 on this
> > platform |     ^~~~~~~ gcc -shared
> > build/temp.linux-x86_64-cpython-310/src/borg/crypto/_crypto_helpers.o
> > build/temp.linux-x86_64-cpython-310/src/borg/crypto/low_level.o
> > -L/usr/lib64 -lcrypto -o
> > build/lib.linux-x86_64-cpython-310/borg/crypto/low_level.cpython-310-x86_64-linux-gnu.so
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/libc.so.6 when searching for
> > /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > cannot find /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/libc.so.6 when searching for
> > /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section
> > `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching
> > for /lib64/ld-linux-x86-64.so.2
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > cannot find /lib64/ld-linux-x86-64.so.2
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section
> > `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching
> > for /lib64/ld-linux-x86-64.so.2 collect2: Fehler: ld gab 1 als
> > Ende-Status zur?ck error: command '/usr/bin/gcc' failed with exit
> > code 1 [end of output] note: This error originates from a
> > subprocess, and is likely not a problem with pip. ERROR: Failed
> > building wheel for borgbackup Failed to build borgbackup ERROR:
> > Could not build wheels for borgbackup, which is required to install
> > pyproject.toml-based projects
> 
> 
> As a non-developer, this is too much for me, I do not understand
> what's going on.
> 
> 
> 


From tschoening at am-soft.de  Sun Sep 11 14:10:40 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Sun, 11 Sep 2022 20:10:40 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
Message-ID: <541846672.20220911201040@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Sonntag, 11. September 2022 um 19:27 schrieben Sie:

>>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
>>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching for /lib64/ld-linux-x86-64.so.2
>>       collect2: Fehler: ld gab 1 als Ende-Status zur?ck

You need to update ld or binutils if possible. Your version simply
doesn't support how some system libraries seem to look like. No idea
how those have been built, but maybe using lld instead of ld?

Your issue is known for different projects and things heavily depend
on how things are suppsed to work in the first place for your distro.
Have no idea...

https://github.com/chromebrew/chromebrew/issues/2563#issuecomment-418110227
https://github.com/chromebrew/chromebrew/issues/2563#issuecomment-478332209

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From borgbackup at aluaces.fastmail.com  Sun Sep 11 15:19:25 2022
From: borgbackup at aluaces.fastmail.com (Alberto Luaces)
Date: Sun, 11 Sep 2022 21:19:25 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <541846672.20220911201040@am-soft.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
 <541846672.20220911201040@am-soft.de>
Message-ID: <87bkrllnr0.fsf@pantallon>


Thorsten Sch?ning <tschoening at am-soft.de> writes:

> Guten Tag Boris Kirkorowicz,
> am Sonntag, 11. September 2022 um 19:27 schrieben Sie:
>
>>>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
>>>       /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching for /lib64/ld-linux-x86-64.so.2
>>>       collect2: Fehler: ld gab 1 als Ende-Status zur?ck
>
> You need to update ld or binutils if possible. Your version simply
> doesn't support how some system libraries seem to look like. No idea
> how those have been built, but maybe using lld instead of ld?
>
> Your issue is known for different projects and things heavily depend
> on how things are suppsed to work in the first place for your distro.
> Have no idea...
>
> https://github.com/chromebrew/chromebrew/issues/2563#issuecomment-418110227
> https://github.com/chromebrew/chromebrew/issues/2563#issuecomment-478332209

What about installing wheels?  pip has an option for downloading
already-compiled binary packages, so those local building problems could
be avoided.

You just install the "wheel" package first, and then try to install borg
again:

pip install wheel
pip install borgbackup

Reference: https://roman.pt/posts/optimize-pip-install-with-wheels/

From bkborg at kirk.de  Sun Sep 11 16:19:06 2022
From: bkborg at kirk.de (Boris Kirkorowicz)
Date: Sun, 11 Sep 2022 22:19:06 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <20220911193409.53e94cc7@msi.defcon1.lan>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
 <20220911193409.53e94cc7@msi.defcon1.lan>
Message-ID: <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>

Hello,

Am 11.09.22 um 19:34 schrieb Bzzzz:
> Sooo, RTFM!

I feel unblamable, since I only looked for installation, and the
instruction I found was
? download
? pip install pkgconfig
? pip install "borgbackup==1.2.2"

That's all. I did not guess that this meant a complete build process. If
I would, I never had tried.

So please excuse, I'll give up.


-- 
Mit freundlichem Gru?                                 Best regards
                           ?     Kirkorowicz

From lazyvirus at gmx.com  Sun Sep 11 16:42:40 2022
From: lazyvirus at gmx.com (Bzzzz)
Date: Sun, 11 Sep 2022 22:42:40 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
 <20220911193409.53e94cc7@msi.defcon1.lan>
 <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>
Message-ID: <20220911224240.3f05bbe6@msi.defcon1.lan>

On Sun, 11 Sep 2022 22:19:06 +0200
Boris Kirkorowicz <bkborg at kirk.de> wrote:

> Hello,
> 
> Am 11.09.22 um 19:34 schrieb Bzzzz:
> > Sooo, RTFM!
> 
> I feel unblamable, since I only looked for installation, and the
> instruction I found was
> ? download
> ? pip install pkgconfig
> ? pip install "borgbackup==1.2.2"

Unblamable, but you obviously do not know how pip is working?
There are numerous excellent articles about borgbackup, python3, pip,
etc on the net.

> That's all. I did not guess that this meant a complete build process.
> If I would, I never had tried.

There's nothing to be afraid of, just to read the borgbackup doc and
some others too.

Linux is not windows, if you don't involve yourself into it, you'll
mostly fail at one moment or another, the later the worse ; it's
philosophy is to first document yourself, now would be a good moment to
do so?

> So please excuse, I'll give up.

There's something weird as almost each and every distro have
borgbackup available as a package.

Jean-Yves

From jdc at uwo.ca  Sun Sep 11 19:16:38 2022
From: jdc at uwo.ca (Dan Christensen)
Date: Sun, 11 Sep 2022 23:16:38 +0000
Subject: [Borgbackup] pip install failed
In-Reply-To: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de> (Boris
 Kirkorowicz's message of "Sat, 10 Sep 2022 12:09:05 +0200")
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
Message-ID: <87pmg1zeln.fsf@uwo.ca>

On Sep 10, 2022, Boris Kirkorowicz <bkborg at kirk.de> wrote:

> Since borgbackup version 1.2.2 is not available as rpm packet in the
> SUSE repos, I tried the following to get it installed:

Did you consider using the pre-built fat binaries?  They are available
at

  https://github.com/borgbackup/borg/releases

I'm not 100% sure what will work best on SUSE, but you could try the one
called borg-linux64.  You just download it and run it, no installation
required.

Dan

From tschoening at am-soft.de  Mon Sep 12 04:09:46 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Mon, 12 Sep 2022 10:09:46 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <20220911224240.3f05bbe6@msi.defcon1.lan>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
 <20220911193409.53e94cc7@msi.defcon1.lan>
 <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>
 <20220911224240.3f05bbe6@msi.defcon1.lan>
Message-ID: <1485469168.20220912100946@am-soft.de>

Guten Tag Bzzzz,
am Sonntag, 11. September 2022 um 22:42 schrieben Sie:

> Linux is not windows[...]

Ever heard of phrases like toxic Linux community? If you have actual
solutions to problems, please provide them. Otherwise one "RTFM" is
more than enough.

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From tschoening at am-soft.de  Mon Sep 12 04:09:54 2022
From: tschoening at am-soft.de (=?utf-8?Q?Thorsten_Sch=C3=B6ning?=)
Date: Mon, 12 Sep 2022 10:09:54 +0200
Subject: [Borgbackup] pip install failed
In-Reply-To: <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>
References: <e0fd86c8-5f72-7d14-e8a1-0c070a2b2453@kirk.de>
 <CAG3t+pG5tVm1604sksF1AXycUZdRPUL92h8zfdN5paNmootmRw@mail.gmail.com>
 <4c1a70b8-22e8-c79a-9432-48f304852b4c@kirk.de>
 <38718015.20220911114207@am-soft.de>
 <a1e70730-c646-6730-8ce2-410a4f5286d5@kirk.de>
 <1025115835.20220911173243@am-soft.de>
 <cba099ac-25f7-d7a7-8a1e-0df4adf87c6e@kirk.de>
 <20220911193409.53e94cc7@msi.defcon1.lan>
 <d71e8a19-b5f3-473a-7005-2e4a9fdead06@kirk.de>
Message-ID: <1678150039.20220912100954@am-soft.de>

Guten Tag Boris Kirkorowicz,
am Sonntag, 11. September 2022 um 22:19 schrieben Sie:

> So please excuse, I'll give up.

Don't, focus on avialable binaries or older versions available for
your distro. Why do you need exactly 1.2.2 at all?

> pip install wheel
> pip install borgbackup

> Reference: https://roman.pt/posts/optimize-pip-install-with-wheels/

https://github.com/borgbackup/borg/releases
https://software.opensuse.org/package/borgbackup

Mit freundlichen Gr??en

Thorsten Sch?ning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister f?r IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   +49 5151-  9468- 0
Tel:   +49 5151-  9468-55
Mobil: +49  178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Gesch?ftsf?hrer: Janine Galonska


F?r R?ckfragen stehe ich Ihnen jederzeit zur Verf?gung. 

Mit freundlichen Gr??en, 

Thorsten Sch?ning


Telefon: +49 5151 9468-55
Fax: 
E-Mail: TSchoening at am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Stra?e 7c
31789 Hameln

Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen und ist ausschliesslich f?r den Adressaten bestimmt. Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Sollten Sie nicht der f?r diese E-Mail bestimmte Adressat sein, ist Ihnen jede Ver?ffentlichung, Vervielf?ltigung oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz




From dave at gasaway.org  Thu Sep 15 19:58:54 2022
From: dave at gasaway.org (David Gasaway)
Date: Thu, 15 Sep 2022 16:58:54 -0700
Subject: [Borgbackup] Pattern relative paths with multiple recursion roots
Message-ID: <CAGsJ5AW54QgCuY+wMWAxnHdTiB+iUyvQj=q4Ux+dTzJF0ZhB3g@mail.gmail.com>

Hi,

As someone who is preparing to upgrade from 1.1 to 1.2, I'm reviewing my
patterns and docs to make sure everything works with the new relative
behavior.  I'm looking for some clarification from the pattern matching
docs, i.e.,
https://borgbackup.readthedocs.io/en/stable/usage/help.html#borg-help-patterns.
It leads with

The path/filenames used as input for the pattern matching start from the
> currently active recursion root.
>

As someone who uses --patterns-from and multiple recursion roots in the
file (currently 1.1, preparing to upgrade to 1.2), the meaning of
"currently active recursion root" isn't clear.  At first, I thought it
meant that I might have to move the recursion roots around so that the
patterns are immediately after the recursion root to which they would
match.  As in, borg keeps track of the last recursion root when parsing the
file.  However, the example further down suggests otherwise.

borg create --patterns-from patternfile.lst repo::arch
> # note that excludes use fm: by default and patternfiles use sh: by
> default.
> # therefore, we need to specify fm: to have the same exact behavior.
> P fm
> R /home/bobby
> R /home/susan
>
> - home/bobby/junk
>

This example makes it clear that an exclusion pattern is not relative to
either recursion root.  The docs do explain this, I think.

If you give /absolute/ as root, the paths going into the matcher will look
> relative like absolute/?/file.ext, because file paths in Borg archives are
> always stored normalized and relative.
>

I find the "relative" description a little confusing, but the end result
seems clear, anyway.  It does seem like one could end up with naming
conflicts by trying to mix absolute and relative roots (or multiple
relative roots?), but I have no intention of doing that.  I think I've
cleared my mind on that point, but I'd like to know if I misunderstood
something here.

The above example also shows, though the pattern applies to the contents of
the first root, it is after the second root.  That leaves me wondering
about "currently active recursion root".  I'm going to take a guess that it
means the code has a top-level loop through the recursion roots and
"current" is wherever it is in the loop at the time it's checking a
particular path-to-pattern combination.  Have I got that (close to) right?

Thanks.

-- 
-:-:- David K. Gasaway
-:-:- Email: dave at gasaway.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220915/fc929a30/attachment.html>