Bug#970234: consider dropping "No hard links in source packages"
Russ Allbery <rra@debian.org> writes:
> The fact that this has gone unnoticed in a source package in an existing
> release makes a pretty strong argument that nothing in Debian cares and
> we should just remove the constraint.
Here is a patch dropping the restriction on hard links in source packages
that I think is ready for seconds. I'm copying Guillem for his review, in
case there's some dpkg concern.
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
>From 12b014c4b930577a728dfb1254b64aac6a5eb1e0 Mon Sep 17 00:00:00 2001
From: Russ Allbery <rra@debian.org>
Date: Thu, 22 Sep 2022 19:15:52 -0700
Subject: [PATCH] Allow hard links in source packages
It's not clear why this restriction was in place, and Debian
included a package containing hard links without anyone noticing
in the last release.
---
policy/ch-source.rst | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index c7415fc..a7df539 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -282,8 +282,8 @@ source files in a package, as far as is reasonably possible. [#]_
Restrictions on objects in source packages
------------------------------------------
-The source package must not contain any hard links, [#]_ device special
-files, sockets or setuid or setgid files.. [#]_
+The source package must not contain device special files, sockets, or
+setuid or setgid files. [#]_
.. _s-debianrules:
@@ -918,13 +918,6 @@ must not exist a file ``debian/patches/foo.series`` for any ``foo``.
would be nice if the modification time of the upstream source would
be preserved.
-.. [#]
- This is not currently detected when building source packages, but
- only when extracting them.
-
- Hard links may be permitted at some point in the future, but would
- require a fair amount of work.
-
.. [#]
Setgid directories are allowed.
--
2.37.2
Reply to: