e). See:
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#run-time-shared-libraries
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
Ansgar writes:
> On Wed, 2023-05-10 at 13:50 -0700, Russ Allbery wrote:
>> Caring about them isn't the same thing as doing everything they want.
>> We can both try to make things as smooth for them as possible and still
>> make design decisions about Debian t
ng they want. We
can both try to make things as smooth for them as possible and still make
design decisions about Debian that they may disagree with or that may make
some property they want to maintain difficult or impossible. It's the
sort of decision we have to make on a case-by-case basis.
English, as a word that I
wouldn't expect to see in a technical context and for which the analogy is
not immediately obvious).
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
Guillem Jover writes:
> On Tue, 2020-08-04 at 13:56:45 -0700, Russ Allbery wrote:
>> I assume this is in support of systems, containers, or jails where UID
>> 0 may not have CAP_FOWNER?
> If that's the reason, it certainly was not clear from the original
> report. :)
It s
n strategy coordinated across multiple
packages, since this behavior is encoded in a lot of places. Maybe it
would make sense for Guillem to weigh in first and indicate whether this
would be a problem on the dpkg side and if he sees any concerns. Copying
debian-dpkg@lists for that.
--
Russ Allbery
nlikely.
So this is undefined behavior, but I suspect in practice it's relatively
unlikely to break.
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
Ian Jackson writes:
> Ian Jackson writes ("Re: Bug#932753: tag2upload should record git tag signer
> info in .dsc [and 1 more messages]"):
>> Russ Allbery writes ("Bug#932753: tag2upload should record git tag signer
>> info in .dsc [and 1 more messages]"
allows the tagger field to be defined has having the same syntax
as Maintainer (or one of the other existing RFC-2822-style fields we
have), which I think increases the chances that parsers will get this
right.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
libdeps imposes some restrictions, so maybe it
would be worth adding some details there. But I'm not sure how often this
comes up.
Usually I refer people to the Libtool documentation on maintaining the
SONAME, which documents two specific and reasonable conventions in the
context o
gnome_shell.json
Splitting that single config file into a separate contrib package feels
like overkill here. It shouldn't hurt anything on a system without Chrome
and it doesn't create any sort of dependency on Chrome, which is the
normal case for contrib.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
hat Policy recommends the maintainer does. So don't
feel any obligation to change what uscan is doing on Policy's account
here.
That said, as discussed elsewhere, I'm a huge fan of there being only one
way to do something like this, with some easy tools to convert other
methods into th
hat anyone who wants to
include an upstream signature that's provided in *.sig format will need to
convert it to *.asc, but that's not a *change*. That's the current state
of the archive.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Henrique de Moraes Holschuh <h...@debian.org> writes:
> On Sun, 13 Aug 2017, Russ Allbery wrote:
>> it can't just move the file -- it has to ASCII-armor it. But still, I
>> think that's the right thing for the tools to do, not add another file.
>> (The ASCII form
ent how to include upstream
signature files in a Debian source package, absolutely. (That's quite a
bit more than just adding them to examples.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
rce tarballs to follow our naming convention
(which upstream almost never uses). The bug may be best filed against
devscripts for uscan --download to rename the signature on download.
It's almost never a good idea to introduce synonyms into any sort of
standard. It adds a lot of complexity
ecific versions of packages and not
allow anything else.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
n and not ASCII 45, I'm really
>> confused what's going on with this, though.)
> We should probably ask Colin about this. :)
Yes, please -- Colin, do you have any idea what the current best practice
is here? I'm trying to figure out what to have Pod::Man do.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
/cache/pbuilder by default. I think a good
argument can be made for picking some default like this and going with
it unless overridden.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
use in my
packages these days, is to have these reflect the authors, copyright, and
license of the *manual page*, but that's also weird.
=for license, resulting in a comment in the generated man page, seems like
a better general solution (and then it probably makes sense for this to
alway
eirdly parallel track without much interaction with those of
us who were maintaining all this stuff for Perl 5.
I generally just give up on this and use the normal text markup
conventions of angle brackets and whatnot, although I see why you don't
want to do that here.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
just suppress it entirely, I
guess). I'm happy to add support for this (obviously, patches even more
welcome).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
the right thing instead, since
it would be nice to allow, say, a smart HTML converter to do proper links
between man pages.
> Seems to be really needed, mostly to markup verbatim blocks, otherwise
> the formatting would need to be dropped. :/
What sort of verbatim formatting problems have you
(which is where
cowbuilder is right now), I personally would be happy to use something
that's a bit closer to what the buildds are doing.
However, cowbuilder does just work, in my experience, and it's nice to not
have to change.
Note that the same integration also works with qemubuilder, for whatever
would be
a bad idea and quite annoying because it could disallow possible
installations which would be even more confusing.
+1.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject
guidance on how to
interpret the results of dpkg-architecture -L and how they map to wildcard
strings.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
to the glibc packages.
solution 3: Create metapackage libc-dev and let glibc-dev,
musl-libc-dev and possible others provide libc-dev.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject
the states)
I thought Guillem requested we use the capitalized versions. I think the
capitalized versions stand out more and make it clearer that the expected
meaning isn't necessarily the plain English meaning of the phrase.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
and perltidyrc files. (perltidy is... awkward.
There are places where how it formats the code is clearly suboptimal, at
least to me, and despite initial appearances it doesn't have enough dials.
But I'm sticking with it so far.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
Russ Allbery r...@debian.org writes:
Oh, glad it was helpful! In case it's of interest, attached are my
current perlcriticrc and perltidyrc files. (perltidy is... awkward.
There are places where how it formats the code is clearly suboptimal, at
least to me, and despite initial appearances
. That seems more useful.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87pq5lobfi
from the intention of this construct without multiarch.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
Kip Warner k...@thevertigo.com writes:
On Sat, 2012-09-08 at 22:57 -0700, Russ Allbery wrote:
Generally you can just do it as a separate branch within the same
repository. See, for example:
http://www.eyrie.org/~eagle/notes/debian/git.html#combine
(This still needs some updates
Julien Cristau jcris...@debian.org writes:
On Sun, Aug 12, 2012 at 14:25:12 -0700, Russ Allbery wrote:
Okay, once more for the win. Here is the current version of the patch,
incorporating substantial improvements from Jonathan Nieder and
hopefully incorporating all the feedback in subsequent
Jonathan Nieder jrnie...@gmail.com writes:
Russ Allbery wrote:
I'm therefore including here the complete SGML source of that section
not in diff format, followed by the diff of everything *outside* of
that section. I think this will be easier to review.
Thanks! I would have preferred
version of
the patch to review what I further changed.
I'm going to reply to this thread in a moment with the whole current
patch, for hopefully the last time, and then we can try to get seconds and
(at least) merge this monster.
commit 97cb027db4afab774ea4f4ff9e7bef7a6dcbbda0
Author: Russ Allbery r
Russ Allbery r...@debian.org writes:
commit 97cb027db4afab774ea4f4ff9e7bef7a6dcbbda0
Author: Russ Allbery r...@debian.org
Date: Sun Aug 12 14:14:23 2012 -0700
Further wording changes on top of Jonathan Neider's work
I fixed the spelling of your name in Git before I pushed. Sorry
~) or (= 1:1.2.3.3.dfsg) to be
kind to backporters? Before the patch, the example said = 1:1.1.3.
Let's go with 1:1.2.3.3.dfsg in the example to show the common case
instead of the unusual case. I've applied this:
commit 29e3fc2e05b59a7e13913a263a1e22d40cbc9918
Author: Russ Allbery r...@debian.org
the
coordination with the package maintainer part.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org
it with a much simpler
debate about the right interface to view those files for installed
packages.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
don't think that the move to package metadata will be
done in time.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
. Architecture: all in a binary package means
it can be installed on any architecture; otherwise, it's an
architcture-specific binary package and must be multiarch to be
installable as a non-native architecture (without --force options, of
course).
--
Russ Allbery (r...@debian.org) http
Guillem Jover guil...@debian.org writes:
On Fri, 2012-04-20 at 16:06:19 -0700, Russ Allbery wrote:
No, that's only for source packages and indicates that the package
*can* be built on any architecture. Architecture: all in a binary
package means it can be installed on any architecture
to note that Guillem raised very good objections to my
proposed model for handling architectures. (I didn't reply because I
didn't know enough about the internal data model of dpkg to be able to
discuss it meaningfully.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
-detection
are temporary to ease the transition but should be dropped at some
point (wheezy+1, or wheezy+2).
Debian Policy should be updated to make build-arch and build-indep
mandatory targets.
B. Further discussion
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
is that there is not; if anyone
disagrees, please speak up and I'll draft a revised ballot including that
option.
If there is no other feedback, I plan to call for a vote on the above
ballot in a few days.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
heading
prgndpkg-distaddfile/prgn - adds a file to
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
to call for a vote in a few days.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ipi2n1z2
of which have
been on the mailing list.
Please, could you take your specific technical concerns to a separate
discussion and not jump into the middle of a difficult personal issue
between people you're not working closely with?
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
m...@linux.it (Marco d'Itri) writes:
On Mar 01, Russ Allbery r...@debian.org wrote:
The situation with refcounting seems much less fragile than the situation
without refcounting to me.
I totally agree.
Also, why does refcounting have to be perfect?
What would break if it did not actually
Guillem Jover guil...@debian.org writes:
On Thu, 2012-02-16 at 10:43:53 -0800, Russ Allbery wrote:
I was thinking more about this, and I was finally able to put a finger
on why I don't like package splitting as a solution.
We know from prior experience with splitting packages for large
arch
Carsten Hey cars...@debian.org writes:
* Russ Allbery [2012-02-16 14:55 -0800]:
Every file that differs has to be fixed in the current multi-arch plan.
Documentation that contains its build date is going to need to be split
out into a separate -docs package.
I doubt that ftpmaster would
made it
arch-specific later on and the maintainer didn't notice. (It's very easy
to miss.) This is particularly common with header files.
Note that arch-qualifying all of the files does not have the problems of
package splitting, but it's also a much more intrusive fix.
--
Russ Allbery (r
Carsten Hey cars...@debian.org writes:
* Russ Allbery [2012-02-16 10:43 -0800]:
* Users who want to co-install separate architectures will immediately
encounter a dpkg error saying that the files aren't consistent. This
means they won't be able to co-install the packages, but dpkg
the perspective of version mismatches between arches.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
. But this is going down exactly that complexity path that
Joey is talking about, IMO.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
--sysroot
or mini-chroots, and I don't think those are satisfying solutions to the
set of problems we're trying to solve.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe
if this is going
to make wheezy.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874nutncef.fsf
this without changing some tools. (One
should not read that as my support of this specific alternative, as I've
not decided there yet, but in general I think it's fair game to change our
tools to support multiarch.)
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
lose something from the
UI perspective. That's going to be a change historically from where we've
told users to look, and it's a little awkward. But, thinking it over, the
set of packages that we're talking about is fairly limited.
--
Russ Allbery (r...@debian.org) http
as a dependency, and
nothing else on my system uses libaudio2, I still expect to get
/usr/share/libaudio2/AuErrorDB installed.
How is that not a serious policy violation already? AuErrorDB isn't
versioned with the SONAME, so libaudio2 and libaudio3 would not be
coinstallable.
--
Russ Allbery (r
Steve Langasek vor...@debian.org writes:
On Wed, Feb 08, 2012 at 04:55:02PM -0800, Russ Allbery wrote:
Steve Langasek vor...@debian.org writes:
The unfounded assumption here is that you will always install a
foreign-arch M-A: same package together with the native-arch version.
If I install
a mistake and the packages contain different contents, but it also solves
the binNMU issue (well, solves; the changelog will randomly swap back
and forth between the packages, but I'm having a hard time being convinced
this is a huge problem).
--
Russ Allbery (r...@debian.org) http
Raphael Hertzog hert...@debian.org writes:
On Mon, 02 Jan 2012, Russ Allbery wrote:
[...]
p
fileshlibs/file files were the original mechanism for
handling library dependencies. They are documented
in ref id=sharedlibs-shlibdeps. filesymbols/file files
Russ Allbery r...@debian.org writes:
I tried sending a unified diff, but the new sections are largely
unreadable since they're intermixed with the old sections being removed.
Hence, for review purposes, here are the symbols and shlibs sections in
their entirety, followed by a diff
how the syntax definition worked and the spaces around []
weren't literal. Aie.
I'll fix.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
that it will
+be parsed as part of the entry for that library.)
And that sentence is then useless (or needs to be reworded).
Dropped.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject
not have time this weekend (which is a long holiday weekend in the US).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
Cyril Brulebois k...@debian.org writes:
Russ Allbery r...@debian.org (13/01/2012):
Yes, but there was some discussion in the Policy bug asking why shlibs
files were required when they're not used if a symbols file is present,
and while I originally argued that keeping them both made sense, I
to in the appropriate parts of the
- binary package control files.
- /p
- /sect1
-
-
sect1 id=pkg-dpkg-distaddfile
heading
prgndpkg-distaddfile/prgn - adds a file to
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
no good tool in the base installation
to handle it for you, and that's a bug that should be fixed.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-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-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zkldvf2v@windlord.stanford.edu
Package: dpkg-dev
Version: 1.16.0.3
Severity: wishlist
Most of my packages are maintained in Git, with the separate changes, if
broken out at all, broken out in separate branches with their own
history. Since the tools like TopGit for generating a patch series from
that setup are all rather
).
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87d3iy4ok3@windlord.stanford.edu
to the wrong (diverted) file.
An interesting complex example of current uses of diversions that
illustrates your point about shared libraries and a few other things may
be the libglx-nvidia-alternatives package.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
to work on catching up today.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
the same tools.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
there; it is conventional to put a
Apart from adding that fields names may not begin with #, I also changed
‘US-ASCII’ for ‘ASCII’, since this is the vocabulary used by the Policy.
Thanks, this is now applied for the next Policy release. Sorry about the
long delay.
--
Russ Allbery (r...@debian.org
of this giant patch. I think it
will be a great first step towards making maintainer script state less
confusing.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
list and then you'd get something that should
be reasonably easy to parse and would still use spaces to separate from
other fields, since the architecture list isn't too complex in syntax
other than being a list.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle
. I prefer using options,
but opinions will vary.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
there; it is conventional to put a
Apart from adding that fields names may not begin with #, I also changed
‘US-ASCII’ for ‘ASCII’, since this is the vocabulary used by the Policy.
And, for the record, seconding this combined patch. Thank you for all
your work on this!
--
Russ Allbery (r...@debian.org
(see below). Horizontal
whitespace
(spaces and tabs) may occur immediately before or after the
value and is ignored there; it is conventional to put a
single space after the colon. For example, a field might
Seconded.
--
Russ Allbery (r...@debian.org
am
preparing for clarifying the Policy's chapter about control files, in
bug #593909.
It occurred to me, on reviewing your other patch as well, that this change
should probably also say explicitly that field names may not begin with #.
--
Russ Allbery (r...@debian.org) http
.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
and unambiguously state the allowed characters for
each component.
I'm certainly OK with policy requiring field names to be ASCII.
I think that's probably the right thing to do.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ
Raphael Hertzog hert...@debian.org writes:
On Fri, 20 Aug 2010, Russ Allbery wrote:
+ p
+A package that declares the same ttconffile/tt as another,
+conflicting package may see left-over configuration files from
+that other package.
EPARSE on this sentence
Raphael Hertzog hert...@debian.org writes:
On Wed, 18 Aug 2010, Russ Allbery wrote:
What happens if you have a package on the system that's removed but not
purged and you install another package (conflicting with the first)
that contains the same conffile? I suspect the conffile
Steve Langasek vor...@debian.org writes:
On Sun, Aug 15, 2010 at 12:25:19PM -0700, Russ Allbery wrote:
I believe they can be in the same state as the pre-dependency itself
for exactly the same reasons, no? Upgrades don't require deconfiguring
packages that depend on the package being
Raphael Hertzog hert...@debian.org writes:
On Mon, 26 Jul 2010, Russ Allbery wrote:
p
The prgnDEBIAN/prgn directory will not appear in the
file system archive of the package, and so won't be installed
- by prgndpkg/prgn when the package is installed
Steve Langasek vor...@debian.org writes:
On Wed, Jul 21, 2010 at 01:52:50PM -0700, Russ Allbery wrote:
+ Sometimes, a package requires another package to be unpacked
+ emand/em configured before it can be unpacked. In this
+ case, the dependent package must specify
when the package is unpacked.
/p
p
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
of pointless for Debian.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
to
be unpacked at the same time.
/p
We do use breaking and broken elsewhere in Policy with respect to the
Breaks header, so I felt comfortable using them here.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg
Jonathan Nieder jrnie...@gmail.com writes:
Russ Allbery wrote:
I found the original awkward and hard to puzzle out. How about this:
p
Since ttDepends/tt only places requirements on the order in
which packages are configured, packages in an installation run
directory will not appear in the
file system archive of the package, and so won't be installed
- by prgndpkg/prgn when the package is installed.
+ by prgndpkg/prgn when the package is unpacked.
/p
p
--
Russ Allbery (r...@debian.org) http
Jonathan Nieder jrnie...@gmail.com writes:
Russ Allbery wrote:
I think we should hopefully be close to a final wording now.
Indeed! All I have left are copy-edits (patch below).
Thanks! Applied to my copy.
@@ -5048,7 +5132,7 @@ Provides: mail-transport-agent
Conflicts: mail-transport
is that apt calls dpkg with
some --force-* flag, or at least that's what the messages that I've seen
scroll by in this sort of situation seem to imply. I agree that it would
be good to have a better way of handling it (although also agree that's a
different bug than this one).
--
Russ Allbery (r
Thank you very much for the detailed review!
Jonathan Nieder jrnie...@gmail.com writes:
Russ Allbery wrote:
p
+ What follows is a summary of all the ways in which maintainer
+ scripts may be called along with what facilities those scripts
+ may rely on being available
Russ Allbery r...@debian.org writes:
Please review in detail, as this is the first documentation we'll have
of several hairy assumptions involved in maintainer script dependencies.
Here is an updated patch reflecting feedback from Ben Finney and Jonathan
Nieder.
diff --git a/policy.sgml b
1 - 100 of 172 matches
Mail list logo
