Re: RFS: blacs-pvm (updated package)
On (29/09/06 22:13), Muammar Wadih El Khatib Rodriguez wrote:
Hi James,
On 9/26/06, James Westby [EMAIL PROTECTED] wrote:
* Please drop the use of ${Source-Version}, see
http://lists.debian.org/debian-mentors/2006/09/msg00228.html
I read all the thread including [1] and [2]. I think the part of the
code that you mentioned above is into control file. I did tests and I
didn't have success when I changed Source by binary.
It should work, note that the field is ${binary:Version} with a colon
now.
I was reading the
code of one package that you maintain [libksba] and you use
${Source-Version} instead of ${source-Version} which is the correct
form :S Well, If we are talking about that variable into control file.
Yes, I do not practice what I preach.
This package is involved in an important dependency chain (indeed a
Priority: Important chain), so it was decided to keep the old variable
to make backports easier. We will probably change post-etch to the new
variable though.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: blacs-pvm (updated package)
Hi James,
On 9/30/06, James Westby [EMAIL PROTECTED] wrote:
On (29/09/06 22:13), Muammar Wadih El Khatib Rodriguez wrote:
Hi James,
On 9/26/06, James Westby [EMAIL PROTECTED] wrote:
* Please drop the use of ${Source-Version}, see
http://lists.debian.org/debian-mentors/2006/09/msg00228.html
I read all the thread including [1] and [2]. I think the part of the
code that you mentioned above is into control file. I did tests and I
didn't have success when I changed Source by binary.
It should work, note that the field is ${binary:Version} with a colon
now.
I'm going to try again, because I want to improve the packages which I maintain.
I was reading the
code of one package that you maintain [libksba] and you use
${Source-Version} instead of ${source-Version} which is the correct
form :S Well, If we are talking about that variable into control file.
Yes, I do not practice what I preach.
This package is involved in an important dependency chain (indeed a
Priority: Important chain), so it was decided to keep the old variable
to make backports easier. We will probably change post-etch to the new
variable though.
My comment was because for doing my watch file I followed your
packages like examples, you know, for having an idea. And I read the
USCAN's man page [0], too.
Thanks :-)
Regards,
[0] http://dehs.alioth.debian.org/uscan.html
--
Muammar El Khatib.
Linux user: 403107.
Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1
http://muammarelkhatib.net | http://www.teorex.org
,''`.
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: blacs-pvm (updated package)
Hi James,
On 9/26/06, James Westby [EMAIL PROTECTED] wrote:
On (25/09/06 20:53), Muammar Wadih El Khatib Rodriguez wrote:
Dear mentors,
I am looking for a sponsor for the new version 1.1-17
of my package blacs-pvm.
Hi,
I cannot sponsor, but I have some comments for you.
* Should the package names be prefixed with lib?
Well, If you get lintian warnings about it so the package names should
be prefixed with lib. I know that I'm getting those warnings.But, What
about the dependencies? I'll research if dependencies problems happen
when the blacs' package names are changed. I think at least
scalapack's dependencies should break.
* blacs1-pvm.postinst is useless, as that will be added by
dh_makeshlibs
You are right. I made a test. I erased the file blacs1-pvm.postins and
dh_makeshlibs created this file like I read in the online manual [0]
So, Done :-)
* Please drop the use of ${Source-Version}, see
http://lists.debian.org/debian-mentors/2006/09/msg00228.html
I read all the thread including [1] and [2]. I think the part of the
code that you mentioned above is into control file. I did tests and I
didn't have success when I changed Source by binary. I was reading the
code of one package that you maintain [libksba] and you use
${Source-Version} instead of ${source-Version} which is the correct
form :S Well, If we are talking about that variable into control file.
* The short descriptions are all lacking in my opinion
Basic Linear Algebra Comm. Subprograms - Dev. files for PVM
doesn't give much indication of what the package is for.
* The convention is to indent Homepage: by two spaces, see
I read the reference, and I could see that changelog file of blacs
does not have problems with:
6.2.4 Upstream home page
* It would be good if the license informtion could be included in the
package itself. At any rate I think it would help to make it clearer
what is going on the the debian/copyright file. You should state
that you enquired by email and got that response.
Also there is no copyright information in that file, there is only
license information wrongly labelled as copyright information. See
http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
* Why do you clean at the start of all your build targets? That is
what the clean target is for, and is messy.
I agree. I'm fixing it.
* Please add a watch file.
Done.
* There is an important linda warning
W: blacs1-pvm; The library libblacs is not in a shlibs file.
I'm working on it.
Thanks for your mail, I learned a lot :-)
[0] http://www.fifi.org/cgi-bin/man2html/usr/share/man/man1/dh_makeshlibs.1.gz
[1] http://wiki.debian.org/binNMU
[2] http://wiki.debian.org/NonMaintainerUpload
--
Muammar El Khatib.
Linux user: 403107.
Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1
http://muammarelkhatib.net | http://www.teorex.org
,''`.
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: blacs-pvm (updated package)
On 9/26/06, James Westby [EMAIL PROTECTED] wrote: On (25/09/06 20:53), Muammar Wadih El Khatib Rodriguez wrote: Dear mentors, * It would be good if the license informtion could be included in the package itself. At any rate I think it would help to make it clearer what is going on the the debian/copyright file. You should state that you enquired by email and got that response. Also there is no copyright information in that file, there is only license information wrongly labelled as copyright information. See http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html I forgot to say I'm fixing this part, too. Thanks for reading. -- Muammar El Khatib. Linux user: 403107. Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1 http://muammarelkhatib.net | http://www.teorex.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: blacs-pvm (updated package)
On (25/09/06 20:53), Muammar Wadih El Khatib Rodriguez wrote:
Dear mentors,
I am looking for a sponsor for the new version 1.1-17
of my package blacs-pvm.
Hi,
I cannot sponsor, but I have some comments for you.
* Should the package names be prefixed with lib?
* blacs1-pvm.postinst is useless, as that will be added by
dh_makeshlibs
* Please drop the use of ${Source-Version}, see
http://lists.debian.org/debian-mentors/2006/09/msg00228.html
* The short descriptions are all lacking in my opinion
Basic Linear Algebra Comm. Subprograms - Dev. files for PVM
doesn't give much indication of what the package is for.
* The convention is to indent Homepage: by two spaces, see
http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-upstream-info
* It would be good if the license informtion could be included in the
package itself. At any rate I think it would help to make it clearer
what is going on the the debian/copyright file. You should state
that you enquired by email and got that response.
Also there is no copyright information in that file, there is only
license information wrongly labelled as copyright information. See
http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
* Why do you clean at the start of all your build targets? That is
what the clean target is for, and is messy.
* Please add a watch file.
* There is an important linda warning
W: blacs1-pvm; The library libblacs is not in a shlibs file.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: blacs-pvm (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.1-17 of my package blacs-pvm. It builds these binary packages: blacs-pvm-dev - Basic Linear Algebra Comm. Subprograms - Dev. files for PVM blacs-pvm-test - Basic Linear Algebra Comm. Subprograms - Test files for PVM blacs1-pvm - Basic Linear Algebra Comm. Subprograms - Shared libs. for PVM The package is lintian clean. The upload would fix these bugs: 335009 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/blacs-pvm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/blacs-pvm/blacs-pvm_1.1-17.dsc I would be glad if someone uploaded this package for me. Thanks for reading and regards, -- Muammar El Khatib. Linux user: 403107. Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1 http://muammarelkhatib.net | http://www.teorex.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
