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 the place to note the provenance and licensing of the source.
--
Russ Allbery ([EMAIL PROTECTED
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 subject of unsubscribe. Trouble
.
--
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 PROTECTED]) http
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]
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.
Does it make sense to have six different packages
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't end up needing some sort of patch
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 like that?
No, they're unrelated.
I guess you mean
.
--
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/pkg instead.
--
Russ Allbery ([EMAIL PROTECTED
, 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://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
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]
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 Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
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
is broken at several different levels
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.debian.org only checks i386.
--
Russ Allbery ([EMAIL
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 a lot of
software in this category.)
--
Russ Allbery ([EMAIL
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 version is permissable or whether the or
later
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 time I built them. It's
now Sid ;-)
You can also pin lintian
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.
We probably don't really want to include a copy of the GPLv1
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 don't know of any packages that say
) and will be fixed in a later
version.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
and submit
that as a bug against debian-policy, that would be greatly appreciated and
would start the process of including it in Policy.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
to accept such packages in the
archive. If so, we should change 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]
contractors. It
depends on the terms of the contract. But if they say that the contract
didn't assign copyright to the contractor in this case, it's reasonable to
believe them.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
says to run ldconfig when installing libraries into
the default search path.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
they in /usr/lib?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, but the
wording is buggy. I expect upstream really intends something more like
the license Automake uses.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the same symbols even if it was -1~bpo.40 or -0.1 or
something strange.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to change the
library package name to not include an underscore since underscore isn't
allowed in package names in Debian. The recommendation (which will make
lintian happy) is to replace _ with - in the package name.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
to fix it for hours
but someone point me at a bug that makes this empty usr/lib/
FTR: #452227.
Let me know if python-central decides to keep the empty directories and I
can add an exception to lintian. This tag is fairly new and still needs
more exceptions added to it.
--
Russ Allbery ([EMAIL
libpoco.so.2.
It is a place where an override is probably justified, however.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Guidelines.) So
the practical impact for a Debian derivative of including or not including
one more package with the four-clause BSD license is minimal.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
package with this license would not cause
any noticable hardship for redistributors compared to what they already
would need to deal with.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
assumed the BSD license as referred
to in the DFSG must, regardless of what the web site currently links to,
actually refer to the 4-clause license since that's the only thing that
existed at the time.
Am I missing something?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
Charles Plessy [EMAIL PROTECTED] writes:
Le Wed, Feb 06, 2008 at 10:27:55PM -0800, Russ Allbery a écrit :
Am I missing something?
This ?
http://web.archive.org/web/19990210065944/http://www.debian.org/misc/bsd.license
http://web.archive.org/web/20001205083200/http://www.debian.org/misc
/doc at all. You
should ship them in /usr/share/package and add a symlink in
/usr/share/doc if desired.
See Policy 12.3.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
the files is fairly common
right now.
See http://bugs.debian.org/397939 for some additional discussion.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Székelyi Szabolcs [EMAIL PROTECTED] writes:
What's the usual way of handling preX upstream version numbers in
watch files? I'm having trouble because uscan considers 1.0pre3 newer
than 1.0.
opts=uversionmangle=s/pre/~pre/
--
Russ Allbery ([EMAIL PROTECTED]) http
-running autoconf and automake would increase the number of
FTBFS's that we'd need to fix. (Probably for the greater good of free
software, but.)
Also, it's not always easy to figure out which files are generated in
order to remove them, but that's probably programmatically fixable.
--
Russ Allbery
Bas Wijnen [EMAIL PROTECTED] writes:
On Mon, Feb 11, 2008 at 09:21:29AM -0800, Russ Allbery wrote:
Always re-running autoconf and automake would increase the number of
FTBFS's that we'd need to fix.
Not really.
No, really, I promise it will. :) Each time we upgrade autoconf, it will
break
generation is done is already done as
part of the installation of libtool.
It's not like Autoconf or Automake where a file in the source is used as
input to a compiler which generates a shell script based on it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
Clint Adams [EMAIL PROTECTED] writes:
On Thu, Feb 14, 2008 at 04:02:41PM -0800, Russ Allbery wrote:
Note that libtool is an unusual case here and isn't the same as
Autoconf or Automake. The files included in the package (libtool.m4
and ltmain.sh) are not generated files in the same sense
with the current autotools, the partial run of Automake can
leave the whole tree in a broken state, and so forth.
But I suppose that's basically the normal argument for AM_MAINTAINER_MODE.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
/main Packages
100 /var/lib/dpkg/status
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. For example, should you declare
the programs it needs in Build-Depends? I don't think so, and it would
feel weird to me to do so, but as a result I use software in
get-orig-source for which there's no hint in the source package control
file might be needed (wget is the most common).
--
Russ Allbery
by a person. But I don't think
you need to file a bug for this case.
You need to file a bug if you drop a package from only some architectures
that previously had that package, but if you stop building a binary
package entirely, that's caught by the audit scripts.
--
Russ Allbery ([EMAIL PROTECTED
Free Desktop specifications right now anyway
(since tons and tons of .desktop files use Applications, which also isn't
valid).
If you can tell me the list of categories on which you've agreed, I'll add
them to lintian.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
suggestions/pointers?
Usually, but not always, this means upstream is using an outdated libtool.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
library files,
this is common enough practice with Python that the next release of
lintian will ignore it. So you can also leave it alone and the warning
will go away with the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
debian/rules file. You have
to run dh_makeshlibs when building shared libraries. Otherwise, you don't
get a shlibs file, which means that the shared library package won't work
right and dh_shlibdeps can't find it when setting shared library
dependencies.
--
Russ Allbery ([EMAIL PROTECTED
this
to fail. However, lots and lots and lots of stuff does work this way and
usually doesn't cause problems.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the package was
built. You have to edit the *.changes file after the build if you want to
target a different distribution than the debian/changelog entry indicates.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
to in this sentence.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
architectures isn't treating you like shit; it
really isn't personal.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-with-openssl
If you add the exception from upstream to the copyright file and it uses
one of the standard wordings that talks about an exception or exemption,
lintian will figure it out for itself without needing an override.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
of that VCS data.
Is this some additional VCS that the default dpkg-source regex should be
changed to also handle? Excluding any VCS files seems to be the goal of
the regex and I expect the maintainers would not be adverse to adding
another one.
--
Russ Allbery ([EMAIL PROTECTED]) http
.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
know if it's worth being more formal here in Policy or not. It
might be more of a devref thing.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
codenames and indeed
maintainer names are there only for humans to read.
This is not *completely* true; lintian parses the changelog for certain
words and conventions and will whine if you don't follow them. But
lintian tends to be a weird special case about some of these things.
--
Russ Allbery
can still look at the openafs package, which is
currently using quilt and applies a whole bunch of patches (although we
may switch to Git at some point down the road).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Paul Johnson [EMAIL PROTECTED] writes:
On Sat, May 31, 2008 at 9:59 PM, Russ Allbery [EMAIL PROTECTED] wrote:
At this point, I've converted most of my packages to use Git, which
means that the source package as uploaded to Debian has one collapsed
patch including upstream changes and you have
format will address this, or that
otherwise one of the people who are talking about doing this with their
packages will write up a good set of tools to let me do this easily, so
that I don't have to do the work of writing such a tool.
--
Russ Allbery ([EMAIL PROTECTED]) http
George Danchev [EMAIL PROTECTED] writes:
On Sunday 01 June 2008, Russ Allbery wrote:
I'm currently not doing this for a very prosaic reason: I don't have a
simple tool that does it for me, and I'm too busy with other things to
write one. The choice was to stay with quilt or to give this up
Vincent Bernat [EMAIL PROTECTED] writes:
This is a bit odd to have a package depends on xfonts-75dpi. Do you know
the rationale behind this dependency?
It's also a Policy violation. See Policy 11.8.5, first point, last
sentence.
--
Russ Allbery ([EMAIL PROTECTED]) http
in the description is rare, but there are
cases where you want to do it.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
library that's a full
shared library in its own right because building with debugging changes
the library, then yes, you'll need to override a warning about the package
name. But it should be in /usr/lib.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
in the same package, which
happens to be a debugging build of another shared library.
If the package contained only detached debugging information, Lintian
wouldn't be confused.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
that a library named
libkrb5.so.3 should result in a package name of libkrb5-3 and not
libkrb53. It therefore only matches library names that end in a number.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
. You don't really want the build to change depending on
whether or not someone happens to have autotools-dev installed.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
the
*university* license, while ours refers to the real authors.
You're correct. You can only use /usr/share/common-licenses/BSD for code
that's actually owned by the Regents of the University of California, not
for other code licensed under the same license.
--
Russ Allbery ([EMAIL PROTECTED
automatically (standard in the sense that every
time I need to figure out what they are, I have to go grovelling through
arcane compiler flags or obscure documentation).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
of this
for you too. :)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
William Vera [EMAIL PROTECTED] writes:
But I don't know yet how to fix those lintian warnings :/
For each line identified by lintian, look at all the dashes (-) on that
line. If any of them are literal - characters, usually for program
options, put a \ in front of them.
--
Russ Allbery
before the build, you need to delete all the files
modified by that build process in debian/rules clean so that those
spurious changes aren't included in the Debian diff.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
to the
global Apache configuration.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of convenience and because they have
well-known and non-problematic licenses. Since we're distributing them,
to be fully and formally correct, we should probably document the license
status. (Not that I expect many people to go to the effort, but I do do
so when I have time for my packages.)
--
Russ Allbery
Stefan Fritsch [EMAIL PROTECTED] writes:
On Sunday 06 July 2008, Russ Allbery wrote:
That would really upset me if I were a systems administrator. Most of
my Apache configurations have multiple virtual hosts, and having some
package randomly add itself to the namespace of every virtual host
represent some sort of meaningful to-do list
for the Debian maintainer. Including things on that list that aren't
actionable works against that purpose.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
should provide the full path of the target file to dh_link. dh_link
will then do whatever is necessary to make it a Policy-compliant link. So
if you're linking to a file in /usr/share/package, the source should
start with that.
--
Russ Allbery ([EMAIL PROTECTED]) http
Julien Cristau [EMAIL PROTECTED] writes:
On Sun, Jul 13, 2008 at 22:13:27 -0700, Russ Allbery wrote:
[EMAIL PROTECTED] writes:
3) Even if mkfontdir were invoked directly or if it's okay to give
update-fonts-dir an absolute path (in which case its man page needs to
be updated and the warning
Julien Cristau [EMAIL PROTECTED] writes:
Maybe HOME was still set to the user's home dir? If XAUTHORITY isn't
set Xlib looks in $HOME/.Xauthority, so that may work depending how you
get root.
Ah, XAUTHORITY was set. Thank you. I didn't know about that.
--
Russ Allbery ([EMAIL PROTECTED
of confusion lately.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is being used as an adjective, which
conventionally means that you hyphenate the entire phrase.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to be able to install (in practice, old enough that it's
supported in stable), but there's really no reason not to use the more
accurate and informative dependency.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
there was an oldstable
(or even just stable) version that didn't support what I needed, but with
debhelper it's just so easy to always version it for consistency.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
empty directories in /var. I suspect that
your empty directories (particularly cache) may be in the wrong place
according to the FHS for what the package will put in them.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
could be removed.
The Lintian warning frequently catches scripts that were supposed to be
executable but don't have correct permissions, as Joey says. There are
already exceptions in Lintian for libraries for some scripting languages.
--
Russ Allbery ([EMAIL PROTECTED]) http
. Then move all
the other tags and branches to the new commits, and git gc should remove
the unreachable objects.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
-data).
That would imply that Lintian's threshold for this warning is too low.
What do other people think?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
reason.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
broken (you have the same block in both diffs).
Please re-upload without those changes and I'll be happy to upload this
NMU given that the maintainer is listed in LowNMU.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
Standard Debian packaging practices don't let you do this sort of thing
and require a hand-maintained changelog file with hand-written new entries
for each new version. The standard packaging tools like debuild therefore
are not prepared to deal with this and probably are not going to cope.
--
Russ
or not I'd bother would probably depend on the package.
Is there something useful (some tricks) to know about it? Something to
easy SVN management and it's not written in howto?
http://svnbook.red-bean.com/ is incredibly useful for all the general
Subversion stuff.
--
Russ Allbery ([EMAIL
,
the answer is run dh_strip and it takes care of this for you. However,
it's good to understand the basics and the reasons for what's going on
behind the scenes.
There's some additional information in section 10.1 of Policy.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256900
Yeah, Objective CAML has been that way for years and years.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
101 - 200 of 690 matches
Mail list logo
