George Danchev <[EMAIL PROTECTED]> writes:
> On Saturday 15 July 2006 03:48, Russ Allbery wrote:
>> lintian warns if you do an NMU without mentioning it in the changelog,
>> but although it has the necessary information to do so, it doesn't do
>> the inverse. Com
eats this an error (The
> package contains no changelog.Debian.)
I've cleaned up the handling of changelog files that are symlinks in
lintian for the next release. It was doing a few weird things that
resulted in unhelpful warnings that didn't talk about the actual problem.
ppen
again and can gather some sort of trace information of what it thought it
was doing, that would be great fodder for a bug report.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
erves as useful
documentation for other bug filers to keep from getting duplicate bugs, or
if leaving the bug open and tagged avoids pointless arguments that you'd
have to go through if it were just closed.
If none of those cases apply, I'd just close it.
--
Russ Allbery ([EMAIL PROTECTED
quently just what new users want, and
new users are the ones who frequently won't know to look in some other
section or use apt-cache to search for a separate doc package.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email
7;m
biased since I maintain Pod::Man.) It means a build dependency on Perl,
but the POD syntax is very simple and quick to learn.
man perlpod and man pod2man should get you started. For examples of POD
manual pages, see several of the packages I maintain (remctl, libpam-krb5,
kftgt,
Jörg Sommer <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> wrote:
>> I prefer putting them in the same section as the main package so that
>> people browsing by section in aptitude will actually see them.
> I don't like this philosophie. Th
There is an index that's built
to support man -k, but that index is generally built nightly from cron,
not through an action of the installed package.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
sion control as part of the package build process. A big part
> of (my) testing is attempting a build of the package from the working
> copy of the source, *before* committing the latest changes to version
> control.
Yup, you can do this from inside your regular working directory, and only
use
.
That's what I do, and then I have a script that pulls the latest release,
untars it, checks out the debian directory, and uses pbuilder to build the
final packages.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EM
d line with whitespace.) Policy allows dependency lines
to be wrapped now in the debian/control file.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ngelog.gz rather than
> NEWS.gz, but I'm not sure that is necessary.
See Policy 12.7.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
. :)
Yeah, that's generally what I do as well, and install NEWS as NEWS.gz. So
it sounds like you're doing things the right way.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &quo
builder?
pdebuild --debbuildopts -sa
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
s, I think lintian is at fault here and needs to exclude
files in /var/lib/aspell to this check. So I don't think you need to do
anything in your package.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Mashrab Kuvatov <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> Based on those bugs, I think lintian is at fault here and needs to
>> exclude files in /var/lib/aspell to this check. So I don't think you
>> need to do anything in your package.
> Do you
es/splits/merges.)
...thus making the dependency on the old package an RC bug (eventually),
meaning that omitting dependencies on essential packages *prevents* RC
bugs. :)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [
ser as well.
Ideally, I would do something a bit more complex where the Apache code
hands files off to a separate daemon running as a dedicated user for your
package, which then audits what Apache is trying to do and then puts the
files in an appropriate place with the correct ownership.
Hope th
big issue.
I think you have to distinguish between control-panel software performing
edits at the request of a user, in which case they're just a form of
editor, and control-panel software modifying configuration files for its
own purposes. The latter I think should still be for
e sure we "do
> the right thing fromt eh beginning".
Yeah, info-priority messages are filling this need for right now, and this
one is already info-priority. Eventually this will get better.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
-
they should be compressed with gzip -9. If they're
compressed but don't end in .gz, wouldn't lots of stuff break?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
ut this is
> because, due to the way fakeroot was used, which means that the chgrp
> and chmod commands in your debian/rules did not have any effect.
I suspect dh_fixperms cleaning up after the fact rather than anything
related to fakeroot.
--
Russ Allbery ([EMAIL PROTECTED]) &l
specific reason why they don't have
standard names like all the other info files in /usr/share/info? I
presume that they should actually be called jed.gz, jed-1.gz, jed-2.gz,
and jed-3.gz.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
binary packages in debian/control just right.
> Do those who dislike CDBS also all use dpkg-buildpackage in full or is
> debuild "better" somehow?
You're really comparing apples to kumquats here; CDBS and debuild are
completely unrelated. You can use either debuild or dpkg-b
o. There's a proposed patch that I'm not horribly happy with because I'm
worried that it's too aggressive, and I haven't had a chance to think more
about it and revisit it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
T
l the style check functionality has been added since
they're really more minor even than I:.
In other words, feel free to submit a wishlist lintian bug for things like
this. I'm going to pull up all of those once the style check facility is
available.
--
Russ Allbery ([EMAIL PROTEC
n the format that it likes).
It sometimes does other stuff, like change the line numbers in the po
files (to things that don't look like line numbers) and word-wrap
translations, so you can get unimportant diffs between builds by running
it as part of the build.
--
Russ Allbery ([EMAIL PROTECTED])
e who want him for a sponsor have to do things his
way; people who don't want to do that are certainly no worse off than if
Daniel wasn't sponsoring anything at all.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
onfused,
well, that's what epochs are for.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ave a tool that I use to
do all of this, for which I need to write some documentation so that I can
release it to the world.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Florent Rougon <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> wrote:
>> In other words, use + if you're packaging
>> that version plus some additional upstream modifications, and use
>> + if you're packaging an alpha or beta arelease
>
e CAML binaries.
There's a special exception in lintian for them.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
better to do just do that. The transition issues aren't
difficult when the binaries all come from the same source package, and it
saves a lot of headaches.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Justin Pryzby <[EMAIL PROTECTED]> writes:
> On Mon, Feb 19, 2007 at 05:03:47PM -0800, Russ Allbery wrote:
>> Yes, installing the libraries in /usr/lib.
> For such packages with libraries without sonames, one should just make
> something up?
If the library is not suitable to
ntence or maybe a
paragraph, which is a bit short to warrant a separate file.
I'll open a wishlist bug against developers-reference.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
package and that's the only binary package produced by the netcdf-doc
source package, netcdf-doc will be removed from the archive
semi-automatically without any further action by the maintainer required.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
case, I bet you're looking for dh_installchangelogs
and specifically for passing CHANGELOG.TXT as an argument to it. (This
assumes you're using debhelper; if not, you'll need to do it another way.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle
n. It should be requiring the /usr/share/pixmaps
path now for unqualified icon pathnames.
However, that doesn't explain why you're getting that message, since
lintian does check in /usr/share/pixmaps (even though the long description
of the tag is wrong). Are you sure the icon is p
Michael Rasmussen <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> wrote:
>> However, that doesn't explain why you're getting that message, since
>> lintian does check in /usr/share/pixmaps (even though the long
>> description of the tag i
ng the input causes a lintian warning.
Other people have given you good suggestions, but I did want to mention
that the lintian warning is just because lintian can't easily tell the
difference between valid uses of debconf in postinst and prompting in
postinst instead of config.
/xen (or perhaps /srv/xen) and perhaps provide some
configuration that makes it simple for the sysadmin to do so. For the FHS
reasons, it shouldn't be the default (perhaps the admin is already using
/xen for something completely different), but if the admin *chooses* to
put them there, there&
Thomas Goirand <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> If I were you, I'd document in README.Debian how the administrator can
>> mount the images in /xen (or perhaps /srv/xen) and perhaps provide some
>> configuration that makes it simple for the sy
Magnus Holmgren <[EMAIL PROTECTED]> writes:
> What tools do you prefer for writing manpages (e.g. for commands that
> lack one from upstream)?
I use POD and pod2man.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email t
> utilities as soon as the w&p source format is used.
Even if you don't use quilt to apply the patches at build time, using the
quilt utilities to construct the patches is still a good idea. I've never
seen anything that can manage a set of patches as smoothly
Is there benefit
in retaining them?
There are some fairly fundamental ones there, such as a lot of the
versioned debconf dependencies and the cases where one can't use
debconf-2.0 because features were introduced after that point. But if all
of the stable providers of debconf-2.0 provide
he next upload. It needed to be smarter
about the places where *roff uses '-' as part of escapes and commands.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Files line (which can be continued like a mail
header if need be). Other than that, yes, this is correct.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ip and permissions properly in the package. Debian's
package build process, unlike RPMs, doesn't rely on the spec file to
handle ownership of files. Just chown the files as appropriate in
debian/rules and Debian's package building software will preserve that
ownership.
-
ersion := $(shell dpkg-parsechangelog | grep ^Version: \
| cut -d' ' -f2 | cut -d- -f1)
I'm guessing the problem with the Perl one-liner is that you need to
double the $ in $1 since you're inside make.
--
Russ Allbery ([EMAIL PROTECTED]) <http://ww
censes may not
require citing authors, and in fact many DFSG-free licenses require that
one preserve copyright statements or authorship information.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
on licenses in Debian. The four-clause BSD
license is not a particularly good idea, but I believe it's always been
considered DFSG-free.
Or am I missing some subtlety of your argument?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBS
Russ Allbery <[EMAIL PROTECTED]> writes:
> I believe this is not the interpretation being applied by the
> ftpmasters, who are the final authorities on licenses in Debian. The
> four-clause BSD license is not a particularly good idea, but I believe
> it's always been cons
eference
and either is specifically allowed in Debian Policy. The fourth revision
number is supposed to be only for non-normative changes, and hence the
argument is that it's not useful information for package control files.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie
Matthew Palmer <[EMAIL PROTECTED]> writes:
> On Thu, May 31, 2007 at 06:01:53PM -0700, Russ Allbery wrote:
>> Why? I don't see anything in the DFSG that says that licenses may not
>> require citing authors, and in fact many DFSG-free licenses require
>> that one
sure why GD does that.
Maybe because Xpm support requires linking in X libraries, which makes the
dependency chain heavier?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Can I use it safely for building a package since I can not build-depend
> on it and it does not seem to be contained in an essential package ?
You do need a build-depends since prename is provided by perl, not
perl-base.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyri
that it's only needed to
get prototypes for a few functions that aren't prototyped otherwise. That
would imply that if your software is building without undeclared function
warnings, you don't need it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.o
s much as possible before each upload.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
asks linda
> and lintian differ on.
A lot of people file the bug against one package and then clone it and
reassign the clone to the other.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
o tell if
the package can go in main or non-free.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ricardo Mones <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> wrote:
>> For example:
>>
>> http://www.oreilly.com/catalog/samba2/book/toc.html
>>
>> has the GFDL appended to the book, but I see no explicit statement that
>> t
h editing mechanism
just feels more natural than dpatch's.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
installed on the system for this check to work, so the output of this
check will change depending on what packages you have installed.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in UTF-8, that's great, but a quick test
seems to indicate it still doesn't work even if you run groff -T utf8 in a
UTF-8 locale.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
page for more details.
However, I don't know if this will work for Asian characters. It's the
best solution for European characters, but a quick skim doesn't show a
way to enter an arbitrary UTF-8 code point.
So, not good. :/
It might be worth raising this on debian-devel,
that
groff's handling of multibyte characters needed to be reworked entirely.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d to do this for 2.0, but the work is mostly
stalled.
groff can apparently produce UTF-8 *output*, but I think the encodings of
all of its input at the moment are in other character sets.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE,
can probably make without backward
compatibility issues right now, since currently those code points are
disallowed.
I'd love to see this dealt with for lenny. I just don't know how
realistic that is.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
ve -s from install if upstream puts such things into
makefile variables.
If they don't, you have to patch the Makefile.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pecific Asian encodings and works okay for them, but
possibly not for arbitrary UTF-8. I wonder if that's what Red Hat uses or
if they transcode as well and just lose on man pages that contain
non-European characters.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~
y (I haven't looked at it).
For a one-off module that we put together on a whim, the Perl module has
been amazingly popular, seems to be used all over the place, and is now
included in Perl core, so there's some indication that people really do
like having this sort of functionality.
-
\x{AC00}-\x{D7A3} \x{FF01}-\x{FF60});
but even that is not a particularly good approximation compared to using
the real table.
My guess is that wcwidth's answer is based on the latest version of that
table at the time that glibc released, although I'd have to double-check
to be
> somebody wants to rebuild the archive and find out?
It's a bug that's annoying to try to fix and probably not worth the
effort. make *really* doesn't like spaces in filenames in various
contexts.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~ea
library seems entirely reasonable to me. It is a standard,
and it's not like they change or are system-dependent.
Yes, there are terminals that don't implement those standards. How many
of them are used by anyone other than hobbyists as part of computer
archeology?
--
Russ Allbery ([EMAIL
The Fungi <[EMAIL PROTECTED]> writes:
> On Wed, Aug 15, 2007 at 12:38:07PM -0700, Russ Allbery wrote:
>> Thomas Dickey <[EMAIL PROTECTED]> writes:
>>
>> > (no point in hardcoding "a few dozen string" definitions, unless one
>> > _likes_ the
deo0 -o '
You can ignore these; they'll go away with the next release of Policy.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
f true and sort of not. That code itself is not covered by
copyright, but any derivative work that you create from it is still
covered by your copyright. And that's fine.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n.
I think the only problem may be that the note isn't in the place they
looked. I have a package with a similar problem (openafs-doc) and it was
approved, but I put the note to that effect in debian/copyright, which is
the file that the ftp-masters review for these sorts of issues and which
is t
Kevin Coyner <[EMAIL PROTECTED]> writes:
> what is LP: #96014?
LP numbers are usually Launchpad bugs (in Ubuntu's system).
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
non-free, as it says in the Policy
document. It's a perfectly reasonable question.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ben Finney <[EMAIL PROTECTED]> writes:
> Can you show the location where that's stated?
Did you try searching the table of contents for "non-free" and following
the link? It's section 2.2.3. See also the last sentence of section 2.
--
Russ Allbery ([EMAIL PR
private libraries for the binaries built by this
package rather than trying to use them as first-class shared libraries.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rstand the situation well enough to really recommend
something. How big are each of these packages?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Nikolaus Schulz <[EMAIL PROTECTED]> writes:
> On Mon, Oct 01, 2007 at 05:35:36PM -0700, Russ Allbery wrote:
>> While with non-free software you can't really change the binaries, you
>> definitely *can* change the packaging structure however you'd like.
>> Doe
ame, but I
> could just hard-code the library dependency and be done with it. There
> would be no shlibs file. Again no problem, right?
That's my take, yes.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Nikolaus Schulz <[EMAIL PROTECTED]> writes:
> On Wed, Oct 03, 2007 at 12:57:06AM -0700, Russ Allbery wrote:
>> It would require that you make modifications to the upstream source,
>> probably. So will lots of other things, though. The only packages for
>> which I don
Nikolaus Schulz <[EMAIL PROTECTED]> writes:
> On Wed, Oct 03, 2007 at 11:51:41AM -0700, Russ Allbery wrote:
>> Nikolaus Schulz <[EMAIL PROTECTED]> writes:
>>> Doesn't dumping several upstream tarballs in one Debian source package
>>> require something l
ms for multilib.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Justin Pryzby <[EMAIL PROTECTED]> writes:
> The debhelper tools (dh_install) used to use debian/tmp but now
> (depending on DH_COMPAT) use debian/$package. So this is a small-ish
> lintian bug.
I've changed the lintian message to use debian/ instead.
--
Russ Allbe
rapper, and some time, someone
> will have to proper massbugfil about that..
Could you file a wishlist bug against lintian to add a check for this,
including a rationale for why one shouldn't use gksu or kdesu directly?
--
Russ Allbery ([EMAIL PROTECTED]) <http:/
the whole package in the package documentation,
you can safely assume any unmarked files are also released under that
copyright and license.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ght that are the problem is related to the symlink...
The problem is that libtool doesn't think that lib64 is on the regular
library search path and hence decides that it needs to add rpath, which is
broken at several different levels but best avoided by just using lib.
--
Russ Allb
Francesco Namuri <[EMAIL PROTECTED]> writes:
> Il giorno 04/dic/07, alle ore 01:23, Russ Allbery ha scritto:
>> The problem is that libtool doesn't think that lib64 is on the regular
>> library search path and hence decides that it needs to add rpath, which
>>
"Leo \"costela\" Antunes" <[EMAIL PROTECTED]> writes:
> Are you sure? Check out package 'transmission', it's been using chrpath
> for the last 3 releases (IIRC) without issues on any arch (at least
> according to lintian.debian.org).
lintian.debi
whether only that version is permissable or whether the "or later" part is
available. (The exception is GPL v1, which isn't in common-licenses; in
that case, right now, I think the best course of action is to treat the
software as under GPL v2 for Debian's purposes. There isn't
rwise testing. It's arch: all, so it shouldn't pull in a lot of other
packages.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Matthias Julius <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Agreed. I think debian/copyright should always refer to the exact
>> version of the GPL that the package says it's covered under and then
>> document whether only that
Matthias Julius <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Dave Ewart <[EMAIL PROTECTED]> writes:
>>> Yes, I do run lintian (and linda), but the spare machine I used to
>>> build the packages was running Lenny at the tim
Bas Wijnen <[EMAIL PROTECTED]> writes:
> On Fri, Dec 14, 2007 at 12:04:48PM -0800, Russ Allbery wrote:
>>> I think the best way is to include the license text in
>>> debian/copyright just like any other license that is not in
>>> common-licenses.
>>
Bas Wijnen <[EMAIL PROTECTED]> writes:
> On Fri, Dec 14, 2007 at 06:44:39PM -0800, Russ Allbery wrote:
>> So my original statement that not many packages are in that situation
>> is kind of true and kind of not, depending on how you feel about the
>> Perl situation. (I
201 - 300 of 707 matches
Mail list logo
