ubuntu-packaging-guide-team team mailing list archive
-
ubuntu-packaging-guide-team team
-
Mailing list archive
-
Message #01897
[Bug 1248353] Re: Probem in Packaging New Software Article
I am experiencing this same issue with hello-2.10 as described on
http://packaging.ubuntu.com/html/packaging-new-software.html.
--
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/1248353
Title:
Probem in Packaging New Software Article
Status in Ubuntu Packaging Guide:
Fix Released
Bug description:
I am attempting to get through the "packaging new software" section
(http://developer.ubuntu.com/packaging/html/packaging-new-
software.html) of ubuntu's packaging guide. I have hit a roadblock and
am hoping that somebody can point me in the right direction.
When I get to the point were it asks me to insert the code:
[CODE]$ bzr builddeb -- -us -uc[/CODE]
I get this message in the terminal:
[CODE]
make[1]: Entering directory `/home/morgan/build-area/hello-2.9'
There seems to be no Makefile in this directory.
You must run ./configure before running 'make'.
make[1]: *** [abort-due-to-no-makefile] Error 1
make[1]: Leaving directory `/home/morgan/build-area/hello-2.9'
dh_auto_clean: make -j1 distclean returned exit code 2
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
debuild: fatal error at line 1361:
dpkg-buildpackage -rfakeroot -D -us -uc failed
bzr: ERROR: The build failed.
morgan@morgans-laptop:~/hello/debian$
[/CODE]
I am assuming that this means I am missing a makefile so it is not
able to get past that. I just dont understand why I am missing a
makefile or where to get it.
To get to this point I have followed the "GETTING SET UP" article
(http://developer.ubuntu.com/packaging/html/getting-set-up.html) and
the "PACKAGING NEW SOFTWARE" article
(http://developer.ubuntu.com/packaging/html/packaging-new-
software.html) point by point.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1248353/+subscriptions
References