Active Topics

 


Reply
Thread Tools
Chrome's Avatar
Posts: 349 | Thanked: 309 times | Joined on Feb 2010 @ PS/IL
#1
Lets say we have this package: callforwarding_1.0-1_armel.deb

inside the package there's the control folder, and inside it there is "md5sums" which contains paths for various stuff afaik. For example:

8fbde587a6965bbaf5e8e301a4d80589 usr/share/locale/en_GB/LC_MESSAGES/callforwarding.mo

Now my question is where did this "8fbde587a6965bbaf5e8e301a4d80589" come from?

Silly question yep, but i want to know
 
MohammadAG's Avatar
Posts: 2,473 | Thanked: 12,265 times | Joined on Oct 2009 @ Jerusalem, PS/IL
#2
dh_md5sums in debian/rules, build section
 

The Following User Says Thank You to MohammadAG For This Useful Post:
Chrome's Avatar
Posts: 349 | Thanked: 309 times | Joined on Feb 2010 @ PS/IL
#3
Hey mohammad..

You added this next to the arabic.po in case you remember: "597cac6d8767652a31ae21e67deaccce"

597cac6d8767652a31ae21e67deaccce usr/share/locale/ar_SA/LC_MESSAGES/callforwarding.mo

Where did you get it from ... :P
 
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#4
The build script uses a binary, often md5sum, to calculate the MD5 hash of the different files that are in the package.

MD5 hashes is a cryptographical way of ensuring that the file has not changed when you install it. If you Google for "MD5 RFC" you'll find the algorithm that is used.
 

The Following User Says Thank You to Joorin For This Useful Post:
Chrome's Avatar
Posts: 349 | Thanked: 309 times | Joined on Feb 2010 @ PS/IL
#5
Originally Posted by Joorin View Post
The build script uses a binary, often md5sum, to calculate the MD5 hash of the different files that are in the package.

MD5 hashes is a cryptographical way of ensuring that the file has not changed when you install it. If you Google for "MD5 RFC" you'll find the algorithm that is used.
Alright let's say i added an extra .po (locale file) to a package, now i have to add something like this in the md5sums:

PHP Code:
f8fb0a67cf671dc00bfff47160e6991b  usr/share/locale/pl_PL/LC_MESSAGES/callforwarding.mo
5a0179031e2681c3e64fb411ba80924a  usr
/share/locale/fi_FI/LC_MESSAGES/callforwarding.mo
597cac6d8767652a31ae21e67deaccce  usr
/share/locale/ar_SA/LC_MESSAGES/callforwarding.mo
8fbde587a6965bbaf5e8e301a4d80589  usr
/share/locale/en_GB/LC_MESSAGES/callforwarding.mo 
Where do people get the hashes from? hopefully i'll get the answer if i search for "MD5 RFC".
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#6
?

You don't have to add anything. dh_md5sums calculates the MD5 sums for all the files in debian/<binary package 1, 2,...> automatically, as part of the binary target in rules.

Hell, even the md5sums file itself is optional. Tools like debsums check a package's md5sums file to see if any installed files have been modified compared to the ones in the package.
 

The Following 2 Users Say Thank You to qwerty12 For This Useful Post:
Chrome's Avatar
Posts: 349 | Thanked: 309 times | Joined on Feb 2010 @ PS/IL
#7
Ok, let's say i opened a package, added the extra locale files beside other locales and then repackaged it.

Will that work for getting a specific app to support my language?
 
Reply


 
Forum Jump


All times are GMT. The time now is 19:21.