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

Re: "dh_autoreconf: Can only be run once, see dh-autoreconf" when building package from Sid for Stretch

On Sep 3, 2018, at 22:53, 丰 <hxf.prc@gmail.com> wrote:

Hi, Jacob

This is because the Backports Release file has "NotAutomatic: yes", which means that apt won’t get package
dependencies from there. However, aptitude will. So you could call sbuild like this:

Thank you for your explanation.

sbuild --build-dep-resolver=aptitude --extra-repository="deb http://deb.debian.org/debian stretch-backports main" -d stretch-backports .

Both package can be build with your method now. But
"stretch-backports" was still not a valid release on my side. Maybe it
was because I really didn't have a schroot for "stretch-backports".
Error in the build log was:

E: Chroot for distribution stretch-backports, architecture amd64 not found
E: Error creating chroot

My original email included this note, as in my my setup stretch-backports is an alias for my stretch schroot:
(Note that this also assumes that stretch-backports is an alias to stretch, see https://wiki.debian.org/sbuild#Using_aliases )

So I changed a little bit. I built with the following command, using
source directly from sid.

sbuild --build-dep-resolver=aptitude --extra-repository="deb
http://mirrors.ustc.edu.cn/debian stretch-backports main" -d stretch

Building for stretch works just as well, but it means the package will have a distribution of “stretch” regardless of what the changelog says. This could be a problem if you’re going to upload the package to stretch-backports but otherwise shouldn’t matter. 

BTW, I didn't know why your email did not show up in my gmail inbox.
Luckily I looked at
https://lists.debian.org/debian-backports/2018/09/threads.html first
and saw your reply. So I had to copy the content from that link and
added my response below. Hope it all format correctly in your email

Apologizes. It’s common practice on these mailing lists to send only to the list and assume the original sender is subscribed. This is supposed to prevent duplicates but it often just means that they miss your reply. Including a note to CC you on replies in future emails should help to ensure that such messages don’t miss your inbox. 


Reply to: