packaging

I'm trying to create a deb package from binaries but I have a problem with copyright file. If I place a file named copyright inside DEBIAN folder it complains of two things: Missing copyright Unknown control file copyright If I place it under /usr/share/doc or /usr/share/doc/mypackage it does not complain at all but, in any case, when I open generated debian package, Ubuntu Software Center states License: Unknown Using: ubuntu raring Executing fakeroot dpkg-deb -z8 -Zgzip --build myproj Copyright file looks as follows: Format: http://dep.debian.net/deps/dep5 Upstream-Name: myproj Source: Files

I would like to use a rpm to build subpackages for different environments (live,testing,developer) but for the same files, so having a package called name-config-live, one called name-config-testing and one called name-config-developer and in them to have the same paths but each with the configs corresponding to the environment it's named after. as an example let's say on all environments I have a file called /etc/name.conf and on testing I want it to contain "1", on development "2" and on live "3". Is it possible to do this in the same spec since the subpackage generation only happens last

I have created a package that I will be distributing throughout the company that replaces a legacy bash script with the same name. It is referenced many places so it needs to execute like the current script does. This has worked fine until I encountered some servers that do not have a current version of Python as the default Python (aka CentOS). Is there a way to specify in the setup.py what shebang line is created at the top of the script file? i.e. I need #!/opt/bin/python rather than #!/usr/bin/env python . Run the script with /opt/bin/python script.py , or edit the first line to read #!

This question already has an answer here: python: can executable zip files include data files? 4 answers I'm doing a little program and I want to distribute it using this recipe: single directory with __main__.py in it zip this directory and adding a shebang on it #!/usr/bin/env python making it executable The problem is that in this package I have also extra files (I'm using pygtk toolkit and I need images and ui xml files). When I try to access these files I have the error that the resource is unavailable (the path that I'm trying to open is something like file.zip/gui/gui.ui ). How can I

I'm building an Android app from a Maven project that is using the android-maven-plugin. In this project I'm using the new beta data-binding library. It is contained in the local m2repository of the Android SDK (extras/android/m2repository). The libraries in this repository are packaged as type aar. I can add the dependency in my pom like this: <dependency> <groupId>com.android.databinding</groupId> <artifactId>library</artifactId> <version>1.0-rc1</version> <type>aar</type> </dependency> This seems to work, but the build fails with this: Failed to execute goal on project demo: Could not

In my spec file for packaging a python rpm, I want to remove certain filetypes in certain directories: e.g., I want to exclude source *.py files in these directories: lib/*.py comm/*.py I think I should do this in the %file section of my spec. Any suggestions? At one point in the distant past, you did that by just not including the files you didn't want in the %file section, and so they would not be packaged. That might have turned out to be too error prone, and so some RPM implementations started complaining about unpackaged files. Since RPM development has always been a bit fragmented and