Re: git revision number for package update

> On Apr 22, 2020, at 2:38 PM, Hanspeter Niederstrasser <[email protected]> wrote:
> 
> On 4/22/20 12:31 PM, Ebrahim Mayat via Fink-devel wrote:
>> Dear Finkers,
>> I am trying to update the fluidsynth1 package which is now available from GitHub. I came across a couple of “minor” problems which I need to iron out.
>> 1. How can I get the revision number of the source from a git repository?
> 
> Not sure what you mean here. A git repo is a sequence of commits with some commits 'blessed' with tags, which are what are usually used to mark released versions. Revisions are not something that usually come up for git.
> In Fink, a revision is the tracker for changes to an individual package at a certain source version. So if you have Version: 2.1.1 and then realize something needs to change in the package (a bug, new feature), but it's still using the same version from upstream, the Revision field is increased to note that the older description is now outdated.
> 

Dear Hanspeter,

Thanks for your reply. So, if I understand correctly, my record of the source being revision 1 of version 2.1.1 is correct? 


>> 2. After package validation, I got the following warnings and error with the —build-as-nobody option
>>> % fink validate /opt/sw/fink/dists/local/main/finkinfo/fluidsynth1.info <http://fluidsynth1.info>
>>> 
>>> % fink -m --build-as-nobody rebuild fluidsynth1
> ...
>>> fluidsynth-2.1.1/test/test_synth_chorus_reverb.c
>>> fluidsynth-2.1.1/test/test_synth_process.c
>>> Removing runtime build-lock...
>>> Removing build-lock package...
>>> /opt/sw/bin/dpkg-lockwait -r fink-buildlock-fluidsynth1-2.1.1-1
>>> (Reading database ... 44429 files and directories currently installed.)
>>> Removing fink-buildlock-fluidsynth1-2.1.1-1 ...
>>> Failed: directory /opt/sw/src/fink.build/fluidsynth1-2.1.1-1/v2.1.1 doesn't exist, check the package description
>> The source tarball is named "v2.1.1.tar.gz”. I wonder if this could be the problem?
> 
> By default, Fink assumes the tarball foo-x.y.z.tar.gz unpacks to the directory foo-x.y.z/. In your case, the tarball v2.1.1.tar.gz is assumed to expand to v2.1.1/ but in this case is actually fluidsynt-2.1.1.
> 
> Use the SourceRename: field to rename the tarball as it gets downloaded. This has the benefit of 1) being easier to know who owns that tarball (v2.1.1.tar.gz is not very informative), and 2) Fink will automatically know what directory the source is actually in.

Thanks for the information about the SourceRename field. I did not know about it. I envisage this field to immediately follow the “Source” field?
> 
>>>  % ls /opt/sw/src/fink.build
>>> fluidsynth1-2.1.1-1fluidsynth1-2.1.1-2.1.1perl5162-5.16.2-103
>> Attached is the package description.
> 
> The .info file you attached is for Version 1.1.6., not for the new 2.1.1 version you're testing.

No, there have been also many updates in the dependencies in addition to a change in the home page and source repo.
> 
> Hanspeter

Thanks again,
E

_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel