be willing to sponsor it with those
changes.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
KPAO nor KSJC appear to work, for instance.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/build-tools.html
has some additional details for how I do this personally.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Tyler MacDonald [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] wrote:
The general rule of thumb is that if there is any intention whatsoever
that the package be used on a platform other than Debian, the Debian
packaging and the upstream source should be separate.
Okay, so
Jeremy Stanley [EMAIL PROTECTED] writes:
On Sun, Apr 23, 2006 at 07:35:29PM -0700, Russ Allbery wrote:
The reference to /usr/share/common-licenses/BSD is not really correct
since your software is not Copyright The Regents of the University of
California. I'd remove that and just put the full
, as the Debian apxs2 should not
be doing this. But I haven't looked at your package rules to see how
you're building the shared library.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
Tyler MacDonald [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] wrote:
W: libapache2-mod-bt: binary-or-shlib-defines-rpath
./usr/lib/apache2/modules/mod_bt.so /usr/local/lib
It's not clear where this is coming from, as the Debian apxs2 should
not be doing this. But I haven't
Tyler MacDonald [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] wrote:
However, if $CFG_LIBEXECDIR in your build is /usr/local/lib, that's
probably a problem. In general, the string /usr/local should not
appear anywhere in your build for Debian packages.
It doesn't, and apxs2's
. It's very difficult to implement that check even at the 80%
level and to implement it fully correctly requires knowledge about the
global state of the repository that's hard to come by.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
information, for instance, I believe embeds the name of the
build directory.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
post, wouldn't information about how a
non-pristine sourceball is repacked belong in debian/copyright? That's
certainly where I've always put it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
identical? I don't think I'm following what you're
getting at with the above or why editing of the .diff.gz would be
required.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Andreas Barth [EMAIL PROTECTED] writes:
* Russ Allbery ([EMAIL PROTECTED]) [060429 05:50]:
4. should use packagename-upstream-version.orig as the name of the
top-level directory in its tarball. This makes it possible to
distinguish pristine tarballs from repackaged ones
out of the Debian archive so that I don't
have to worry about it changing.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
George Danchev [EMAIL PROTECTED] writes:
On Saturday 29 April 2006 21:34, Russ Allbery wrote:
After I've done one upload with a particular upstream source, I usually
just pull the upstream source out of the Debian archive so that I don't
have to worry about it changing.
What about random
George Danchev [EMAIL PROTECTED] writes:
On Saturday 29 April 2006 22:06, Russ Allbery wrote:
George Danchev [EMAIL PROTECTED] writes:
On Saturday 29 April 2006 21:34, Russ Allbery wrote:
After I've done one upload with a particular upstream source, I usually
just pull the upstream source
representation (the
results of the automation).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
George Danchev [EMAIL PROTECTED] writes:
On Sunday 30 April 2006 10:05, Russ Allbery wrote:
Well, discussing it is exactly what I'm doing right now. :) Obviously
if I can't convince anyone here, there's no point in filing a bug
against the Developer's Reference for a change that has
Bart Martens [EMAIL PROTECTED] writes:
On Sun, Apr 30, 2006 at 12:05:19AM -0700, Russ Allbery wrote:
One advantage of insisting on a get-orig-source target
Do you insist on a get-orig-source target while sponsoring? It's
currently optional according to the debian-policy.
http
George Danchev [EMAIL PROTECTED] writes:
On Sunday 30 April 2006 21:37, Russ Allbery wrote:
I don't find get-orig-source as useful for normal packages that don't
require repackaging of upstream source. In that case, for the most
part, I don't think it's worth the effort.
Nobody says
with the DevRef. I think this package is
just part of why that's should and not must, the distinction being that
shoulds are rules that one may occasionally have reason to not follow.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
repackaged, I think such a thing would need to be
hand-crafted, and in other cases it's not clear to me how generally useful
it is. If the maintainer wants to write one, great, but I, for instance,
usually download new upstream source in a way that it doesn't make much
sense to automate.
--
Russ
sure.
--
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 the package since previous versions, for
example.
Hm, are you confusing README.Debian with NEWS.Debian, maybe? I think of
README.Debian as regular documentation.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
people to remove
the commented-out lines.
See http://ftp-master.debian.org/REJECT-FAQ.html down near the bottom
near debian/rules.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
to duplicate a fair amount of the parser logic of a Bourne
shell so that one could tell when one was processing a command, its
arguments, or something else. But it would be lovely to have this, and
there are a lot of checks that could be done much more thoroughly and
reliably with this logic.
--
Russ
.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Space separated list of filenames or shell globs representing
the files which constitute the documentation in this format.
Required field.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
wrapped fields?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [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]
package in my personal repository:
deb http://archives.eyrie.org/debian unstable main
It's going to be included in Subversion proper in their tools section in a
future release, after which it will show up in the regular Debian
Subversion packages.
--
Russ Allbery ([EMAIL PROTECTED
packages till now. I'm filing a bug
against the developer's reference that this section be changed to not
recommend the space in front.
The space is necessary; it tells package front-ends to not wrap the line.
See Policy 5.6.13.
--
Russ Allbery ([EMAIL PROTECTED]) http
, since people won't even
agree on and follow the syntax for the hack of putting it in the long
description so that people can parse it properly. *sigh*
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
are like my personal packages where the maintainer added it
pretty much just because it was in the devref and has no strong opinions
about whether it's useful or not.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
, you should be in Uploaders.
In practice, I agree with...
In the end, I think that it is safe to think the Uploaders field as a
Co-maintainers field. This is also how it is presented in
packages.qa.debian.org...
...this.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
of really obnoxious problems like causing
sub-proceses run by that process to potentially get the wrong libraries.
It's too large of a lever.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
. I'll try to investigate
that further.
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. Committing a fix now.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
not sure it's a good idea; it may add more
problems than it catches in the long run.
It's *great* for development, of course.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
of the changelog
with each binary package isn't large.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
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. Committing a fix now.
Thanks for your
.)
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.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
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 unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
, 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 to [EMAIL PROTECTED]
with a subject of unsubscribe
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, etc.)
--
Russ Allbery ([EMAIL PROTECTED]) http
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. This way packages end up in libs they
don't include
the latest changes to version
control.
Yup, you can do this from inside your regular working directory, and only
use the above method for building the final packages.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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 [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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]
I think it's already done, because in /usr/share/doc/drapes/ there is
the file NEWS.gz which is the gziped copy of the NEWS file of the
tarball
Sandro was suggesting you install it as changelog.gz rather than
NEWS.gz, but I'm not sure that is necessary.
See Policy 12.7.
--
Russ Allbery
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 unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--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]
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 mean I have to include that fix and ignore
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 [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 this was helpful!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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 forbidden.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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/
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]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
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/
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-buildpackage to
build CDBS-using packages, for instance.
--
Russ Allbery ([EMAIL
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
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 PROTECTED]) http://www.eyrie.org/~eagle
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]) http://www.eyrie.org/~eagle
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]
horribly confused,
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]
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 previous-version+svn-stuff if you're packaging
that version plus some additional upstream modifications, and use
next-version+svn-stuff if you're packaging an alpha or beta arelease
.
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]
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 being treated like
a wishlist bug against developers-reference.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
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 present in that directory?
--
Russ Allbery ([EMAIL PROTECTED
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 is wrong). Are you sure the icon is present
and prompting in
postinst instead of config. For cases where one is intentionally
prompting in postinst on the basis of information that isn't available
before that point, a lintian override is appropriate.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
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's no reason why you can't make it easy.
--
Russ Allbery ([EMAIL
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 sysadmin to do so. For the
FHS reasons
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 to [EMAIL PROTECTED
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 and as
intuitively as quilt.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
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 a feature
--
Russ Allbery
?
Report a bug against lintian. :) Although in this case you don't have
to, as I just fixed it. I caught a few of these with the last upload and
this one will be fixed with the next upload. It needed to be smarter
about the places where *roff uses '-' as part of escapes and commands.
--
Russ
Files: /usr/share/doc/cfi-en/html/*.htm
Files: /usr/share/doc/cfi-en/html/*.html
I think you shouldn't repeat the Files: and instead just list multiple
file specifications on the Files line (which can be continued like a mail
header if need be). Other than that, yes, this is correct.
--
Russ
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.
--
Russ Allbery ([EMAIL PROTECTED
: \
| 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://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
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 subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
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 considered DFSG-free.
Here
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.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
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 preserve copyright statements
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]
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.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
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.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
.
--
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 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 subject of unsubscribe. Trouble? Contact [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]
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
the book is actually under the GFDL and, if so, what if any invariant
.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
201 - 300 of 690 matches
Mail list logo
