opportunity to come up with some guidelines so that some of the rest of us
can pitch in and start getting the bug list down to something more
reasonable.
So, any general thoughts on a bug policy? Use of confirmed / patch / etc?
Categories of bugs that we should create with usertags?
--
Russ
Uploaders.) However, I would greatly
appreciate it if you would look over Bug #148194 against debian-policy and
follow up in that bug with any concerns or problems that you have with
this change.
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
Goswin von Brederlow [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] writes:
Hello folks,
I have proposed a modification for Policy that will permit wrapping in
the following fields in debian/control:
Wouldn't it be better to require all tools to accept multi-line fields
for any
the home
page tends to be useful. Mostly people use Alioth for the Subversion
access it controls and occasionally for mailing lists.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
Bruce Sass [EMAIL PROTECTED] writes:
On Thu September 28 2006 18:14, Russ Allbery wrote:
Why would you ever use Alioth's file upload capability for a Debian
project as opposed to simply uploading the package to Debian?
I know nothing about Alioth's file upload capabilities; I was thinking
is insufficient.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
that isn't the case; I think it would be a failure
of imagination in finding a good general solution or a way of optionally
enabling a feature that would still allow Debian and Ubuntu to share the
same source.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
(and because they're often easier to
set up and reason about).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Ian Jackson [EMAIL PROTECTED] writes:
Russ Allbery writes:
Functional tests generally test some user-exposed functionality of the
package and therefore usually don't require access to anything other than
the public interface of the package. Unit tests are tests of specific
internal
, the empty part, tta/tt.
/p
p
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
~svn1245/tt
+ sorts earlier than tt1.0~beta1/tt, which sorts earlier
+ than tt1.0/tt.
+ /footnote
/p
p
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Marc 'HE' Brockschmidt [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] writes:
Here's a new version of the Policy patch for ~ in version numbers that
hopefully incorporates all of the suggestions.
You will hate me for this one :-)
Oh, it's fine. We haven't worked out how best
, although we have broken this rule elsewhere
(most notably in dependency fields, of course).
I think this is a great idea, although I can't comment on the code
implementation.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
Manoj Srivastava [EMAIL PROTECTED] writes:
How is git reconstituting the files if there is no network
access? Are they shipping all the bits needed to get a full working
dir without any network access?
As I understand it, yes, that's the basic idea.
--
Russ Allbery ([EMAIL
modifications.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
where we can use %zu, per C99, and
avoid the cast. It would certainly work on Linux.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
wishes to have a file (or
directory or other such thing) installed with owner and
permissions different from those in the distributed Debian
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
is
essentially what everyone who is using quilt or dpatch is already doing.
It's a standardization of current practice, which is always easier.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
). It is
useful in precisely those circumstances where changesets are useful
first-class objects rather than simply components in a VCS repository,
which is a different mindset than using a VCS.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
Raphael Hertzog [EMAIL PROTECTED] writes:
On Tue, 12 Feb 2008, Russ Allbery wrote:
Basically, the way to do this is to do the dbs thing, I think. The
structure of the .tar.gz file would be:
- All content in the .tar.gz file is in a debian subdirectory as packed.
- debian/patches contains
not to, when I remember, but given
the paucity of systems on which these assumptions break, most C code that
you see is not this careful.
This topic is a whole *section* in C FAQ, BTW. See:
http://c-faq.com/null/index.html
--
Russ Allbery ([EMAIL PROTECTED]) http
to ignore these comments.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Neil Williams [EMAIL PROTECTED] writes:
On Sun, 2008-05-25 at 08:40 -0700, Russ Allbery wrote:
Lots of other packages do this -- one of mine off the top of my head is
xml-security-c.
Nope. No mention of aclocal.m4 in debian/rules for that package,
just /usr/share/misc/config.guess
-establishing the diversion is the
right thing to do. I'm remembering Ian's previous comments that normally
one should not be testing the action in maintainer scripts.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
shared library without violating Policy 8.2.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of the old package is
+ run after unpacking so the removal of the diversion will fail.
/p
p
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ideas as to how to word what dpkg does, they would be
gratefully accepted.
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, be implemented in
one. Then Git would use msgmerge automatically for conflicts between *.po
files.
gitattributes(5) has the details under Defining a custom merge driver.
It looks like the only hard part would be finding the *.pot file with
which to msgmerge.
--
Russ Allbery ([EMAIL PROTECTED
Thanks for the review!
Raphael Hertzog [EMAIL PROTECTED] writes:
On Sat, 05 Jul 2008, Russ Allbery wrote:
The postrm has to do the reverse:
example
- if [ remove = $1 ]; then
+ if [ remove = $1 -o abort-install = $1 -o disappear = $1 ]; then
To be really complete we should
field to set DEB_BUILD_OPTIONS in dpkg-buildpackage
is a solution looking for a problem, IMO, and I'd rather not see that
tangled up with the much-needed problem of specifying which options a
package supports and finally dealing with the whole build-arch/build-indep
mess.
--
Russ Allbery ([EMAIL
Raphael Hertzog [EMAIL PROTECTED] writes:
On Fri, 11 Jul 2008, Russ Allbery wrote:
This doesn't make sense to me. The maintainer writes debian/rules; why
would they need to change Build-Options in debian/control to enable
anything about the build?
Because they want that anyone can easily
not then there should be no error.
The existing DEB_BUILD_OPTIONS mechanism already supports exactly these
semantics for the parallel=N option, so as long as we don't break what we
already have working, this should continue to behave appropriately and we
can add additional options for similar cases.
--
Russ
direction.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
now, I don't think most Debian Developers have any idea what the
implications of these changes are.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
thought to mention it to anyone.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
|
+ bar/tt on all other architectures.
/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
configured when postrm remove and postrm disappear
are called. Package dependencies are also always configured when postinst
configure is called unless there are circular dependencies. Then I would
just say that there are no guarantees for the other postinst, prerm, and
postrm actions.
--
Russ
to a
| debian_revision of `0'.
Policy was changed to match dpkg in April of 2007:
* Policy: better document version ranking and empty Debian revisions
Wording: Russ Allbery r...@debian.org
Seconded: Raphaël Hertzog hert...@debian.org
Seconded: Manoj Srivastava sriva...@debian.org
Seconded
portrayal
of what the source package generates. However, it means that Policy is
wrong and needs to be changed.
What should it say instead? I assume that the current language should
be retained for debian/control, but the specification for .dsc is now
different.
--
Russ Allbery (r...@debian.org
Jonathan Yu jonathan.i...@gmail.com writes:
This is probably a stupid question, but...
On Tue, May 26, 2009 at 11:33 PM, Russ Allbery r...@debian.org wrote:
Currently, Policy's description of Architecture includes the statement:
In the main debian/control file in the source package
problems and isn't clear in a few
other ways, so with that information I'll probably rewrite it completely
and try to make it clearer.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject
?
It's still special in debian/control. The usage is really different now
between all three places that Architecture may appear.
http://bugs.debian.org/530967 is my proposed new wording.
--
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-dpkg-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
, but they're
also fantastic for sharing pending security patches that cannot yet be
publicly disclosed among the co-maintainers of a package.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org
with a subject
) 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...@lists.debian.org
files, but it might be worth adding something
clarifying there. It's also worth saying something about symlinks, so
I'll open a bug on Debian Policy to document that.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-dpkg-requ
Manoj Srivastava sriva...@ieee.org writes:
On Sun, Jan 03 2010, Russ Allbery wrote:
I don't believe that listing symlinks as conffiles works properly at
the moment. See #421344. It doesn't make any sense to list a
directory as a conffile. I think that exhausts all the non-regular
files
Manoj Srivastava sriva...@ieee.org writes:
On Sun, Jan 03 2010, Russ Allbery wrote:
Symlinks in /etc pointing to files not in /etc are used now, so I'm not
sure they should be Policy violations. /etc/nologin is the canonical
example. Depending on how and whether Debian adopts upstart, we
source package. Are their changes
incorporated into my same patch with my same header?
--
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
prove isn't entirely happy with tests not written in Perl),
but probably more relevantly, it provides TAP libraries for writing tests
in C and shell.
The Automake test harness is okay, but I really like the Perl test
framework output and its test protocol.
--
Russ Allbery (r...@debian.org
may want to take a look at readelf. It's quite nice.
--
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
to objdump.
I have a hard time imagining Debian ever supporting non-ELF targets. We'd
need to maintain a completely separate libc, for instance, since I'm
fairly sure glibc is ELF only.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
Hector Oron hector.o...@gmail.com writes:
2010/4/28 Russ Allbery r...@debian.org:
[...]
I'm not sure what you mean by flat binaries here.
I meant
http://www.beyondlogic.org/uClinux/bflt.htm
Ah, thank you. I hadn't known about that.
--
Russ Allbery (r...@debian.org) http
-trivial). I may have
the opportunity to have Stanford pay me to do that packaging work sometime
this summer, but I have a lot of other things on my plate so I'm not sure
that will happen.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian
an intentional affectation to a native speaker, at least of my
dialect (Western 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
-ENTRY
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.
+ by prgndpkg/prgn when the package is unpacked.
/p
p
--
Russ
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
Jonathan Nieder jrnie...@gmail.com writes:
Russ Allbery wrote:
Jonathan Nieder jrnie...@gmail.com writes:
* postrm does not get called until pre-dependencies for the new
version are satisfied. So I think it is impossible for
pre-dependencies to be half-installed here.
I believe
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
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
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
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
(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
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
. 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
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
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
).
--
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
.
--
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
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
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
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
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
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
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
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
--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
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
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
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
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
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
1 - 100 of 171 matches
Mail list logo
