Package: rpvm
Severity: serious
Version: 0.6.2-1
Please refer to the buildd log at the URL listed below.
http://buildd.debian.org/fetch.php?&pkg=rpvm&ver=0.6.2-1&arch=ia64&stamp=1090993499&file=log&as=raw
config.status: creating src/Makevars
config.status: creating inst/pvmhosts
** libs
make[1]: Entering directory `/build/buildd/rpvm-0.6.2/src'
Makevars:3: /usr/lib/pvm3/conf/LINUXRR64.def: No such file or directory
(Or may not, but that is the next bug report re -fPIC which fails, once
again due to pvm, which mixes static and shared libs -- a serious Policy violation.)
On Thu, Aug 19, 2004 at 04:21:49PM -0500, Dirk Eddelbuettel wrote:
(Or may not, but that is the next bug report re -fPIC which fails, once again due to pvm, which mixes static and shared libs -- a serious Policy violation.)
Please see bug #226762 for any discussion on this. (Basically, I do not consider it a policy violation, and would not reconsider this unless
somebody actually entered with new arguments, or the ctte say otherwise.)
What is so difficult to comprehend about the Policy line of 'each library package must provide shared libraries' ?
[Please keep this discussion on #266762]
On Thu, Aug 19, 2004 at 04:33:12PM -0500, Dirk Eddelbuettel wrote:
What is so difficult to comprehend about the Policy line of 'each library package must provide shared libraries' ?
What is no difficult to comprehend about the Policy line of "explicitly not intended by upstream"?
What is no difficult to comprehend about the Policy line of "explicitly not >> intended by upstream"?Irrelevant. If it can't be packaged to Policy, what does it do in the archive.
On Fri, Aug 20, 2004 at 12:46:49AM +0200, Steinar H. Gunderson wrote:
On Thu, Aug 19, 2004 at 05:43:09PM -0500, Dirk Eddelbuettel wrote:
What is no difficult to comprehend about the Policy line of "explicitly notIrrelevant. If it can't be packaged to Policy, what does it do in the archive.
intended by upstream"?
It is packaged to policy, see section 8.3:
In some cases, it is acceptable for a library to be available in static form
only; these cases include:
[...]
* libraries which are explicitly intended to be available only in static
form by their upstream author(s)
Err, which part of 'in static only' suggests you mix static and shared?
--
Those are my principles, and if you don't like them... well, I have others.
-- Groucho Marx
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 42:02:03 |
| Calls: | 12,109 |
| Files: | 15,006 |
| Messages: | 6,518,416 |