[otb] 02/02: update amd64 symbols for 5.2

Rashad Kanavath rashad.kanavath at c-s.fr
Wed Dec 23 14:04:58 UTC 2015



On 12/23/2015 12:00 PM, Sebastiaan Couwenberg wrote:
> On 23-12-15 11:36, Rashad Kanavath wrote:
>> --- a/debian/libotbapplicationengine-5.2-1.symbols
>> +++ b/debian/libotbapplicationengine-5.2-1.symbols
>> @@ -1,21591 +1,20415 @@
>> -# SymbolsHelper-Confirmed: 5.0.0 amd64 i386
>> -libOTBApplicationEngine-5.0.so.1 libotbapplicationengine-5.0-1 #MINVER#
>> ...
>> +# SymbolsHelper-Confirmed: 5.2.0 amd64
>> +libOTBApplicationEngine-5.2.so.1 libotbapplicationengine-5.2-1 #MINVER#
> We renaming symbols files for a new SONAME, you also need to edit the
> dependency line in the symbols file to match the name library SONAME and
> package name.
>
> For this example that would become:
>
>   # SymbolsHelper-Confirmed: 5.0.0 amd64 i386
>   libOTBApplicationEngine-5.2.so.1 libotbapplicationengine-5.2-1 #MINVER#
>
> dpkg-gensymbols will then keep the version history in the symbols file
> instead of generating a completely new file for library SONAME. You have
> now lost which symbols where introduced in 5.0 and not changed in 5.2.

Okay. I had removed and generated new symbol files!. Should I revert 
back the files and then update them again?

since package was not uploaded anywhere, I did this way.
>
> This is quite similar to the renamed lintian overrides, just renaming
> the files is not sufficient, you also need to make minimal edits to the
> files.
I will correct this right away. Maybe we can use a .in file. What do you 
think ?
>
> Also try to keep your commits as single logical changes, the spelling
> patch update does not belong in this commit.

spelling patch was a disaster on my side. It took some time for me to 
get into the quilt workflow.

I promise I will be careful next time.


>
> http://pkg-grass.alioth.debian.org/policy/packaging.html#git-commit-policy
>
> Please review your changes before pushing them to Alioth, this gives you
> the opportunity to rebase your changes into a well formed patch series
> with logical changes per commit. This eases the review burden significantly.
>
> Kind Regards,
>
> Bas
>




More information about the Pkg-grass-devel mailing list