[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"



Hello Christian,

if you want to improve my understanding of Debian's build environment and learn more about it you should start to build yourself a package locally in a Debian's build environment.

I went this way myself some years ago. We here at the list we can help you to do it yourself.

I tried to document my way I do it. This documentation is public. It is like a reference where you can look into it to find answer for your questions. Otherwise ask here at the list and subscribe at debian-mentors@lists.debian.org.

The reference is work in progress you can find the last version at

https://salsa.debian.org/ddp-team/dpb (Sources)
https://ddp-team.pages.debian.net/dpb/en_US/BuildWithGBP.pdf
this is an automatic translation to English. The primary work is in German.

Yes we can discus the problem in a separate thread.

Regards


Am 28.07.23 um 09:13 schrieb c.buhtz@posteo.jp:
Dear Mechtilde,

thanks for taking time to reply.

Am 28.07.2023 07:31 schrieb Mechtilde:
Did you try to build the last released version?
What are your problems to build backintime?

At upstream I have no problems to build and test it because I'm upstream. ;)

But in my understanding the problem described in the bug ticket is about building the package in Debian's build environment (servers?) where I have no idea about. Some of the checking tools (lintian?) might have a problem because my unit tests do write to home filesystem which is not allowed or possible in Debian's build environment. That is how I understand the ticket.

At https://tracker.debian.org/pkg/backintime I can't find the right log or info describing the problem in detail. I'm not familiar with the system. That is why I ask questions like this because it is an opportunity to improve my understanding of Debian's build environment and learn more about all the fancy build-info (DD, UD, lintian, xyz, ...) links available.

May I open a separate thread about the problem described in the ticket?

Kind
Christian


--
Mechtilde Stehmann

## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: