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
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]
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
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
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
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
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
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
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
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]
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]
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
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
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
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]
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
? 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]
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
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/>
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]
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]
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]
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
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
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
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
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
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
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
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
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])
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/
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
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]
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]
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
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]
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]
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 (
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]
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]
.
(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
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
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]
site. It's referred to in Policy 3.9.1.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
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
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]
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/~
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
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]
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]
(>= 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/>
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
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]
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]
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
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
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
-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]
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
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'
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]
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])
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])
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
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
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
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
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]
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
w when you've fixed the above (except maybe the last) and I'll
sponsor 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]
res that cdrtoaster uses
alternatives too, but then the result is much more maintainable and
predictable for the user.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
(which should happen before any upload).
Right. And for this particular lintian error, it also means that if the
"missing man page" QA project gets resurrected, it will be easy for others
to find the packages that need assistance.
--
Russ Allbery ([EMAIL PROTECTED])
ian messages stay rather than using overrides. A
lintian override to me means that the lintian message is wrong in this
particular case, not that it's a known bug.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PR
er uploading that package, I believe you'd need to file
a bug with ftp.debian.org to remove the old fhist-doc package.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
id it come from, anyway? If
> they serve a purpose, they should probably be listed in .PHONY, for
> consistency and transparency.
It's common in older packages, probably due to some migration of policy
from long ago. I just strip it out routinely whenever I see it.
--
Russ Allbery ([EMAIL
Justin Pryzby <[EMAIL PROTECTED]> writes:
> On Wed, Nov 09, 2005 at 01:13:44PM -0800, Russ Allbery wrote:
>> Essential means that it's very difficult to remove the package and you
>> have to jump through extreme hoops to do so, and that removing it may
>> break the
in progress, in fact.
That leaves the following as the only differences that I don't know the
story behind off-hand:
> +gcc-4.0-base
> +lsb-base
> +makedev
> +passwd
> +procps
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Upgrading is typically in the postinst. Or did I misunderstand?
I'm pretty sure that he's talking about updating the .orig.tar.gz tarball,
and the script that was upthread called rpm2cpio as part of that.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eag
as part of package installation, which this isn't.
Depends is for things the package needs to run. Build-Depends is for
things the package needs to build. Things the package needs to run
get-orig-source or the like are neither, and therefore don't need to be
listed, IMO.
--
Russ Allb
ge the doc is for.
I prefer -tutorial to -doc in this particular case, since otherwise when
browsing the package list I'd think I'd have to install the -doc package
to get any documentation at all (rather than just a separate tutorial).
--
Russ Allbery ([EMAIL PROTECTED]) &
t to run the clean rule, although I
know that isn't always as easy as it sounds. But it's nice to be able to
use pdebuild without having the build dependencies installed outside the
chroot.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
at could
be easily fixed
I think it's very important to use the upstream tarball exactly as it was
downloaded from upstream whenever possible, since that way (as previously
mentioned) signatures are still valid, MD5 checksums are still valid, etc.
The exception would be when you have to
ches that the upstream maintainers might take.
They still might not be willing, but at least you have a fighting chance,
where as the post-configure sed stuff they'll never want.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [E
ce, and most of my concern only
applies when maintaining the package rather than NMUing it. The minimal
modifications that one makes in an NMU are hopefully unlikely to result in
other unrelated Policy violations due to forgetting to do something that a
debhelper script might have remembered
Ben Finney <[EMAIL PROTECTED]> writes:
> On 08-May-2005, Russ Allbery wrote:
>> If they're really just shell libraries (and hence
>> platform-independent), they should go into /usr/share rather than
>> /usr/lib per the FHS.
> Relevant sections of the FHS:
to do, any reason Debian doesnt want them there?
If they're really just shell libraries (and hence platform-independent),
they should go into /usr/share rather than /usr/lib per the FHS.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRI
them, but that shouldn't be questionable.
I thought the user would only be prompted if the file changed *and* they
had made local modifications to the old file. The last is fairly unlikely
for READMEs.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To
> debian-mentors, but I can't find it, nor remember the conclusion.)
I would, yes, just to make sure that the files you distribute can be
regenerated from the package. You should be able to do this by running
latex and pdflatex on the .dtx file.
--
Russ Allbery ([EMAIL PROTECTED])
modifications.
To do anything else, you have to get permission from DJB, although he's
stated elsewhere that he doesn't think copyright law can prohibit the
distribution of patches or your application of patches to software you're
building yourself. (Note that doesn't include d
grading-checklist.txt.gz works for
> me. Naturally you need the debian-policy package installed for that to
> work...
Having debian-policy installed plus using apt-listchanges is a pretty nice
way of getting notified of new policy releases too. :)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
grading-checklist.txt.gz works for
> me. Naturally you need the debian-policy package installed for that to
> work...
Having debian-policy installed plus using apt-listchanges is a pretty nice
way of getting notified of new policy releases too. :)
--
Russ Allbery ([EMAIL PROTECTED])
a new upstream version. I figure that if it's important
enough to release a new Debian package, it's important enough to release a
new upstream release too, and just make it clear to people in the release
notes whether it's a bug fix they're likely to care about.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
a new upstream version. I figure that if it's important
enough to release a new Debian package, it's important enough to release a
new upstream release too, and just make it clear to people in the release
notes whether it's a bug fix they're likely to care about.
--
would be easier to sponsor, I can start on one of them.
I do have a bunch of new packages that I'd like to contribute over time
too, but I figured it would be better to start with adoptions and only add
new packages after I'd helped with the backlog of packages needing a
would be easier to sponsor, I can start on one of them.
I do have a bunch of new packages that I'd like to contribute over time
too, but I figured it would be better to start with adoptions and only add
new packages after I'd helped with the backlog of packages needing a
e the
package details:
Package: xfonts-jmk
Priority: optional
Section: x11
Installed-Size: 984
Maintainer: Russ Allbery <[EMAIL PROTECTED]>
Architecture: all
Version: 3.0-5
Depends: xutils (>= 4.0.3)
Filename: dists/sid/main/binary-all/x11/xfonts-jmk_3.0-5_all.deb
Size: 515976
MD5sum: de
e the
package details:
Package: xfonts-jmk
Priority: optional
Section: x11
Installed-Size: 984
Maintainer: Russ Allbery <[EMAIL PROTECTED]>
Architecture: all
Version: 3.0-5
Depends: xutils (>= 4.0.3)
Filename: dists/sid/main/binary-all/x11/xfonts-jmk_3.0-5_all.deb
Size: 515976
MD5sum: de
it hard to comment
without retrieving the whole source package and poking around, and I'm not
sure what segfaults you're getting or how they're produced. Is there a
fairly self-contained example that you know is segfaulting that you can
include? I've done varargs conversions befo
601 - 700 of 707 matches
Mail list logo
