Advanced search
Log In
New Account
  
Home My Page Project Cloud Code Snippets Project Openings ESbox
Summary Forums Tracker Lists Tasks News SCM Files Wiki

Bugs: Browse | Download .csv

[#3358] Python Project: Fails to build debian package

Please login

State:
Open
Date:
2009-01-21 12:39
Priority:
5
Submitted By:
Juha Hentunen (juhentun1)
Assigned To:
Ilja Pyykkonen (ilpyykko)
Summary:
Python Project: Fails to build debian package

Detailed description
PROCEDURE: 
1. Create a new project (Use template Python - > Maemo Python Hildon Hello World Project).
2. Select DIABLO_X86 target. 
3. Generate Debian structure. Right - click on each project and select Debian Package - > Create Debian Structure. 
4. Right - click on each project and select Debian Package - > Create Debian Package. 
5. Check if the files 
<pythonhildonhelloworld_1.0_i386.[deb,changes,dsc,tar.gz]> were created on folder previously selected. 

After Step 3 (console): 
 Currently there is no top level Makefile. This may require additional tuning. 
Done. Please edit the files in the debian/ subdirectory now. You should also check that the pythonhildonhelloworld Makefiles
install into $DESTDIR and not in / .

After Step 4 (console) 
:make[1]: *** No targets specified and no makefile found.  Stop

Followup

Message
Date: 2009-09-16 08:56
Sender: Juha  Hentunen

Verified using build mica_esbox_pluthon_3.4.2_build.493.
Date: 2009-09-09 12:31
Sender: Ilja Pyykkonen

- Created Makefile and setup.py generator for Python projects
- Updated Python templates

Fixed in commit r2729, 2009-09-09.
Date: 2009-09-01 12:58
Sender: Ed Swartz

I guess we do need to do something here.  It's not going away
from being ignored ;)

Python projects don't have a Makefile at all, so for any Python
project we generate, this issue will arise when using Create
Debian Structure, since the default debian/rules tries to run
make.

So, either we need to:

1) provide a debian/ folder that works (so that creating the
Makefile and/or editing the debian/rules file is not a manual
step)
or 
2) provide a Makefile that (say) provides an empty "make
all" target and a "make install" target which
deploys the application into /usr/lib/python*/site-packages.

(We need the empty 'make all' target because the presence of
a makefile might make the Convert to ... project wizard assign
a make builder, and we want to still do nothing when building
in Eclipse.)
Date: 2009-03-16 08:45
Sender: Mika Rasanen

Fails in sprint 5 tests:
http://200.157.251.139/testlink/lib/execute/execSetResults.php?le
vel=testcase&build_id=1&id=43&version_id=44
Date: 2009-02-13 20:27
Sender: Fabricio Epaminondas

Hi, 

  The feature "Debian Pacakge" helps user to debianize
(create debian structure default), build and install the packages.
But between step 1 and 2 exists some configurations to do manually
by user as described on Debian Manual
(http://www.debian.org/doc/maint-guide/ch-first.en.html,  topic
2.4, chapter 4, etc..) and we follow these rules because this
configuration is application specific

 So steps described on Test Case Procedure, can only be executed
in this order if you run on "project created from template"
with a pré-defined debian template folder and all configurations
done.
 Otherwhise, you must add to test case a new step between step
3 and 4: Configure debian files. That is the debianize procedure.
 

Attached Files:

Name Download
No Files Currently Attached

Changes:

Field Old Value Date By
ResolutionFixed2009-09-16 08:56juhentun1
ResolutionNone2009-09-09 12:31ilpyykko
assigned_tonone2009-09-08 08:48ilpyykko
ResolutionAwating Response2009-05-18 06:31juhentun1
status_idClosed2009-05-18 06:31juhentun1
close_date2009-04-08 14:192009-04-08 14:19fabricioepa
status_idOpen2009-04-08 14:19fabricioepa
ResolutionNone2009-02-13 20:27fabricioepa
priority32009-02-10 14:40eswartz

Terms of Use    Privacy Policy    Contribution Guidelines    Feedback

Powered By GForge Collaborative Development Environment