Devuan bug report logs -
#569
(no subject)
Reported by: Austin France <adf@sorcerer.co.uk>
Date: Sat, 13 Mar 2021 23:33:02 UTC
Severity: grave
Tags: debian, invalid, moreinfo
Found in version 3.0043
Done: Mark Hindley <mark@hindley.org.uk>
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your bug report
which was filed against the ucf package:
#569: (no subject)
It has been closed by Mark Hindley <mark@hindley.org.uk>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.
--
569: https://bugs.devuan.org/cgi/bugreport.cgi?bug=569
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
tags 569 + invalid
thanks
On Tue, Mar 16, 2021 at 06:44:07PM +0000, Mark Hindley wrote:
> > sudo apt-get install openssh-server
> >
> > * What was the outcome of this action?
> >
> > Setting up openssh-server (1:8.4p1-4) ...
> > /usr/bin/ucf[734]: >&3 : bad file descriptor
>
> Neither openssh-server nor ucf are forked packages and Devuan uses Debian's
> packages directly without recompilation. So this report should go to Debian's
> BTS.
>
> In addition:
>
> > -- System Information:
> > Distributor ID: Nitrux
> > Description: Nitrux 1.3.7 build.290121
> > Release: 1.3.7 build.290121
> > Codename: nitrux
> > Architecture: x86_64
>
> I see you are using Nitrux. I am unsure how that combines Ubuntu and Devuan and
> what effect that may have here?
According to this post[1], Nitrux uses mksh as /bin/sh and this can cause the
"bad file descriptor" error above.
Closing here. Please report to Nitrux BTS.
Thanks
Mark
[1] https://github.com/Nitrux/nitrux-bug-tracker/issues/15#issuecomment-709654613
[Message part 3 (message/rfc822, inline)]
Package: ucf
Version: 3.0043
Severity: grave
Dear Maintainer,
* What led up to the situation?
sudo apt-get install openssh-server
* What was the outcome of this action?
Setting up openssh-server (1:8.4p1-4) ...
/usr/bin/ucf[734]: >&3 : bad file descriptor
dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What outcome did you expect instead?
openssh-server to be automatically configured. I had to manually
configure openssh-server then hack /var/lib/dpkg/status to stop apt-get
trying to configure it at every oppertunity.
-- System Information:
Distributor ID: Nitrux
Description: Nitrux 1.3.7 build.290121
Release: 1.3.7 build.290121
Codename: nitrux
Architecture: x86_64
Kernel: Linux 5.10.10-051010-generic (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/mksh
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled
Versions of packages ucf depends on:
ii coreutils 8.32-4+b1
ii debconf 1.5.74
ii sensible-utils 0.0.14
ucf recommends no packages.
ucf suggests no packages.
-- debconf information:
ucf/conflicts_found:
ucf/title:
ucf/changeprompt_threeway: keep_current
ucf/changeprompt: keep_current
ucf/show_diff:
Send a report that this bug log contains spam.