e for that. It's a bug in lintian (there's code to
not warn about URLs that doesn't work) 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]
patch to Policy that documents the field 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/>
e unified diff of a patch is going to be a derivative
work in most cases and also won't be redistributable.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subje
th upload rights. ftpmaster is just checking for mistakes (at
the point at which most mistakes are made).
The difference for mentors is that the uploaders are not (yet) Debian
project members and are not guaranteed to be trained in our licensing
policies, and have not agreed to follow our rules
Michael Gilbert writes:
> On Thu, Jan 19, 2012 at 1:07 PM, Russ Allbery wrote:
>> For the main archive, the NEW check I think is best thought of as a
>> spot check to ensure maintainers are doing their jobs. The real
>> responsibility of not uploading non-redistributab
nsidered (if, thankfully, not yet
passed), it's probably worth being somewhat paranoid about things that get
the official imprimatur of the project. And I'm certainly not a lawyer
and this is just my guess.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/
course a whole field of expertise
in and of itself.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
d, for example.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http
e correct
dependencies, changes that upstream was completely uninterested in since
from their perspective there was no upside and it just made the build
system more fragile. I was able to drop a ton of that cruft by switching
over to --as-needed.
For packages that use Automake and Libtool, dh-autorec
ke the build system buggy on other operating systems and is not actually
a good idea unless all of the libraries the package uses support a
facility like pkgconfig (which is something that upstream is often not in
control of).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org
makes it
> hard to look up what they are!
The current plan is to release debian-policy with the 1.0 version of this
document on February 22nd.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@l
e-tar, since that will get you
started on a good branch layout and workflow without really changing how
Git behaves (unlike the more complex patch management tools).
Later on, once you're familiar with Git and have a firmer grasp of the
tradeoffs, you can consider using one of the more complex ov
Jerome BENOIT writes:
> What should be the default target for debian/rules ?
Whatever you want, basically. None of the standard tools ever invoke it
with the default target, so it's up to the discretion of the maintainer.
--
Russ Allbery (r...@debian.org) <http://ww
Even with valgrind, personally I'd just list a specific set of
architectures on which valgrind is required, even if you also
opportunistically test for its existence. There's no reason to allow
*not* running valgrind tests on i386 and amd64.
--
Russ Allbery (r...@debian.org)
and ignore the test failures (if you think
they're bugs in the test suite and not the package) if the output is
valuable, or don't depend on the tools and skip the tests.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCR
or maintaining the upstream branch that I want to move to eventually.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
Goswin von Brederlow writes:
> Russ Allbery writes:
>> http://www.eyrie.org/~eagle/notes/debian/git.html
> Where were you 2 years ago when I first asked about how to use git when
> being both upstream and debian maintainer? :)
Posting that site to Planet Debian. :) In Aug
working directory. It then
> remains out of the orig tarballs even if I keep the patch across
> upstream releases.
Yeah, I did that for a while too when I realized that I really needed a
Debian-specific patch. It works, but quilt is really another VCS, and I
don't like layering one V
eam. Looking at it again I think
> debian/import-upstream tarball master upstream/x.y
> would be correct. Will try that when I find the time to recreate the
> repository.
Yes, that would work if you want to preserve the history. But since
nothing other than pristine-tar is goin
elopers-reference/pkgs.html#nmu
Also the wrong version for an NMU of a new upstream release (should be
-0.1).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "
> does with #DEBHELPER#).
Yup, this is what the OpenLDAP packages do for exactly this use case.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe&
Malte Forkel writes:
> Am 25.03.2012 19:21, schrieb Russ Allbery:
>> Arno Töll writes:
>>> As another alternative which comes me in mind is a pseudo-shared
>>> library. You would put the common functions into
>>> debian/maintscripts-common and copy its con
the merge, but doesn't send
notifications for all the individual commits. I'm not sure why, but I'm
not complaining.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a su
bined. The merge approach
described in the last paragraph there is now supported natively by the
latest git-buildpackage (although I haven't had a chance to test yet).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-me
nd loose coupling right; even
Java, which provides a lot of tools to try to get it right, doesn't offer
a good ABI versioning system, so if you do have to change the ABI, there
isn't a good way of handling the transition.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/
rpg really
sufficiently better than than apg's pronounceable password generation
algorithm to warrant yet another package?
apg uses Morrie Gasser's algorithm from A Random Word Generator For
Pronounceable Passwords (National Technical Information Service (NTIS)
AD-A-017676).
--
Russ Allbery (r
that was made in an earlier version, I fix it like any other bug:
correct the changelog for that version, and add a note in the changelog
for the most recent version that I fixed the documentation bug.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNS
won't be reached in its
entirety. There will be some remnant of non-multi-arch library packages
in the wheezy release.
> Then all other packages must be removed from testing before freeze, right?
No.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/&
rsioning system. The key requirement of coinstallability
of multiple versions of the library is that the library MUST use symbol
versioning properly so that the libraries can coexist in memory without
tromping on each other.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.
tall that as a documentation file like any
other (but don't bother to invent copyright notices for all the people
listed there to add to debian/coypright).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-req
nd documentation, for
example), and it's traditional to have a blank line between each option
documented in OPTIONS. The second problem at least can be fixed by just
deleting the .PD 0 command (or at least moving it down to the formatting
section, if it's still desireable fo
Russ Allbery writes:
> * The formatting of the man page isn't great. There are a few places that
> seem to have spurious line breaks (the --append documentation, for
> example), and it's traditional to have a blank line between each option
> documented in OPTIONS.
. It's certainly fine
for you to follow stricter standards in your own packages and ask for
stricter standards in packages you sponsor, but I'm willing to sponsor the
package as-is.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSU
it. It's possible that after further discussion my interpretation
will be considered wrong by consensus, but as you mention, I think it's a
common interpretation by other packagers of GNU software.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
plied in all of my own packaging, and
which I had, prior to this thread, assumed was the interpretation that
everyone held.
We're both on the same page about applying the same standards to
sponsoring as one would generally apply to any other package in the
archive; I think this is just a disag
OK to use the Comment section for David Keppel.
Absolutely.
And I'm sorry for my tone in some of my earlier messages. I had a really
obnoxious week and didn't do a very good job of keeping that out of my
tone.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~e
Bart Martens writes:
> On Sat, Jun 23, 2012 at 12:54:10AM -0700, Russ Allbery wrote:
>> Bart Martens writes:
>>> That "authors" are not the same as "copyright holders" is simply a
>>> fact regardless of what debian-policy states. For example, th
Ds, so both p12 and Name Surname are identical for the
> purposes of identification. The only difference is that it's obvious
> that the former is a pseudonym :)
For the record, here's the actual policy for DDs:
http://lists.debian.org/debian-newmaint/2009/07/msg00044.html
--
Rus
Bob Proulx writes:
> It was. But then Russ Allbery noted some oddities! :-) I have
> addressed those issues with a new package turn. Here is the latest
> and greatest:
>
> http://www.proulx.com/~bob/debian/pool/sid/main/time/2012-06-24/time_1.7-24.dsc
>
> http:
Sandro Tosi writes:
> thanks for pinging me. I saw others taking over the additional reviews
> of time, so I'm fine with them sponsoring it.
Thanks, Sandro!
Bob, I've uploaded the latest version. Thank you for your work!
--
Russ Allbery (r...@debian.org) <h
to the documentation
through to completion.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Marc Haber writes:
> On Sun, Jul 01, 2012 at 07:53:04PM -0700, Russ Allbery wrote:
>> It would indeed be best if everything possible was documented, but very
>> few people volunteer to do the work to drive changes to the
>> documentation through to completion.
> This
econd package for
changes in a third package just feels like the wrong design to me.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
e package
that holds all that shared stuff between the MySQL packages.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
elieve
is not copyrightable in Europe either. There is some precendent for doing
something similar to what you're doing (see readline/editline).
Of course, even if what you're doing is perfectly legal, that doesn't
prevent someone from suing you anyway.
--
Russ Allbery (r...@de
will know next time.
I've always taken the time to ask the sponsee first if making the change
is okay. Usually people don't mind, and it rarely takes much time to get
a response, so it's not much of a delay. I don't know that it's
necessarily *required*, but it felt to
e known to be
free, is not something that ftpmaster has ever previously required.
Unfortunately, there is not good documentation of exactly what's required
in copyright files. There are a lot of open bugs against Policy about
this.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.or
sed build system licenses.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://li
you can do that by overriding dh_autoreconf and running:
dh_autoreconf -- autoconf
instead of its default action. That should be safe, since the package
doesn't use automake or libtool either, so the other things that
autoreconf runs are not relevant to it.
--
Russ Allbery (r...@debian.org)
the
library shared object version.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y5m57gbu@windlord.stanford.edu
ainer is also upstream and this is not
a trivial change semantically even if it's small in number of lines
changed, it would be good to have Lars be able to review this before
pushing it into the archive as an NMU.
Lars was posting to debian-devel as recently as last Saturday. Let me
copy him
ie from your hardening options. For some reason that I've
not been able to figure out, PIE causes some really weird problems in some
applications.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@
)
> "merged" not in the sense of merging the branch but in the sense of
> reimporting it, right? At least I don't see an git-import-orig option
> which allows "upstream-source" to be a git branch.
git-import-orig --upstream-vcs-tag. It's great. :) I use it
fically to gain the above effect. I would recommend against ever
using .dfsg due to the sorting problem with upstream minor versions, since
+dfsg is otherwise equivalent.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-
d:
http://www.eyrie.org/~eagle/journal/2012-01/007.html
http://www.eyrie.org/~eagle/journal/2012-01/008.html
http://www.eyrie.org/~eagle/journal/2012-02/001.html
before going too far down this path.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Lintian cannot detect), such as this
one. There are huge false positive problems with the tag, which is why
it's still experimental.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
w
"Bernhard R. Link" writes:
> * Russ Allbery [121102 19:29]:
>> I'm starting to think that we should drop this tag entirely. There are
>> a lot of legitimate reasons why shared libraries call exit(), plus
>> there are legitimate reasons why shared libra
ve to debdiff the *.dsc files. The
devscripts package has an nmudiff script that automates much of this
procedure.
(I'm listed as a comaintainer for openldap but haven't had any time to
work on the package for quite some time, unfortunately. I should really
probably remove myse
TS ?
I use Bugs: mailto: as a source package header in debian/control
instead.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
publicly archived (including the email address of the
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Russ Allbery ' as your from address.
Getting status for svnlog...
Checking for newer versions at madison...
Will use mailto pr
ht now, I think the best thing for the Doxygen *clients* to do is
just ignore this issue. It may need a bug against doxygen, though (and
possibly some help for the Doxygen maintainer).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email
ept
your new uploads.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/871uf696xv@windlord.stanford.edu
this
isn't the right solution, since it also breaks invoking debian/rules as a
makefile instead of as an executable.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of
s, that's how it's looking now.
> You should then take Russ Allbery's comment into account:
> On Tue, Feb 17, 2009 at 02:06:09PM -0800, Russ Allbery wrote:
>> If the -B flag is necessary, this will require a change in Debian Policy;
>> currently, the above arguably v
Joey Hess writes:
> Russ Allbery wrote:
>> I really think this is a bug in make.
>
> Probably, but who knows. It could just be a misfeature on which ghod
> knows what somehow depends.
>
> .PHONY: precompiled-binary-we-cannot-regenerate-with-gcc.o
It feels like the
r another
platform where shared libraries require PIC to see the problem.
Lintian should also warn about this, though, even on i386.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
support IPv6, and
inetd can already do all that for you.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Version} or
${source:Version} as appropriate (introduced in dpkg 1.13.19, released
with etch). Support for ${Source-Version} may be removed from dpkg-dev
in the future.
Is that still unclear?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSU
GPL 2 and GPL 3, Eduardo is correct and the
address portion is not part of the notices that the GPL requires be
maintained.
> If it is not required to be verbatim in ‘debian/copyright’, then why
> include it at all?
I don't see any reason to do so at the moment.
--
Russ Allbery (r...@d
ue to a non-free build-dependency.
That would mean it should go into contrib, which is for DFSG-free things
that can't be built or used without non-free bits.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentor
Chow Loong Jin writes:
> On Thu, 2009-03-26 at 10:53 -0700, Russ Allbery wrote:
>> That would mean it should go into contrib, which is for DFSG-free
>> things that can't be built or used without non-free bits.
> I'm actually considering using a postinst script to tel
with sh -x
/var/lib/dpkg/info/foo.postinst, and then it doesn't exit on error, it's
surprising and can be dangerous.
It's an unusual situation, which is why it's only tagged with --pedantic.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle
)
instead of:
$(DESTDIR)$(prefix)
I used to write my makefiles that way too. It's hard to shake the feeling
that there should be a slash in there.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-re
Chow Loong Jin writes:
> Looking at where the extra / is, I'd think more like:
>
> pkgincludedir = $(includedir)/slv2
>
> rather than
>
> pkgincludedir = $(includedir)slv2
Oh, hm, good point. In that case, it is a little odd that $(includedir)
has a
it's fine to omit the
version number if you expect not to need it. I plan on starting to omit
the version number after dfsg in the next upstream release for some of my
repackaged source packages where the repackaging has been stable for quite
some time.
--
Russ Allbery (r...@debian.org)
end to add overrides for info-level tags. It's only pedantic
tags that I recommend against overriding.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
o remove the override again and in
some cases it can hide other problems that are real. We in turn try to
fix bugs quickly, although I've been swamped lately so the pace of
releases has dropped.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
added explicit nul termination for all strings
as an additional line of code when making that change, correct? (I
personally prefer to ship a replacement strlcpy function rather than
using strncpy, since the strncpy semantics are rather broken.)
--
Russ Allbery (r...@debian.org)
strlen("\r\n").
That code is safe from a buffer overflow perspective using strlcpy and
strlcat, but may not end the buffer with \r\n.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
re.ac and then include
LTLIBOBJS in the list of objects that go into the shared library in your
Makefile.am.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe&q
; ftp.cpp~
> ftp.h~
> ftp.protocol~
> README~
> rfc4217.txt
> "
I'd put that information in debian/copyright instead. (What you have
sounds fine, or you could just say that you removed rfc4217.txt for DFSG
reasons and, since you were repackaging the source anyway
t unfortunately doesn't help unless you're writing kernel modules.
That's an implementation inside the kernel only for code running inside
the kernel; it isn't available to normal programs.
I just provide replacement implementations of strlcpy and strlcat with
all of the softwar
etty bad, either including way more
details than the average user cares about or including almost nothing.
I'm with Ben; I try to summarize major changes for all of my packages
that are likely to affect users in the Debian changelog. I don't always
manage, but I try.
--
Russ Allbery
his. That
being said, there's already a wishlist bug against Lintian to check for
this at the --pedantic level.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Rogério Brito writes:
> I'd like to make it clear that I'm just brainstorming here and that at
> this stage, I'm not really concerned with the feasibility of the ideas.
> I'm just doing a "what if" thing.
Oh, sure, totally understood.
> On May 02 20
tags can be a little
annoying.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Patrick Matthäi writes:
> Russ Allbery schrieb:
>> Given that anyone can upload packages to mentors, this seems like a
>> fairly worrisome security risk.
> Why that? It may be implemented as the current Debian buildd network.
> OpenSuSE is also providing such a buildd se
binary packages but throw
> them away so I'd like to have mentors do something similar.
This seems like a good idea to me too.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.o
rit to keeping a package of the newer code
available to people who specifically need newer versions.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
etter to say:
PKG_CHECK_MODULES([PKGNAME], [glib])
AC_SUBST([PKGNAME_CFLAGS])
AC_SUBST([PKGNAME_LIBS])
It doesn't matter until one day it does and you get bizarre and obscure
error messages and corrupted shell scripts and spend hours trying to
figure out why.
--
Russ Allb
Rogério Brito writes:
> On May 11 2009, Russ Allbery wrote:
>> Just to double-check: did you already know the background on this?
>> The gnus Debian package is not really recommended for most users.
>> Most users of Gnus are probably better off not installing the gnus
Check the contents of your package. For some reason, the package still
contains the directory even though you've removed it from debian/dirs.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.o
rror.
next if /^Record size =/;
next if /^Skipping to next header/;
-next if /^gpg: /;
+next if /^gpgv?: /;
next if /^secmem usage: /;
next if /^Exiting with failure status due to previous errors/;
tag $tag, $
moved:
DwString::operator[](unsigned long)
which was present in the previous version. Is this also an internal
symbol or was it part of the published API?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ional (and
can be tricky with C++ since the symbol names can vary per architecture).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
lready knows
it exists are likely to want to use this package.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
y unused SASL
implementation, or Shishi (an interesting Kerberos implementation, but
99% of users will want either MIT or Heimdal instead).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a s
, I agree. I wouldn't go to people in general and ask them to
make their packages priority: extra. I was only questioning because
you'd said to raise the priority from extra to optional, and this didn't
seem like a package where we'd want to make a special effort to move it
i
Simply calling dh_installdeb before dh_shlibdeps fixed it; it wasn't me
> who wrote that debian/rules and I have no idea whether it used to work.
It looks like dh runs dh_shlibdeps before dh_installdeb, so I would have
expected more people to run into this.
--
Russ Allbery (r...@debian.org)
directory already exists
(I can't find a mkdir anywhere and it writes to the shlibs file there),
and I can't figure out where earlier in the calling sequence the DEBIAN
directory would be made.
Clearly I'm missing something
--
Russ Allbery (r...@debian.org) <h
301 - 400 of 707 matches
Mail list logo
