Hi Guillem,
Guillem Jover wrote:
> > A maybe a bit safer variant would be to call dpkg-checkbuilddeps
> > beforehand and filter out build-essential if it appears. That way
> > around it should hurt way less to hardcode the package name.
>
> You can simply use --ignore-builtin-builddeps. :)
Hi!
On Tue, 2020-05-26 at 17:59:33 +0200, Axel Beckert wrote:
> Johannes Schauer wrote:
> > And I got the same error as Otto ("Unmet build dependencies:
> > build-essential:native")
> One idea was to add some logic to automatically decide if we can use
> dpkg-buildpackage or not and if not, fall
Hi josch,
Johannes Schauer wrote:
> > If it's similar as with mk-ci-build-deps above, this is likely a bug in
> > mk-build-deps then, just triggered by equivs.
>
> Again, I don't want to be confrontational here.
Ok. Already forgotten. :-)
> I don't understand as much
> about equivs as you do.
Quoting Otto Kekäläinen (2020-05-26 15:56:04)
> Yes, installing build-essential manually has been the work-around I've
> been using. So that is now the permanent solution?
No, I think that now that equivs always uses dpkg-buildpackage instead of
manually invoking debian/rules it *must* depend on
Yes, installing build-essential manually has been the work-around I've
been using. So that is now the permanent solution?
Hi Otto,
On Tue, 21 Apr 2020 21:54:57 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> I noticed my builds started failing today with error message:
>
> Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i
> control -t 'apt-get -y -o Debug::pkgProblemResolver=yes
>
Hi Axel,
Quoting Axel Beckert (2020-05-07 15:45:12)
> > bisection finished successfully
> > last good timestamp: 2020-04-19 06:52:31.476563+02:00
> > first bad timestamp: 2020-04-19 10:35:09.156250+02:00
> > only one package differs: equivs is the culprit
> Yeah, but we know
Hi Josch,
thanks for bringing this to my attention. It seems as if I have
overseen Otto's bug report wen it came in two weeks ago. (Sorry,
Otto.)
Johannes Schauer wrote:
> Otto Kekäläinen wrote:
> > I am pretty sure this is related to the recent equivs 2.3.0 release,
> > but I have not figured
Control: severity -1 grave
On Tue, 21 Apr 2020 21:54:57 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> I noticed my builds started failing today with error message:
>
> Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i
> control -t 'apt-get -y -o
Package: equivs
Version: 2.3.0
I noticed my builds started failing today with error message:
Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i
control -t 'apt-get -y -o Debug::pkgProblemResolver=yes
--no-install-recommends'
---> Running in 912092c7ebbd
dpkg-buildpackage:
10 matches
Mail list logo
