Justin Pryzby <[EMAIL PROTECTED]> writes:
> On Sat, Dec 03, 2005 at 09:31:45AM -0800, Russ Allbery wrote:
>> Justin Pryzby <[EMAIL PROTECTED]> writes:
>>> This will only make a symlink if cdrtoaster isn't installed. But is
>>> there a way to make the
n the above has been fixed
and I'll be happy to sponsor the 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]
Jonas Genannt <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> Everything else looks good. Drop me a line when the above has been
>> fixed and I'll be happy to sponsor the upload.
> Ok, I have updated the package.
> Can you please look at the copyright-f
Jonas Genannt <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> I would move his e-mail address up to the same line where you list the
>> upstream maintainer and then replace all of the bit quoted above with
>> the bit I quoted from the COPYRIGHT section of the mo
r whatever good "do nothing" option scons has to make sure it's around.
Incidentally, you shouldn't need the - in front of rm -rf. The -f makes
it exit with a 0 status even if none of the files were found to remove.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie
r/bin/cdrtoaster ]
&& [ "`readlink /usr/bin/cdrtoaster`" = "cdrbq" ] ; then
rm -f /usr/bin/cdrtoaster
fi
You have a stray debian/files in your diff.
Send me e-mail when the above has been addressed and I'll be happy to
upload the package.
--
Russ Al
sure if Marc would agree with me. :)
* The make clean target has:
-$(MAKE) realclean
As previously mentioned, I think:
ifeq (Makefile,$(wildcard Makefile))
$(MAKE) realclean
endif
is cleaner and more reliable.
--
Russ Allbery ([EMAIL PROTECTED])
this version to the previous
version, but looking over the diff, it seems fine to me. Could you fix
the packages on your web site and then send me an e-mail so that I can
take another look? Assuming everything is fine, I'll be happy to upload
it.
--
Russ Allbery ([EMAIL PROTECTED])
KE) realclean
as I mentioned my previous message.
Send me e-mail when you've done the above and I'll be happy to upload the
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]
Russ Allbery <[EMAIL PROTECTED]> writes:
> Could you run $(MAKE) test in debian/rules? I think it's best to do
> that whenever possible just to make sure nothing strange has happened
> and I notice that this package provides a fair number of tests. Also,
> while you'
s the useful work.
> New build depend for #329990
> ITP: #343887
> Debian source and binary package:
> http://jonas.capi2name.de/debian-upload/libpod-tests-perl/
Looks good to me. Uploaded. Same comment about -$(MAKE) realclean when
you have some reason to upload a new vers
-make clean will likely cause a lintian warning/error.
Yeah, I should go provide a patch for that to lintian, since I keep
noticing 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]
Justin Pryzby <[EMAIL PROTECTED]> writes:
> On Sun, Dec 18, 2005 at 01:58:11PM -0800, Russ Allbery wrote:
>> If you do keep it, the postinstall removes cdrtoaster regardless of
>> whether it's a symlink. I think it would be better to do something
>> like:
> s
Jose Manuel dos Santos Calhariz <[EMAIL PROTECTED]> writes:
> The new version is online, and I have made a build test from the online
> files. Everything seams to be fine now.
Looks good to me. Uploaded.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.e
ne
could improve with sponsors/mentors.debian.net, such as the state tracking
that Raphael mentioned earlier or more push notification of things that a
sponsor should be looking at that would fit well into this sort of
framework.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie
ho have compiled software and can work
on Debian packages how to use Subversion, but explaining bzr feels rather
intimidating.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7;t contain any perldoc documentation (which is unusual).
--
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'm still interested.
I need to finish another release of the OpenAFS package, and then I'll
take a look.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Mon, 19 Dec 2005, Russ Allbery wrote:
>> This may not be the most popular opinion, particularly among fans of
>> distributed VCSes (and I do understand the merits), but wrapping your
>> mind around the distr
(>= 1.3.22) | debconf-2.0
> Does anybody know where the problem is?
I wonder if lintian is getting confused by the dependency added by
${misc:Depends} and missing the second dependency that is tighter.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
2.1 or debconf-3.0 as well. If cdebconf implements that
protocol, it can provide that pseudopackage as well.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hangelog entries -- I think you meant debian/copyright as the
file modified, not debian/changelog.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
useful in
the qa.debian.org/developer.php summary.
> I could probably remove it, but just for the future reference, how would
> one fix it? Removing the commented lines, or...?
See the man page for uscan; it explains the format.
--
Russ Allbery ([EMAIL PROTECTED]) <h
cause it create an ISO, but
> it could also write it to a DVD...
> BTW Debian menu is a little beat
There's a discussion going on on debian-policy right now about how to redo
all the menu categories.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~
e
maintainer scripts section would probably be a good idea.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Rogério Brito <[EMAIL PROTECTED]> writes:
> On Dec 25 2005, Russ Allbery wrote:
>> Policy describes the config script in section 3.10.1. A reference in
>> the maintainer scripts section would probably be a good idea.
> Ah, then that would explain it... The copy of t
site. It's referred to in Policy 3.9.1.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
n it's had a 1.0 release and other
packages start depending on it. (The -dev packages should always be
priority extra, though.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jonas Genannt <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> The package looks fine, except that you didn't need to repackage the
>> upstream source. The package build tools don't care in the slightest
>> what directory the upstream source unpacks in
.
(It's particularly satisfying to sponsor adoptions of orphaned packages by
people who are really interested in them. Adding more software to Debian
is nice, but improving the software already in Debian is even better.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie
to sync development cycles with
the other. For the most part, software should easily build in the other,
though, even if the binary packages don't port over.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
have to call dh_installdocs because it's
what installs debian/copyright.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
incorrect, could you talk to the debhelper maintainer about it?
> You would talk to the dh-make maintainer, and not the debhelper
> maintainer.
You may want to talk to them too (I never use dh-make), but take a look at
/usr/share/doc/debhelper/examples/rules and friends.
--
Russ Allbery (
a new .0 release, but that's a
fairly common case.
(I suppose it could work for two-part version numbers too -- 2rc3 before
2.0. But it looks stranger.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ail me in the future any time a new package is available for 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]
ities.
> The xorg, glibc, and samba packages, for instance, are all using quilt
> today.
Oh, interesting. I'd been noticing it in use by large packages, but I
wasn't aware it was at the point where it was a reasonable alternative to
dpatch even for smaller ones. I'll have to
orribly (or worse, break subtlely) on a
given package.
You're probably safe doing this with small packages, but I cringe at the
idea of re-running the autotools automatically on a substantial 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]
t does pretty much
everything properly except package pools.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Sat, 14 Jan 2006, Russ Allbery wrote:
>> The problem is, in a nutshell, this doesn't actually work reliably. If
> It does inside Debian (you can explicitly choose a given version, and
> upgrade to the ne
ball. You can choose between
reporting the bug to upstream and waiting for them to fix it, or reporting
the bug to upstream and also fixing it yourself in the Debian package,
such as by build-depending on the appropriate version of autotools and
running autogen.sh inside your debian/
bly request you to sponsor me for this course. The fees is
> 3,000 us dollars. Shall be grateful for your assistance. My e-mail is
> [EMAIL PROTECTED]
Sorry, I'm afraid this isn't lintian-clean and doesn't build properly in
pbuilder.
--
Russ Allbery ([EMAIL PROTECTED])
e but
rather its presence in the generated binary package. In general, in
Debian, you should never install additional copies of the GPL, the LGPL,
or other common licenses; instead, just refer the user to the copy that
already ships with Debian in /usr/share/common-licenses.
--
Russ Allbery ([E
as easily. Heck, if what
upstream ships there is too annoying, you can always just blow away the
debian directory in your working copy, create your own packaging, and let
diff figure out the transform (although be careful of upstream files that
you need to delete in your version).
--
Russ Allbe
es are a little more straightforward. You may want to give it a
look; I found the manual quite sufficient to get started.
The workflow is substantially different than it is with dpatch, so that
takes a little getting used to, but after I got used to it I actually
liked it better.
--
Russ
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> On Tuesday 24 January 2006 13:23, Russ Allbery wrote:
>> What I would do if I were you would be to make the changes you need to
>> make to the upstream debian directory to have the package work the way
>> that it should
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> On Tuesday 24 January 2006 13:52, Russ Allbery wrote:
>> Why? Do you have to remove some files for DFSG-compliance?
> Sorry, what I meant was my orig.tar.gz ends up being the pre-release
> version, not the official version re
version. This is generally a bad idea
even if you're upstream; it's really not a good idea if you're not
upstream for the package.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Daniel Knabl <[EMAIL PROTECTED]> writes:
> As recommended, I had a discussion about it with the author. Now the
> license has been changed. I think it can be included into
> debian/copyright as follows:
It's fine. There's lots of stuff in Debian with this sort of l
ill use debhelper 4 for all my packages because it makes backporting
to sarge easier. There doesn't seem to be anything in debhelper 5 that
particularly warrants making backporting harder, so I'm planning on
waiting until etch is released to bump the compatibility level.
--
Russ Allbery
m definitely will not make your code portable to all of
those platforms. If the program is non-trivial, you will probably still
have to do some porting.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
27;m much more likely to be able to fix what I need to fix or add
the functionality that I need to add without significant surgery in a
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]
e
/usr/share/doc/kernel-package/README.modules, particularly at the end of
that 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]
the name of the programmer of picprog (Jaakko Hyvätti) so I don't know
> if that is really a good idea?
Replace ä with \[:a]. Upstream may not be able to do this since this is a
groff-specific thing, but it's safe to do in Debian.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
versal among the packaging tools and it's what
everyone is used to. Also, if you use debhelper (most people seem to,
either directly or through cdbs), it assumes that convention.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email
? Should I report it on BTS?
Do you have CDPATH set? If so, this is a bug in lintian that's already
fixed in Subversion.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
you join the pkg-perl group and maintain such
packages there, and then ask one of the DD members to sponsor an upload
when ready. Currently eloy is doing most of the sponsoring work, but
there are several others involved (myself included) who could and would do
more sponsored uploads if things
y are not going to cope.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
may be useful or it may not; whether
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 a
binaries to work
properly. So in general, if you're using debhelper to package binaries,
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 so
tion or such.
> Aha, I was thinking of:
> http://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 PROTEC
lpr in one place and lp in another? (There may be a good reason. I
just can't follow well enough in the code to know what it might be.)
Other than that, this looks fine. I'd 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]
data source? Are only some METARs supported? Neither
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]
ebian directory from the distribution and
build Debian packages by exporting the Debian directory from Subversion
over a virgin source untar.
<http://www.eyrie.org/~eagle/notes/debian/build-tools.html>
has some additional details for how I do this personally.
--
Russ Allbery ([EMAIL PROT
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 u
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
7;s not clear where this is coming from, 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, em
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
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
o just be
ignored. 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
would be affected ..
All debugging 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]
in reaction to your 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
and then comparing the resulting
.orig.tar.gz file with the one that came with your source package to make
sure that they're 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 P
Andreas Barth <[EMAIL PROTECTED]> writes:
> * Russ Allbery ([EMAIL PROTECTED]) [060429 05:50]:
>> 4. should use -.orig as the name of the
>> top-level directory in its tarball. This makes it possible to
>> distinguish pristine tarballs from repackaged ones. +
rce, I usually
just pull the upstream source 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 w
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 particula
s
an exceptional case that requires careful review, it's even *more*
important to automate where possible so that humans don't miss things by
accident and can review the information-dense representation (the
automation) as opposed to the information-diffuse 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 t
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
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
awfully wasteful to include just for the sake of
completeness.
In this case, I don't disagree 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 Allb
the
source is being 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 muc
build-depends are fine and he just needs to
upgrade to the current xutils-dev. The bad one never got out of unstable,
I'm fairly 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]
s
> that influence the behaviour 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/>
--
particular, ftp-masters actually made a ruling and asked 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/>
--
T
thoroughly and
reliably with this logic.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ient understanding of Debian to
be able to find the debhelper documentation themselves.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rds with the normal shell meaning:
Files
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/>
da warning disappears. Is this
> intended? In every case, this should be documented somewhere.
Sounds like a bug in linda. Maybe it doesn't support 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]
pful at all,
but it's easy enough to make the offer. :)
--
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 a lintian
check, particularly for something that people are going to say just
clutters up the rules file and isn't likely to apply much in practice.
There's no way I'm going to remember to look for this without a lintian
check, though.
--
Russ Allbery ([EMAIL PROTECTED])
kage like I am,
there's an unofficial temporary Debian 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
t* using the space in front of the Homepage field. I've
> not seen any problem with those 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 p
t
completely and instead add a real field to dpkg, 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/>
't use it, although admittedly I expect a
lot of cases 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
entries. If you list yourself as the author of a version in
debian/changelog, 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
?
No. Basically, you should never use LD_LIBRARY_PATH if you can possibly
help it; it causes a bunch 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])
lintian/checks/nmu but it
> doesn't work as expected or at least for me. 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.
ng compiler
version transitions). I'm 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/>
dditional space used by installing a copy of the changelog
with each binary package isn't large.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
101 - 200 of 707 matches
Mail list logo
