Re: How to avoid "all arch" notice in dpkg-buildpackage.
Hi and thanks again.
On 05/31/2013 02:58 AM, Andrey Rahmatullin wrote:
On Thu, May 30, 2013 at 06:38:30PM -0400, linux at iocellnetworks wrote:
I am working on the debian package for 7.0 ndas.
I would like to have it build without comment, notice or error.
I use the instructions here
Where?
Sorry.
These are the build instructions:
https://github.com/iocellnetworks/ndas4linux/wiki/How-to-build,-install-and-remove-.deb-ndas-packages
These are not instructions how to write a debian package, they tell about
building an existing one, using code that you didn't write or even read.
Actually, I've been reading it quite a while, but surely not
understanding it well.
That is why and am looking for help on the subject.
There are some notices left though in the dh_ commands.
example: dh_builddeb: You asked that all arch in(dep) packages be
built, but there are none of that type
Can any of y'all point me to the place those are specified so I can
have it build those, or bypass?
Mostly impossible to tell without seeing your debian/rules.
Rules on this build are here:
https://github.com/iocellnetworks/ndas4linux/blob/master/3.2.0/platform/linux/tarball-tag/debian/rules
# This version is for a hypothetical package that can build a kernel
# modules
# architecture-dependant package via make-kpkg, as well as an
# architecture-independent module source package, and other packages
# either dep/indep for things like common files or userspace components
# needed for the kernel modules.
It's fine that this generic code for a hypothetical package generates some
harmless warnings.
I guess it is still a hypothetical package, relative to distribution
through Debian.
But it has worked for quite some time.
If the warnings are harmless, that is fine too.
If you are
calling programs with -i while not having any arch-indep packages then you
should not do that
Maybe this is where to start? The architecture in the control file
says "all".
I changed the one for the modules to amd64, when I am building on
the 64Bit version.
I got the notice in either case.
Please don't do things you don't understand to fix problems that do not
exist.
If you really want to fix those warnings you need to understand how does
this debian/rules work and what causes the warnings, and then fix them.
To understand how debian/rules works, and get on my way to a clean,
acceptable
package creation is why I am writing for help.
(it's also not a good idea to blindly copy-paste code
>from some instructions on the web without understanding what does that
code do).
I do run the code, almost as it was from the beginning. I did not
write it, but I also
do not know what it does, since I have not much experience.
Then you don't need to fix those warnings.
When I looked around to learn what they mean, I found a post from a mentor
instructing a mentee to solve those warnings before submitting a package.
http://lists.debian.org/debian-mentors/2009/06/msg00155.html
So, I figured I would ask how to solve the warnings.
Reply to: