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
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will
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 Sat, Oct 08, 2022 at 03:42:59PM +0100, Simon McVittie wrote:
> I was under the impression that the Debian archive does not allow
> dependencies with an explicit architecture like this, only the :any
> qualifier for M-A: allowed packages (like python3:any).
"allow" is a strong word especially
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
> > > >
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
9 matches
Mail list logo
