Re: Correction to web site information: OpenMRS has debian packages available for download
Hi Andreas et al:
Sorry to bother... I have made some changes to the package but I am
actually not getting anything packaged :( and would appreciate any
help.
I am getting lots of messages like the bottom of this post (ignoring
deletion ...), and the whole source tree gets deleted. Any ideas?
Thank you
Misha
p.s. Perhaps the following will help _a lot_. I know I've read the
Package Maintainer's guide etc., but I am missing something quite
_basic_:
1. Let's say I check out a debian package for Debian Med from the svn
repository. Any package. I end up with a trunk directory that has a
debian folder in it.
2. What are the exact steps to go from that to having a deb... i.e., is it:
debian/rules get-orig-source
debuild
or something else?
I guess I am somewhat confused about how we store debian folders in
subversion but nothing else. Where does the source come from? Do
developers simply have the source locally and check out the debian
folder into the source folder?
If someone could perhaps clarify for our repository how one would go
from retrieving the debian folder to building a package in two or
three steps that would be great.
Thank you
Misha
---
misha@misha-d630:~/debianmed/trunk$ dpkg-buildpackage -d
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package openmrs
dpkg-buildpackage: source version 1.6.1-1
dpkg-buildpackage: source changed by Andreas Tille <tille@debian.org>
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
dh --with javahelper --with quilt clean
dh_testdir
dh_auto_clean
dh_quilt_unpatch
No patch removed
dh_clean
jh_clean
dpkg-source -b trunk
dpkg-source: info: using source format `1.0'
dpkg-source: warning: source directory 'trunk' is not
<sourcepackage>-<upstreamversion> 'openmrs-1.6.1'
dpkg-source: warning: .orig directory name trunk.orig is not
<package>-<upstreamversion> (wanted openmrs-1.6.1.orig)
dpkg-source: info: building openmrs using existing openmrs_1.6.1.orig.tar.gz
dpkg-source: info: building openmrs in openmrs_1.6.1-1.diff.gz
dpkg-source: warning: executable mode 0755 of 'debian/postrm' will not
be represented in diff
dpkg-source: warning: executable mode 0755 of 'debian/postinst' will
not be represented in diff
dpkg-source: warning: file trunk/debian/copyright has no final newline
(either original or modified version)
dpkg-source: warning: executable mode 0755 of 'debian/get-orig-source'
will not be represented in diff
dpkg-source: warning: file
trunk/debian/.svn/text-base/copyright.svn-base has no final newline
(either original or modified version)
dpkg-source: warning: file trunk/debian/patches/series has no final
newline (either original or modified version)
dpkg-source: warning: file
trunk/debian/patches/.svn/text-base/series.svn-base has no final
newline (either original or modified version)
dpkg-source: warning: ignoring deletion of file .classpath
dpkg-source: warning: ignoring deletion of file license.txt
dpkg-source: warning: ignoring deletion of file build.xml
dpkg-source: warning: ignoring deletion of file liquibase.build.xml
dpkg-source: warning: ignoring deletion of file readme.txt
dpkg-source: warning: ignoring deletion of file .project
...
On Mon, Sep 27, 2010 at 3:31 PM, Andreas Tille <andreas@an3as.eu> wrote:
> Hi Misha,
>
> I hope you don't mind if I quote you in public but I think there are
> some issues which might interest other people here. It is perfectly
> OK if you post your questions to the list in the future. They are
> on topic there.
>
> At first I'm happy that you made some progress!
>
> On Mon, Sep 27, 2010 at 11:44:27AM -0500, Misha Koshelev wrote:
>> Hi Andreas:
>>
>> Thanks for your detailed email.
>>
>> Sorry I didn't respond for a bit... but I did the issue with the ant
>> builds fixed upstream:
>> http://tickets.openmrs.org/browse/TRUNK-1759
>
> Great!
>
>> Also I wrote a little script for Ben Wolfe (one of our core maintainers)
>> to upload tarballs to Sourceforge.
>
> Great as well.
>
>> Unfortunately, it won't get fixed in the release until 1.6.2 is out,
>> which is not currently the case.
>
> This does not really matter IMHO because it is no real blocker for
> the moment.
>
>> Anyway, I can use quilt to get the patch. I've also set up a Debian
>> Squeeze system with pbuilder (barebones) in VMWare with which I am
>> happy.
>
> I'm happy that you finally solved this issue.
>
>> I am at the moment a little confused about the get-orig-source target.
>>
>> I noticed I can run it via:
>> debian/rules get-orig-source
>>
>> Is this supposed to get run automatically somehow? I noticed
>> dpkg-buildpackage does _not_ run it.
>
> Yes, that's normal. It is described in Developers Reference[1] and just
> a convention which comes handy if you are working in a team and
> everybody uses this. The script is also used by uscan in the
> debian/watch control file. However, dpkg-buildpackage just expects a
> ready prepared orig.tar.gz tarball.
>
>> In any case, no biggie. I will make a minor change so that the patches
>> which are going into 1.6.2 are applied via quilt and then commit to SVN
>> repo.
>
> Great.
>
>> What, if anything, do I need to do next? I will try to build the package
>> using pbuilder, and then what? Do I upload it somewhere?
>
> Just tell us here on list. Some Debian developer (probably me) will
> have a close look and try to rebuild the packages and test on his
> machine. In case everything is fine he will upload the package as so
> called sponsor. You are not allowed to upload to the Debian mirror as
> long as your GPG key is not in the keyring of Debian Developers or
> Debian Maintainers.
>
>> Any help appreciated?
>
> Hope this helps
>
> Andreas.
>
> --
> http://fam-tille.de
>
Reply to: