On Mon, Jul 17, 2023 at 11:10:52AM +0100, Simon McVittie wrote:
> > I wonder what's the point of B-D-Arch And B-D-Indep then?
>
> The point is the same as it always was: primarily to exclude large
> dependencies from a `dpkg-buildpackage -B` build chroot (like the official
> buildd for each archit
Quoting Simon McVittie (2023-07-17 12:10:52)
> On Mon, 17 Jul 2023 at 08:57:51 +, Holger Levsen wrote:
> > On Sun, Jul 16, 2023 at 11:41:36AM +0100, Simon McVittie wrote:
> > > On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote:
> > > > due to Build-Depends
> > > > being inadequate (per
On Mon, 17 Jul 2023 at 08:57:51 +, Holger Levsen wrote:
> On Sun, Jul 16, 2023 at 11:41:36AM +0100, Simon McVittie wrote:
> > On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote:
> > > due to Build-Depends
> > > being inadequate (per the Policy, B-D-Indep are _not_ necessarily
> > > inst
Hi Adam,
On Sun, Jul 16, 2023 at 12:03:00AM +0200, Adam Borowski wrote:
> Here's a raw list of packages that fail to build their source (ie,
> "dpkg-buildpackage -S"). Usually, this is either due to Build-Depends
> being inadequate (per the Policy, B-D-Indep are _not_ necessarily
> installed), or
On Sun, Jul 16, 2023 at 11:41:36AM +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote:
> > due to Build-Depends
> > being inadequate (per the Policy, B-D-Indep are _not_ necessarily
> > installed)
> For completeness, B-D-Arch are not guaranteed to be installed
On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote:
> due to Build-Depends
> being inadequate (per the Policy, B-D-Indep are _not_ necessarily
> installed)
For completeness, B-D-Arch are not guaranteed to be installed during
clean either. Similarly, Build-Conflicts are guaranteed to be abs
6 matches
Mail list logo
