version control and project management

[Jonathan Dowland]

as software is continuously being developed,
it seems logical that there are packages to use in debian for this
purpose; ie project management (eg tickets, wiki, ..) and version
control (eg git). Ideally, these packages should be dist-upgradable, as
Debian is known for it's stability (eg Debian 11 > Debian 12)

Do you wish for one package to do all of these jobs, or would separate
packages, each addressing a particular facet, be acceptable?

* Gitea or Forgejo: incomplete? 

Gitea has never made it to a Debian stable release. Like most of these
large-ish web applications, with a lot of moving parts and dependencies,
they're ill-suited to Debian's packaging and release model.

* others?

For bugs alone, Debian's own bug system debbugs is packaged.

[Andy Smith]

Hi,

there are packages to use in debian for this purpose; ie project
management (eg tickets, wiki, ..) and version control (eg git).
Ideally, these packages should be dist-upgradable, as Debian is
known for it's stability (eg Debian 11 > Debian 12)
but it seems this is not so straightforward? (unless i miss

You haven;t missed anything, but it is not related to these being
project management solutions ("forges"). It's related to them being
large and complicated web applications with many dependencies.

You see the same sort of thing with e.g. Mailman 3.

They are just hard to package, any such packaging necessarily
diverges from upstream, upgrades become complicated and so on.

For software like this which either isn't packaged in Debian or the
packaging is limited, I tend to make use of virtual machines or
containers and just go with upstream's install instructions. It's
not great but it is often the easiest way.

Thanks,
Andy

[Juri Grabowski]

Hello Wim,

I mean bugs schould be tracked together with software, also in git.
checkmk.com are using own implementation: work
some projects was using
https://gitlab.com/bugseverywhere/bugseverywhere
Some projects prefere just to sync bugs with
https://github.com/git-bug/git-bug

In my opinion, mailing lists are good solution for discussion and
implementing resulting solution.

If you have other suggestions, let me know. Just looking for a stable,
trustworthy solution with at least git, issues/tickets, wiki and user
management.

Packaged solution can be:
gitolite3 + org-mode


Best Regards,
Juri Grabowski

[Jonathan Dowland]

ps: i had been using redmine (debian, postgres) for more than 10 years
with dist-upgrades, which did the job well (with some quirks for git
and automatic repo creation to setup), so i was surprised to see it
disappear
(i had to install a few gems that where not packaged though)

It looks like it's just under-maintained. It's maintained by the Debian
Ruby Team, and perhaps needs more volunteers to work on it.

Although it did drop out of the Bookworm release, it looks like it was
subsequently added to the Bookworm 'backports' repository, so is
available that way.

Given the maintenance situation though, I'd not bet on it being in the
next stable release (it's currently not in the testing distribution).

[Michel Verdier]

If you have other suggestions, let me know. Just looking for a stable,
trustworthy solution with at least git, issues/tickets, wiki and user
management.

I heavily used MantisBT but it's only the bug tracking part
https://mantisbt.org/index.php

Do you try https://packages.debian.org/bookworm/fossil

[Michel Verdier]

https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki
https://fossil-scm.org/home/doc/trunk/www/whyusefossil.wiki
it is not clear to me why i should fossil instead of git?

fossil comes with all tools integrated including VCS