Your message dated Wed, 08 Nov 2023 14:29:33 +0900
with message-id <[email protected]>
and subject line Re: Bug#1052980: debmake-doc: sbuild config should set
$piuparts to '/usr/sbin/piuparts'
has caused the Debian Bug report #1052980,
regarding debmake-doc: sbuild config should set $piuparts to
'/usr/sbin/piuparts'
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 [email protected]
immediately.)
--
1052980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debmake-doc
Version: 1.17-7
Severity: normal
Using the .sbuildrc in the debmake documentation, when I build my
package with sbuild piuparts fails, because it can't be located in the
search path when sudo piuparts is called. Setting $piuparts explicitly
to /usr/sbin/piuparts in .sbuildrc works around this. This is probably
a bug in sbuild (and I will file a separate bug with sbuild about
that), but in the meantime it wouldn't hurt to document the
workaround.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic
APT policy: (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-5-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
debmake-doc depends on no packages.
Versions of packages debmake-doc recommends:
ii debmake 4.4.0-1
Versions of packages debmake-doc suggests:
pn debian-policy <none>
pn developers-reference <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Tue, 2023-09-26 at 11:24 -0400, Jonathan Kamens wrote:
> Package: debmake-doc
> Version: 1.17-7
> Severity: normal
>
> Using the .sbuildrc in the debmake documentation, when I build my
> package with sbuild piuparts fails, because it can't be located in the
> search path when sudo piuparts is called. Setting $piuparts explicitly
> to /usr/sbin/piuparts in .sbuildrc works around this. This is probably
> a bug in sbuild (and I will file a separate bug with sbuild about
> that), but in the meantime it wouldn't hurt to document the
> workaround.
Are you sure? It works here. (Without build log, I can't be sure.)
I had some issue with piuparts:
updated 7.10 chroot in today's upload (1.17-8) has:
Note
When an essential package becomes a non-essential one (e.g., adduser), you
need to remove it manually from the existing chroot environment.
This was causing piuparts failure for me.
Let me close this. If what you see is different from my case, please reopen
this bug with your build log attached.
Osamu
--- End Message ---
