On Wed, 11 Nov 2009 04:14:49 +0100, Frank Ch. Eigler wrote:
(It could be handled by suffixing the arch in the source-tree-name part.)
...
Considering that the same files are also linked into multilib-safe
collision-free /usr/lib/debug/.build-id files, where debuggers already
know to look for
Jan Kratochvil wrote:
On Tue, 10 Nov 2009 22:15:47 +0100, Björn Persson wrote:
Generated files can be placed in separate subdirectories, for example
/usr/src/debug/source tree name/%{_arch}.
My patch uses there:
/usr/src/debug/name-version-release.arch
Duplicating the entire source tree
=?iso-8859-15?q?Bj=F6rn_Persson?= bj...@xn--rombobjrn-67a.se writes:
debuginfo packages cannot be multilib, that is why we don't offer them
multilib.
I'm guessing that we don't offer them multilib means that 32-bit
debuginfo packages aren't meant to be installed on 64-bit systems,
so I'll
Frank Ch. Eigler (f...@redhat.com) said:
I'm guessing that we don't offer them multilib means that 32-bit
debuginfo packages aren't meant to be installed on 64-bit systems,
so I'll take this to mean that I shouldn't bother doing anything to
avoid conflicts.
Well, hold on, debuginfo for
On Tue, Nov 10, 2009 at 02:25:16PM -0500, Bill Nottingham wrote:
Frank Ch. Eigler (f...@redhat.com) said:
I'm guessing that we don't offer them multilib means that 32-bit
debuginfo packages aren't meant to be installed on 64-bit systems,
so I'll take this to mean that I shouldn't bother
Bill Nottingham wrote:
Frank Ch. Eigler (f...@redhat.com) said:
I'm guessing that we don't offer them multilib means that 32-bit
debuginfo packages aren't meant to be installed on 64-bit systems,
so I'll take this to mean that I shouldn't bother doing anything to
avoid conflicts.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Björn Persson wrote:
I think can handle those. For true source code files there is no problem,
because they will be identical in both packages. Generated files can be
placed
in separate subdirectories, for example
/usr/src/debug/source tree
Jakub Jelinek ja...@redhat.com writes:
[...]
Well, hold on, debuginfo for multilib'd libraries like glibc should be
absolutely installable in parallel.
Not unless someone changes the layout of debuginfo entirely, as they
use common paths:
/usr/src/debug/source tree name
Right, that's
Hello, could someone help me understand the rules about file conflicts and
debuginfo packages?
I thought there was a rule that if the 32-bit and 64-bit versions of a package
provide the same file, then the file's contents must be identical in both
packages, with an exception for binary
On Tue, 2009-11-10 at 00:01 +0100, Björn Persson wrote:
I don't see that I as a packager can do anything to prevent these conflicts.
Shall I conclude that I don't need to care about conflicts between
architecture
versions of debuginfo packages? Or shall I try to avoid conflicts in
10 matches
Mail list logo
