Re: [MoM] Packaging fis-get
Hi Luis,
On Wed, Feb 08, 2012 at 09:30:42PM -0500, Luis Ibanez wrote:
>
> It is great to see the debian/watch role
> http://www.debian.org/doc/debian-policy/ch-source.html#s-debianwatch
> (another thing that I needed to learn).
I admit that as a beginner I underestimated watch a lot (admittedly when
I was a beginner it was not that useful for several reasons). Today I'm
actually starting new programs by writing a watch file in the very first
place (well, you need a skeleton of changelog and control as well to let
uscan work properly). The rationale is: The first thing I need is the
upstream source. I want to get the upstream source and this is done by
a proper watch file - so lets start with this.
> > discussed in the previous mails under Depends. However, these are
> > required to build the package and thus I moved the files to
> > Build-Depends to enable properly building the package.
>
> Yes, my bad.
Not "bad" actually - just a misunderstanding which was clarified now
thought.
> Now that you pointed out, I see the difference
> use between Build-Depends and Depends.
Good.
> > Usually the building tools are realising themselves via dh_shlibdeps.
> > (see manpage). There is no point in calling this explicitely when using
> > dh, everything works automagically - provided you are using
> > ${shlibs:Depends} in Depends (and so I did).
>
> Thanks for pointing me to the man page.
> It was very instructive to read the page.
>
> It is probably a good standard item to include in the MoM
> training check-list. It certainly clarifies the content of the control file.
I somehow have the feeling that it is hard to write such a check-list.
IMHO there is a right time to learn some specific thing and you can not
really know in advance when this time has come. You need a "motivation"
to learn about things like this and this motivation was in this specific
case the improperly set (Build-)Depends. In my beginner phase it came
later to read this specific manual.
> > tcsh ./setupenv.sh
> > ----- Start the build -----
> > Linux Host 64
> > Linux Host linux x86_64 x86_regs
> > Source Directory List: sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
> > make[2]: Entering directory `/tmp/buildd/fis-gtm-5.4-002B'
> > make[2]: *** No rule to make target `gtmshr_symbols.export', needed by `../libgtmshr.so'. Stop.
> > make[2]: Leaving directory `/tmp/buildd/fis-gtm-5.4-002B'
> > ------ End of build -------
> > make[1]: Leaving directory `/tmp/buildd/fis-gtm-5.4-002B'
> > dh_auto_test
> > ...
>
> Yes,
> I can replicate this problem here, when I do "debuild".
>
> However, when I call directly: tcsh setupenv.sh
Not for me:
$ tcsh setupenv.sh
----- Start the build -----
Linux Host 64
Linux Host linux x86_64 x86_regs
Source Directory List: sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
tcsh -f /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/sr_unix/gen_xfer_desc.csh sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj
~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj
tcsh -f /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/sr_unix/gen_gtm_threadgbl_deftypes.csh /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B sr_port pro/obj sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
Entering gen_gtm_threadgbl_deftypes.csh to build gtm_threadgbl_deftypes.h
~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B
gen_gtm_threadgbl_deftypes.csh-E-: pro build link of /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj/gtm_threadgbl_deftypes failed, see /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj/gtm_threadgbl_deftypes_linkmap.txt
~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B
make: *** [gtm_threadgbl_deftypes] Fehler 1
------ End of build -------
(sorry for German locale "Fehler" = "error")
> the build proceeds as expected,
> and finishes successfully.
>
> So, I need to study "debuild" more, to understand what
> is different by the time "tcsh setupenv.sh" is called.
I do not see a reason why this should be different. The only reason
might be some preset environment variables.
> >> 1) I'm getting some warnings from changelog
> >> when doing "debuild". I probably have some
> >> lines formatted incorrectly.
> >
> > I did not noticed this on my side.
> >
>
> Sorry, I should have reported the fix for this.
> It turned out to be the formatting of the date field.
> A fix was committed for it by the time you looked at it.
Ahh. BTW, if you are using dch to edit the changelog and you
do not fiddle around with the dates no problems should occure.
> I'm guessing that the environment is different when
> things are called through "debuild", with respect to
> when the command "tcsh setupenv.sh" is called
> directly.
Fits exactly my suspicion.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: