On Wed, Nov 25, 2015 at 12:57:50AM +0900, Norbert Preining wrote: > Hi Santiago, > > thanks for your report, very interesting. I am using the same > stanza in my rules file since quite some time, and never got > any problems.
Just try "dpkg-buildpackage -A" (as I explain in the bug report) and you will see the problem. > > This usually happens because there is a binary-indep target in debian/rules > > which is either empty or does not do anything useful. > > Hmmm, I don't see any of these cases: > > [...] > > so from what I see is that a call to > binary-indep > should do something useful, namely: > binary-indep -> build -> build-arch and build-indep -> build-stamp > -> do all the stuff > binary-indep -> install -> install-stamp -> copy the stuff > > So there should something happen? It's not enough that debian/rules builds stuff and put it somewhere in debian/package. For the .deb packages to be actually created, one or more calls to dh_builddeb (since you are using debhelper) are needed. In this case, those calls never happen when you do "dpkg-buildpackage -A", because you have put all the dh_builddeb calls in binary-arch, which is only for architecture-dependent packages. The calls should be split: binary-arch should create the binary-dependent packages (and only those), and binary-indep should create the binary-independent packages (and only those). This is the reason why (in this package) "dpkg-buildpackage" works while "dpkg-buildpackage -A" does not. Both things should work, but this is not new, it's already policy since a looooong time. > > properly, this package will be suitable to be uploaded in source-only form > > if you wish > > (I recommend that you try it). > > Is there a way to *try* it? I don't like playing around and tagging > and then seeing rejections and failures. Source-only uploads are currently accepted and they work. Just build the package with "dpkg-buildpackage -S" and upload the result (which will be a Debian source package without any .deb). But it is *very* important that you first ensure that both "dpkg-buildpackage -B" and "dpkg-buildpackage -A" work, as the arch-all and arch-any packages are built by different autobuilders. > For now I don't see any big problem, In such case, please read policy, where this is probably explained much better than I could, and try "dpkg-buildpackage -A" for yourself. Thanks.
