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

Bug#1016340: openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.



Source: openssh
Version: 1:9.0p1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> # Remove version control tags to avoid unnecessary conffile
> # resolution steps for administrators.
> sed -i '/\$OpenBSD:/d' \
> 	debian/tmp/etc/ssh/moduli \
> 	debian/tmp/etc/ssh/ssh_config \
> 	debian/tmp/etc/ssh/sshd_config
> dh_install -Nopenssh-client-udeb -Nopenssh-server-udeb
> dh_install -popenssh-client-udeb -popenssh-server-udeb \
> 	--sourcedir=debian/build-udeb
> Failed to copy 'etc/ssh/sshd_config': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
> dh_install: error: debian/openssh-server.install (executable config) returned exit code 127
> make[1]: *** [debian/rules:163: override_dh_install-arch] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/openssh_9.0p1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.


Reply to: