> So please, please, please do fix (remove) the rpath in the package.
I would appreciate any tips on how to go about fixing this. My package
is courierpassd, currently only available in unstable. It depends on
courier-authlib which currently uses /usr/lib/courier-authlib. I can't
figure out how to
> In almost any situation rpath is a bad thing. It is a very good idea to let
> lintian check this. A "private" library for the package is an exception. Of
> course lintian could also check and allow /usr/lib/$packagename without a
> warning. However, the rpath check is useful in general, becau
> > So is the lintian test wrong? Should it only be checking for rpaths that
> > aren't system directories?
>
> good question!
I finally found some pseudo-official documentation on this:
http://wiki.debian.org/RpathIssue
which confirms what you said:
"Currently, the only valid use of thi
> > > Depends. Does it actually fix the warning?
> >
> > Yes, but it also broke my binary, which can no longer find the needed
> > library. Any suggestions? Is rpath okay in this case? The needed library
> > is coming from /usr/lib/courier-authlib.
>
> In this case, I believe it is correct. rpath
> I've looked for this kind of answer before - it's not as simple as it
> appears. rpath arises from libraries in non-standard locations, either
> alone or when linked to a binary.
>
> 1. Dependencies can bring in rpath: See Bug # 374797 (amd64 specific)
> 2. linking binaries against pkglib_LTLIBR
Hi,
A package I am creating from scratch is giving me the lintian warning
binary-or-shlib-defines-rpath. lintian-info in turn tells me "Please
contact debian-devel@lists.debian.org if you have questions about this."
My search revealed two possible solutions: 'configure --disable-rpath'
where supp
Can I ask again if anyone is interested in checking and sponsoring
courierpassd?
thanks,
Charles
-Original Message-
> From: Charles Fry <[EMAIL PROTECTED]>
> Subject: Re: RFS: courierpassd
> Date: Sat, 27 May 2006 00:57:58 -0400
> To: debian-mentor
> > courierpassd is a utility for changing a user's password from across a
> > network. It uses the same protocol as poppassd to obtain user IDs and
> > passwords. This can be used, for example, to allow users to change
> > their passwords from within various webmail programs.
> >
> Are you aw
* Package name: courierpassd
Version : 1.1.0
Upstream Author : Andrew St. Jean <[EMAIL PROTECTED]>
* URL : http://www.arda.homeunix.net/store/
* License : GPL
Description : Change courier user passwords using poppassd interface
courierpassd is a utility f
Hi,
I adopted wmfire earlier this month, and now have a new upstream release
packaged and ready for upload. My original sponsor is busy at Berkeley,
so I wondered if anyone here might be interested in sponsoring wmfire?
License: GPL
Short Description: very cool fiery way of showing your C
Source: bouncycastle
Section: libs
Priority: optional
Maintainer: Charles Fry <[EMAIL PROTECTED]>
Build-Depends-Indep: debhelper (>= 4.0.0), free-java-sdk, libgnumail-java,
gjdoc, junit
Standards-Version: 3.6.2
Package: libbcprov-java
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
Hi,
I am currently in the process of packaging Bouncy Castle, my first
multiple binary package. I ran dh_make to create an initial
debianization of the package, and now have encountered the following
problem when building my package:
dh_clean -k -i
dh_clean: I have no package to build
Al
Hi,
I have started work on packaging the Bouncy Castle Crypto libraries
for Java (bug #234048). I think I have most everything in place for a
first stab, but I can't figure out where to put the signed jar so that
dpkg-buildpackage won't complain.
Basically, the source of the Bouncy Castle Crypto
Hi,
I have started work on packaging the Bouncy Castle Crypto libraries
for Java (bug #234048). I think I have most everything in place for a
first stab, but I can't figure out where to put the signed jar so that
dpkg-buildpackage won't complain.
Basically, the source of the Bouncy Castle Crypto
14 matches
Mail list logo
