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

Bug#1002626: marked as done (When Rules-Require-Root: no, packages should not fail to build as non-root)

Your message dated Mon, 27 Dec 2021 17:54:24 -0700
with message-id <87mtkly2f3.fsf@melete.silentflame.com>
and subject line Re: Bug#1002626: debian-policy: building packages should not require to be root
has caused the Debian Bug report #1002626,
regarding When Rules-Require-Root: no, packages should not fail to build as non-root
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1002626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002626
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-policy
Version: 4.6.0.1
Severity: important

Building packages should not require to be root.

I don't know what's going on, but see

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002497#31

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

debian-policy depends on no packages.

Versions of packages debian-policy recommends:
ii  libjs-sphinxdoc  4.3.2-1

Versions of packages debian-policy suggests:
ii  doc-base  0.11.1

-- no debconf information

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---
--- Begin Message --- 
Hello Russ,

On Mon 27 Dec 2021 at 12:50PM -08, Russ Allbery wrote:

> FWIW, I think Policy requirements may be the wrong way of thinking about
> this problem.  If I try to compile a Perl module with GCC in debian/rules,
> I would be hard-pressed to name a specific Policy requirement that
> violates, but the package wouldn't build and that's a FTBFS bug.  This
> feels more like that: the package metadata says to build it as non-root,
> which means that if it doesn't build as non-root, that's a FTBFS bug.

The sort of case I have in mind is an 'RRR: no'%e package that does not
FTBFS when built as root, but does do so as non-root.  I agree that
that's an FTBFS bug, but is it release-critical?  For a relatively new
feature like RRR, I'm not sure it is, unless Policy says it is.  But I
could be convinced, and I agree with you that the sort of reasoning
you're giving is a good way to think about this sort of thing.

> Anyway, it all seems to be sorted out now, and I suspect the root problem
> was some benign misunderstanding of the root cause Vincent's bug report.

Optimistically going ahead and closing the bug :)

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: