On Mon, Oct 10, 2022 at 08:50:49AM +0800, Paul Wise wrote:
> On Sun, 2022-10-09 at 18:54 +0200, David Kalnischkies wrote:
> > I suppose we could use 'foo-dbgsym Enhances foo:arch (= version)'.
>
> That sounds interesting and would be nice generally, however...
>
> > On a sidenote: What the
On Sun, 2022-10-09 at 18:54 +0200, David Kalnischkies wrote:
> I suppose we could use 'foo-dbgsym Enhances foo:arch (= version)'.
That sounds interesting and would be nice generally, however...
> On a sidenote: What the Depends ensures which the Enhances doesn't is
> that they are upgraded in
On Sun, Oct 09, 2022 at 10:26:39AM +0800, Paul Wise wrote:
> I have often wanted a different kind of relationship between packages
> and their dbgsym packages than mere Depends. Currently when a dbgsym is
> installed it keeps the library package installed even after it is no
> longer used and both
On Sat, 2022-10-08 at 11:00 +0200, Niels Thykier wrote:
> 2) We now have a debuginfod service, so you do not even have to install
> dbgsym packages anymore (if you configure gdb to use it). For the
> cases where you do install the dbgsym, you still have to manage
> inter-source
Simon McVittie:
On Sat, 08 Oct 2022 at 11:00:30 +0200, Niels Thykier wrote:
On Sat, 7 Jul 2018 11:40:54 +0300 "Yuriy M. Kaminskiy"
wrote:
I think (at least, 'Multi-arch: foreign' *and* 'Architecture' != all)
packages should have explicit parent package arch dependency
Depend: foo:${Arch}
On Sat, 08 Oct 2022 at 11:00:30 +0200, Niels Thykier wrote:
> > > On Sat, 7 Jul 2018 11:40:54 +0300 "Yuriy M. Kaminskiy"
> > > wrote:
> > > > I think (at least, 'Multi-arch: foreign' *and* 'Architecture' != all)
> > > > packages should have explicit parent package arch dependency
> > > >
Bastien ROUCARIES:
Le sam. 8 oct. 2022 à 11:00, Niels Thykier a écrit :
Hi,
[...]
2) We now have a debuginfod service, so you do not even have to install
dbgsym packages anymore (if you configure gdb to use it). For the
cases where you do install the dbgsym, you still have to
Le sam. 8 oct. 2022 à 11:00, Niels Thykier a écrit :
> Hi,
>
> I have BCC'ed debian-devel on this email to ask for input on this bug
> (#903158) and ask parties that are interested to follow up there. I am
> considering to remove the dependencies for -dbgsym packages on the
> grounds that:
>
>
Hi,
I have BCC'ed debian-devel on this email to ask for input on this bug
(#903158) and ask parties that are interested to follow up there. I am
considering to remove the dependencies for -dbgsym packages on the
grounds that:
1) They are too weak when M-A: foreign is involved and they are
Hi Niels,
On Sat, Aug 04, 2018 at 08:38:00AM +, Niels Thykier wrote:
> On Sat, 7 Jul 2018 11:40:54 +0300 "Yuriy M. Kaminskiy"
> wrote:
> > I think (at least, 'Multi-arch: foreign' *and* 'Architecture' != all)
> > packages should have explicit parent package arch dependency
> >Depend:
On Sat, 7 Jul 2018 11:40:54 +0300 "Yuriy M. Kaminskiy"
wrote:
> Package: debhelper
> Version: 10.2.5
> Severity: minor
> Tags: patch
>
> Dear Maintainer,
>
> On Multi-Arch i386+amd64 system, when I have foo:amd64 (Multi-Arch:
> foreign), I can install useless foo-dbgsym:i386 (and reverse).
>
>
Package: debhelper
Version: 10.2.5
Severity: minor
Tags: patch
Dear Maintainer,
On Multi-Arch i386+amd64 system, when I have foo:amd64 (Multi-Arch:
foreign), I can install useless foo-dbgsym:i386 (and reverse).
I think (at least, 'Multi-arch: foreign' *and* 'Architecture' != all)
packages
12 matches
Mail list logo
