Re: debci development - Setting up a development environment
Hi,
Thank you for the answers.
I will use a docker container, would it be a problem for me to use the unstable version?
I visited the autopkgtest page, but I didn't see any issues. Is that right or am I looking in the wrong place?
Tiago.
> On 14 Jan 2024, at 12:36, Paul Gevers <elbrus@debian.org> wrote:
>
> Hi Tiago,
>
> On 14-01-2024 02:22, Tiago Zaniquelli wrote:
>
>> I’m Tiago and I’m following this document
> > https://ci.debian.net/doc/file.HACKING.html#grab-the-dependencies-and-required-software
>> my target is start to contribute with the project.
> Nice, welcome.
>
>> In the first step apt-get build-dep . The terminal return a problem,
>> the autopkgtest is 5.28 and is necessary 5.29.
>
> The page you reference above has this:
> """
> If that fails with a complaint that any package it not recent enough, then you probably need to enable the backports repository and install those packages from there (replace <stable> with the current Debian stable release codename, and <PACKAGE> with the package you want to install):
> """
> I note that backports has 5.29~bpo12+1, which is indeed < 5.29, but that's a bug from our side; the build depends should have "<= 5.29~~" or something to ensure that that backports version is good enough. On top of that, we really should update bpo, as testing already has 5.32.
>
>> So, I would like to know what is the better version of Debian to help
>> the project? Stable? Unstable? In this moment I use the stable but no
>> problem that if I need change to stable.
>
> Stable should just work, our workers run stable too with some ci related packages from unstable (autopkgtest, autodep8, debci-*). Personally I have a system running testing.
>
>> I would like to take advantage, what tools do you use to develop, is
>> VIM? With any specific plugin?
>
> I think terceiro uses vim, I use emacs. And I have never searched for plugins but they probably make your life a lot nicer. I recently started to use spyder for python related work again, but I still need to figure out how to have that work for me.
>
>> Another question, how do you debug?
>
> I'm not very good at doing that in Python. breakpoint() and print() are my friends, but (particularly with spyder) you should be able to do that a lot better. Ruby based code I typically leave to terceiro, who I've seen smarter things than I write here.
>
>> Last question, I saw that there are some open issues, would you
>> suggest something to start with? I've been developing for a while,
>> but with Ruby it will be the first time, I've been studying, but only
>> theoretical knowledge for now and I want to put it into practice in
>> this project.
>
> For debci related issues (that's mostly Ruby), we have the newcomer tag:
> https://salsa.debian.org/groups/ci-team/-/issues/?sort=created_date&state=opened&label_name%5B%5D=newcomer&first_page_size=100
>
> If you're more into Python, autopkgtest might be more of interest, but the issues there are harder and we don't have a good overview of newcomer bugs.
>
> Paul
Reply to: