Skip to contentSkip to conversation

Please migrate xfsdump and xfsprogs Debian packaging to Salsa

DISCUSSION Andreas Tille 4 participants 9 messages Apr 12 – Apr 13

lore
Share & tools
lore
#0 lore raw

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

Signature · 1 line
https://fam-tille.de
#1 lore raw
Quoted 8 lines · Andreas Tille

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

Quoted 7 lines

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

--D

Quoted 12 lines

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

Signature · 1 line
https://fam-tille.de
#2 lore raw

Hi Darrick,

thank you for your quick response.

Am Sun, Apr 12, 2026 at 08:55:34PM -0700 schrieb Darrick J. Wong:

Quoted 8 lines
Quoted 2 lines

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

Yes. While I would prefer maintenance on salsa.debian.org for the Debian packaging having setting those fields is helpful in any case.

Kind regards
Andreas.

Signature · 1 line
https://fam-tille.de
#3 lore raw
In reply to Darrick J. Wong
Quoted 14 lines · Darrick J. Wong
Quoted 13 lines · Andreas Tille

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

Quoted 8 lines
Quoted 2 lines

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

ohh.. debian-specific fields for which VCS it uses seems like.

Quoted 16 lines

--D

Quoted 12 lines

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

Signature · 1 line
https://fam-tille.de
#4 lore raw

Hi Carlos,

Am Mon, Apr 13, 2026 at 12:41:08PM +0200 schrieb Carlos Maiolino:

Quoted 10 lines
Quoted 8 lines
Quoted 2 lines

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

ohh.. debian-specific fields for which VCS it uses seems like.

Yes, Debian specific ... and https://salsa.debian.org is Gitlab instance Debian is using for the vast majority of packages. In general there are good reasons to do the packaging there (for instance to not disturb upstream maintainers like you with the communication ;-) ) but there are exceptions from this rule. I'd be happy to hear from the persons (Anibal and Nathan are listed) who usually care for the Debian packaging whether such an exception are these xfs related packages.

If not I'd happily lend a helping hand to migrate the Debian packaging to Salsa.

Kind regards
Andreas.

Signature · 1 line
https://fam-tille.de
#5 lore raw
Quoted 22 lines · Andreas Tille

Hi Carlos,

Am Mon, Apr 13, 2026 at 12:41:08PM +0200 schrieb Carlos Maiolino:

Quoted 10 lines
Quoted 8 lines
Quoted 2 lines

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

ohh.. debian-specific fields for which VCS it uses seems like.

Yes, Debian specific ... and https://salsa.debian.org is Gitlab instance Debian is using for the vast majority of packages. In general there are good reasons to do the packaging there (for instance to not disturb upstream maintainers like you with the communication ;-) ) but there are exceptions from this rule. I'd be happy to hear from the persons (Anibal and Nathan are listed) who usually care for the Debian packaging whether such an exception are these xfs related packages.

Quoted 2 lines

If not I'd happily lend a helping hand to migrate the Debian packaging to Salsa.

Ah.. Thanks! this helps a lot!

Quoted 7 lines

Kind regards
Andreas.

Signature · 1 line
https://fam-tille.de
#6 lore raw
In reply to Darrick J. Wong

Hi all,

Quoted 15 lines · Darrick J. Wong
Quoted 13 lines · Andreas Tille

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

Quoted 8 lines
Quoted 2 lines

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

That's more or less a matter of setting a couple of fields in debian/control, right?

Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master

This is the correct approach to represent the xfsprogs setup, thanks!

cheers.

--
Nathan

Quoted 15 lines

--D

Quoted 12 lines

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

--
https://fam-tille.de

#7 lore raw
In reply to Andreas Tille

Hi Andreas.

Quoted 16 lines · Andreas Tille

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

Quoted 8 lines

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

I'm not sure what Salsa is, nor what Vcs fields are, I'm assuming this is a Debian specific thing and I'm not that familiar with Debian ecosystem...

I'm assuming this is something debian-specific? Perhaps Nathan can chime in here, because this does not think something related to xfsprogs upstream development?!

I'm not the xfsprogs maintainer though, but this doesn't seem to be concerning with xfsprogs upstream development.

Quoted 4 lines
Signature · 2 lines
-- 
https://fam-tille.de
#8 lore raw
Quoted 32 lines · Carlos Maiolino

Hi Andreas.

Quoted 16 lines · Andreas Tille

Hi XFS Development Team,

I'm currently reviewing team-maintained packages that are not exposing Vcs fields. I assume for some efficient team work you are maintaining

xfsdump
xfsprogs

in some Git repository, but the Vcs fields are not set and I could not find corresponding repositories on Salsa. I'm not even sure whether you might have some team space there or whether the Debian team might sufficiently fulfill your needs.

I'd be happy if these packages could be maintained in a publicly visible Git repository on Salsa, with appropriate Vcs fields set.

Quoted 8 lines

If there are specific reasons why this is currently not the case, I would be interested to understand them as well.

If you need any help with creating some Git repository I can happily do so since I have developed some training in doing this.

Thanks for your work on XFS in Debian, and best regards,
Andreas.

I'm not sure what Salsa is, nor what Vcs fields are, I'm assuming this is a Debian specific thing and I'm not that familiar with Debian ecosystem...

Quoted 6 lines

I'm assuming this is something debian-specific? Perhaps Nathan can chime in here, because this does not think something related to xfsprogs upstream development?!

I'm not the xfsprogs maintainer though, but this doesn't seem to be concerning with xfsprogs upstream development.

It is, in the sense that (at least at one time) the debian/ files in the upstream master branch were used to generate the debian packages. Nowadays there's a slight divergence every now and then for Debian to integrate patch backports to old release.

--D