checks in my debian/rules)
A (minor) problem with an external script is that dpkg-source won't make
it executable, so you have to make it executable before running it (or
assume what language it's written in, which seems like a bad move).
--
Russ Allbery (r...@debian.org) http
decide which of the two
get-orig-source should be and not standardize both unless people see a
real need to have both of them).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
to do that.
Also, for most usage situations, one really wants to just use INN's PAM
support rather than a Kerberos-only password authenticator and configure
nnrpd to use pam_krb5.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
takes over
the world in time for squeeze and renders sequence information obsolete,
which would be lovely.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
it with an alias, of course, but having the service
command to scrub the environment properly is easier and more consistent.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
think it's better to fix the packages than to add something to
preserve /var/run directories across boot, which seems like a hack to me.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
Michael Biebl bi...@debian.org writes:
Russ Allbery wrote:
It is, however, a standard and supported option and it's the default in
Hm, what standard exactly do you refer too.
standard, adjective [1622]
2) (a) regularly and widely used, available, or supplied
Michael Biebl bi...@debian.org writes:
Another class of services which might be affected, are daemons/programs
started by inetd.
Why would they put anything in /var/run?
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel
Michael Biebl bi...@debian.org writes:
Russ Allbery wrote:
Michael Biebl bi...@debian.org writes:
Another class of services which might be affected, are
daemons/programs started by inetd.
Why would they put anything in /var/run?
I guess for the same reasons why other system daemons put
boot speed from writing all the startup PID
files to a tmpfs file system (and benefits for flash drives as the only
system storage and similar special configurations) are just a bonus.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
about directories other
than recommending that they be used if an application has more than one
file.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
)
Interesting - The unix way IMHO was that /tmp looses content on reboot
while /var/tmp did not. This had been the case for commercial Unices for
at least some decades.
I'm pretty sure Michael meant /var/lock when he said /var/tmp above.
Policy 3.8.1 doesn't change anything about /var/tmp.
--
Russ
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
by the maintainers.
This is in progress now. Lintian is still sadly slower than we'd like, so
it's only about two-thirds done and probably won't be finished until
Wednesday or so. (I have some additional ideas to speed it up, but
haven't had a lot of time to work on it.)
--
Russ Allbery (r...@debian.org
other team members should be able to do QA-style
fixes and transition uploads without using NMU versioning or add
themselves to Uploaders and hence imply that they're taking ongoing
responsibility for the package.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
Charles Plessy ple...@debian.org writes:
Le Mon, Apr 06, 2009 at 11:51:54AM -0700, Russ Allbery a écrit :
There still should be some humans in Maintainer/Uploaders who are
taking primary responsibility for the package, but I think other team
members should be able to do QA-style fixes
Raphael Hertzog hert...@debian.org writes:
On Mon, 06 Apr 2009, Russ Allbery wrote:
Charles Plessy ple...@debian.org writes:
so in the end, can we use the “ * QA upload.” special first line for
non-uploader uploads without breaking the QA infrastructure?
No, that is reserved for orphaned
at the current Policy.
If there are more exceptions that we should add, do say which ones.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
in the debian/copyright file, we could
just put a tarball of the entire upstream source in there. The
conversation is all about where to draw the line between obviously absurd
completeness and insufficient data.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
that
packages comply with bugs in dash that should be fixed in dash.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Josselin Mouette j...@debian.org writes:
Le mercredi 15 avril 2009 à 02:16 -0700, Russ Allbery a écrit :
The advantage of the current Policy approach is that we have some hope
of introducing a new /bin/sh down the road, and we don't require that
packages comply with bugs in dash that should
constitutes estoppel
against suing over your copyright, which accomplishes essentially the
same thing.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
-policy page.)
Yeah, absolutely. Could you file a bug against debian-policy so that I
don't lose track of this before I get a chance to do it?
Thanks!
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
, constructive resolution of
this problem in a way that's consistent with all of our ideals.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
a
portability problem with $@ (see the Autoconf manual).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
on the buildds.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
* 100 | bc`
echo Tag $tag was used $items times ($percent%)
done
`--
Tag \* was used 9277 times (68.0900%)
Tag - was used 3837 times (28.1600%)
Tag + was used 120 times (.8800%)
Tag o was used 390 times (2.8600%)
And for completeness:
Tag \. was used 17 times (.1200%)
--
Russ Allbery (r
-To is that it makes private
replies extremely difficult (in clients that honor the RFC-defined
meaning of the header field, at least) and significantly increases the
chances that private replies will accidentally become public. I don't
think that's the right social direction in which to go.
--
Russ
corresponding to the group (Gnus speak for folder) in which I'm reading
the message.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
publicly or
privately, you're betraying your biological legacy.
We're too busy grooming bugs out of each other's packages. :)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
, since it suppresses exactly the copy
that can be reasonably filed and leaves only the one that goes into
one's personal inbox.
I personally don't mind cc's or not cc's, but that suppress cc feature
is just horrible.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
I am pretty sure:
* Joe User should not be expected to know about Reply to list option.
(Joe User only has 2 buttons: reply and reply to all)
If this is the case, then your proposal above is unacceptable since it
leaves Joe User without a way to reply privately.
--
Russ Allbery (r
private replies difficult or impossible or dropping the copy of
the message that contains the List-* headers.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
tenable.
Certainly looks tenable right now to me.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
checks and the small amount of manual keying
we've not bothered to automate yet.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Frank Lin PIAT fp...@klabs.be writes:
On Tue, 2009-05-05 at 16:25 -0700, Russ Allbery wrote:
It's not particularly difficult. You update the system master and
push that update into NFS, synchronizing any non-/usr data as you
need to across all the systems mounting that NFS partition.
I
Philipp Kern tr...@philkern.de writes:
On 2009-05-06, Russ Allbery r...@debian.org wrote:
I think it's pretty unlikely that *most* Debian machines are done
that way. There are a lot better tools for keeping large numbers of
systems in sync these days than simple cloning from golden images
will require a lot of manual check before filling the bug
(yes, I think the main task in this case should be on the reporter,
not on the maintainer).
If there are too many false positives for a mass bug filing, there are
probably too many false positives for a Lintian check.
--
Russ Allbery (r
makes a lot
of sense to me, but libfoo1 shouldn't be recommending a *-doc package.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Peter Eisentraut pet...@debian.org writes:
On Saturday 09 May 2009 00:58:56 Russ Allbery wrote:
Wouldn't our users expect to get the documentation with many of these
packages by default? Normally you do get some documentation with
things, and I've always been surprised by, say, ntp
/rules the way that we already support various other
DEB_BUILD_OPTIONS settings.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
packages. I think it's likely that if we go that route, with it
providing the defaults, we'll find over time that some packages will
either not build or will mis-build with debian/rules build and no one
will notice or be particularly interested in fixing it.
--
Russ Allbery (r...@debian.org
Raphael Hertzog hert...@debian.org writes:
On Mon, 11 May 2009, Russ Allbery wrote:
I still think Build-Options-Supported is fundamentally the wrong way
to implement that. You have to modify every package to add it
anyway, in which case you can just as easily support it in the
package's
Raphael Hertzog hert...@debian.org writes:
On Mon, 11 May 2009, Russ Allbery wrote:
That seems orthogonal. Either way, you have to get most package
maintainers to modify their packages and test to be sure that you can
change the default build flags. Either way, the results of that
change
format, so clearly that answer is yes insofar
as you think the current Debian archive is sensible. dpkg-buildpackage
setting CFLAGS is a recent change.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
. It matches what we currently
recommend with dpkg-architecture.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Raphael Hertzog hert...@debian.org writes:
On Tue, 12 May 2009, Russ Allbery wrote:
Why would you want to disable all hardening instead of filtering out
the flag that breaks the package?
Because no-one has identified the precise flag that breaks the package?
Then filter out the ones
by pdebuild is useless. I always
delete it in my shell alias that runs pdebuild. I suppose I should have
gotten around to filing a wishlist bug to have pdebuild delete it.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel
newlines like in the usual \s
perl regexp or not ?
No.
This needs to be clarified in Policy in general, since it's been
confusing to people in several different contexts.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ
Malte Forkel malte.for...@berlin.de writes:
Russ Allbery schrieb:
Malte Forkel malte.for...@berlin.de writes:
After some more checking and thinking, I guess I know what's causing
my problems: Its me, probably! I assume the source.changes files are
created while I setup everything
Cyril Brulebois k...@debian.org writes:
Russ Allbery r...@debian.org (15/05/2009):
Calling dpkg-buildpackage -S produces a superfluous _sources.changes
file, so anything that uses that method to produce a source package
for build would either need to remove it or would leave it lying
around
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
Cyril Brulebois k...@debian.org writes:
You call it superfluous. It's particularly helpful for source-only
uploads.
Well, yes, it's superfluous for Debian, which doesn't support
source-only uploads
not what we want, so we can't only defer to RFC 5322. We at
least need a special exception for Description and any other similar
field (Changes and arguably Files and Checksums-*, for instance).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
part is of course because the
standard is written for e-mail, but our fields are essentially the same
thing as an RFC 5322 header field.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
Goswin von Brederlow goswin-...@web.de writes:
Russ Allbery r...@debian.org writes:
So, y'all realize that pdebuild --buildresult .. by default breaks
the *_source.changes file that it generates because it regenerates a
source package as part of the regular build, right? How are you
a bug, which AIUI
needs fixing. Hence I wonder how this was and will be handled.
Removing that part from Policy would be my preference. It's duplication
of information that's already in the changelog.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
Deng Xiyue manphiz-gu...@users.alioth.debian.org writes:
On Sun, Jun 07, 2009 at 11:51:25PM -0700, Russ Allbery wrote:
Removing that part from Policy would be my preference. It's
duplication of information that's already in the changelog.
Would it merit a BTS entry against debian-policy
the copyright notice.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Robert Collins robe...@robertcollins.net writes:
On Wed, 2009-06-10 at 15:57 -0700, Russ Allbery wrote:
Does Debian only care about listing copyright holders, as opposed to
reproducing legally meaningful copyright statements? If so, why not
just list names here, excluding the word Copyright
Noah Slater nsla...@tumbolia.org writes:
On Wed, Jun 10, 2009 at 03:57:46PM -0700, Russ Allbery wrote:
Because we have to comply with licenses that say that we need to
reproduce the copyright notice.
Don't we satisfy that requirement simply by packaging the source
files?
I don't see how
Russ Allbery r...@debian.org writes:
The BSD license says, in part:
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
If the original said Copyright 1994 Foo Bar and we instead said
Copyright 1992-1996 Foo Bar, is that reproducing the copyright
notice? Personally, and not being a lawyer, I'd say the answer is
obviously yes
Sune Vuorela nos...@vuorela.dk writes:
On 2009-06-11, Russ Allbery r...@debian.org wrote:
Ack, sorry, that's the wrong part. I meant to paste the one
immediately below:
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions
. There are packages with one
GPL component that is not the component that's linked with OpenSSL.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
proposal is simple,
and provides consistency.
That doesn’t hold. Most of my copyright files are much easier to read
than DEP5-like ones.
Yes, I agree. My existing pre-DEP5 copyright files are easier for a
human to read than the DEP5 format.
--
Russ Allbery (r...@debian.org) http
things that aren't part of the bits that have
a fixed format or that aren't easily expressed that way. That would
strike a better balance in some places, I think.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ
, be
| it before or after the machine-interpretable part. I therefore suggest
| that fields can be interspread anywhere in the file. Lines that do not
| start with a known field name or that do not start with a space and
| follow a valid line should be ignored by an interpreter.
--
Russ Allbery (r...@debian.org
Noah Slater nsla...@tumbolia.org writes:
On Thu, Jun 11, 2009 at 06:40:46PM -0700, Russ Allbery wrote:
I think you have to go back most of the way to Sam's original proposal.
Is there any reason a Comment field wouldn't suffice?
I guess it's a matter of taste, but I think there's
Lars Wirzenius l...@liw.fi writes:
to, 2009-06-11 kello 11:47 -0700, Russ Allbery kirjoitti:
Even with the DEP-5 copyright file, you can at most generate a
candidate set that you still have to manually check. There are
packages with one GPL component that is not the component that's
linked
a format.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
are using
prgnlibtool/prgn to do their linking. The latest GNU
libtools (= 1.3a) can take advantage of the metadata in the
Please copy 519...@bugs.debian.org on all discussion.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
knowledge, but it's possible.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
(--remove)
E: bla bla...
Lintian uses N: for informational messages that don't represent
problems. That's not any kind of standard, of course, but it might be
worth copying it.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
wrong, IMHO.
Both Lintian and Policy, in fact. Policy will be fixed in the next
release.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
]
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Philipp Kern tr...@philkern.de writes:
On 2009-06-22, Russ Allbery r...@debian.org wrote:
Philipp Kern tr...@philkern.de writes:
As explained lintian was wrong after I dropped the bit that
collapsed amd64 i386 all to any in dpkg-source. The problem is
that we lost information about what
in the US, but I can't speak for other countries.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
to do that no matter what the copyright statement said.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
$0) $@
It's generally better to just set RPATH when building the binaries for
that case.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
personally be able to trace that key to a person.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Manoj Srivastava sriva...@debian.org writes:
On Mon, Jun 22 2009, Russ Allbery wrote:
Going back to the previous discussion in debian-devel about signing a
key for which the only IDs are pseudonyms, I personally would do
that, but only if I knew the person personally and knew they were
, since a lot of
people in the US simply never bother to get a passport.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
that
this has changed, although it's possible) contains absolutely no
anti-counterfeiting security measures and does not have a photograph.
I could trivially print one out on a laser printer.
Other countries issue cards for similar uses that are much more robust.
--
Russ Allbery (r...@debian.org
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
For example, I think US drivers' licenses are only verifiable by
someone who's lived in that state or otherwise seen drivers' licenses
from that state. I really dislike seeing people use them at key
signings
that
Debian can identify a thousand people who *aren't* responsible, namely
all the rest of us.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
are anywhere near as widely used as Debian.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
to bother to port
the Hurd to hppa.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
be installed
in subdirectories of the `/usr/lib' directory. Such files are
exempt from the rules that govern ordinary shared libraries, except
that they must not be installed executable and should be
stripped.[5]
Perhaps that's not quite the definition of not public we want?
--
Russ
for things like test -a.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
on amd64.
Surely this is as simple as:
case `dpkg --print-architecture` in
amd64)
# Do some stuff.
;;
i386)
# Do some other stuff.
;;
esac
isn't it?
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ
for programs
like lintian than shell scripts (which are already hard enough).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
no time to do the work. :/
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
in, rather than using the coarse
error/warning distinction. It seems like something similar could work
here.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
that explicitly uses bash has no
declared dependency on bash because it's essential. I think attempting to
go through and add all those dependencies and test would be a huge waste
of time and resources.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Giacomo A. Catenazzi c...@debian.org writes:
Russ Allbery wrote:
libc is essential from a Policy perspective. It's just not marked that
way in the packaging system in case the SONAME changes, but it's
essential in the same way that awk is. Note that dependencies on awk
are not required
Giacomo A. Catenazzi c...@debian.org writes:
Russ Allbery wrote:
awk is essential. Specific awk implementations are not, but the
interface is essential. This is something that we've discussed many
times over the years and I'm absolutely certain that statement is
correct.
awk is a virtual
301 - 400 of 4311 matches
Mail list logo
