Package: dpkg-dev
Version: 1.22.0
Severity: normal
Dear Maintainer,
* What led up to the situation?
using: dpkg-source --commit
* What exactly did you do (or not do) that was effective (or
ineffective)?
I used `update-alternatives --config editor` because I want to edit with
vim.
(actually it became the default editor already by manually install
vim-gtk3)
* What was the outcome of this action?
dpkg-source uses nano
* What outcome did you expect instead?
dpkg-source using vim (or just call `editor`)
-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dpkg-dev depends on:
ii binutils 2.41-4
ii bzip2 1.0.8-5+b1
ii libdpkg-perl 1.22.0
ii make 4.3-4.1
ii patch 2.7.6-7
ii perl 5.36.0-7
ii tar 1.34+dfsg-1.2
ii xz-utils 5.4.4-0.1
Versions of packages dpkg-dev recommends:
ii build-essential 12.10
ii clang-14 [c-compiler] 1:14.0.6-13
ii fakeroot 1.32.1-1
ii gcc [c-compiler] 4:13.2.0-1
ii gcc-13 [c-compiler] 13.2.0-2
ii gnupg 2.2.40-1.1
ii gpgv 2.2.40-1.1
ii libalgorithm-merge-perl 0.08-5
Versions of packages dpkg-dev suggests:
ii debian-keyring 2023.05.26
-- no debconf information
