Your message dated Mon, 13 Jun 2022 21:47:04 +0200 with message-id <20220613194704.4dqhhg3n7afxiaap@crossbow> and subject line Re: empty Build-Depends-Indep in debhelper errors has caused the Debian Bug report #1012764, regarding empty Build-Depends-Indep in debhelper errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1012764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012764 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: empty Build-Depends-Indep in debhelper errors
- From: Mark Esler <mark.esler@canonical.com>
- Date: Mon, 13 Jun 2022 11:26:13 -0500
- Message-id: <CAJ=HsV+G2R8dPuaaWunpGLjqsKKTQrThOXr5GawnjryecmBPXg@mail.gmail.com>
Package: dehhelper Version: 13.6ubuntu1 In the debian/control file setting Build-Depends-Indep to nothing or whitespace will cause a build failure. dh appears unable to parse an empty Build-Depends-Indep list: E: Problem parsing dependency: Build-Depends-Indep E: Unable to get build-dependency information for gccgo-6 ERROR: Something went wrong with automatic dependency resolution. I am using Ubuntu 22.04, kernel 5.15.0-30-generic, with debhelper 13.6ubuntu1. Mark
--- End Message ---
--- Begin Message ---
- To: 1012764-done@bugs.debian.org, Mark Esler <mark.esler@canonical.com>
- Cc: Niels Thykier <niels@thykier.net>
- Subject: Re: empty Build-Depends-Indep in debhelper errors
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Mon, 13 Jun 2022 21:47:04 +0200
- Message-id: <20220613194704.4dqhhg3n7afxiaap@crossbow>
- In-reply-to: <[🔎] f910031b-fd6c-a6f6-7001-1075ba734ce7@thykier.net>
- References: <CAJ=HsV+G2R8dPuaaWunpGLjqsKKTQrThOXr5GawnjryecmBPXg@mail.gmail.com> <CAJ=HsV+G2R8dPuaaWunpGLjqsKKTQrThOXr5GawnjryecmBPXg@mail.gmail.com> <[🔎] f910031b-fd6c-a6f6-7001-1075ba734ce7@thykier.net>
On Mon, Jun 13, 2022 at 07:04:03PM +0200, Niels Thykier wrote: > > dh appears unable to parse an empty Build-Depends-Indep list: > > > > E: Problem parsing dependency: Build-Depends-Indep > > E: Unable to get build-dependency information for gccgo-6 > > ERROR: Something went wrong with automatic dependency resolution. > > > > I am using Ubuntu 22.04, kernel 5.15.0-30-generic, with > > debhelper 13.6ubuntu1. I assume the later mail mentioning debhelper 9.20160115ubuntu3 – why would that version be used in a 2022 release – and gccgo-6 – which was removed from Debian unstable more than 3 years ago – is a better indication of the release window we are talking about being somewhere in 2016 or 2017 rather than the claimed 2022. > However, none of those error messages are from debhelper. A codesearch > finds the second line in apt, so @deity tag you are it. Back in 2017 I wrote "allow empty build-dependency fields in the parser" https://salsa.debian.org/apt-team/apt/-/commit/7ea3c67f96e3bc82f86afe72d6c61308c92de515 That would explain why with a ~2016 release something like that would fail with apt being involved. As the example package from #875363 existed in the archive I suppose other tools (like debhelper) were more accepting even back then through. At least I believed that back then as I mention this in the commit message… On a slightly related note: Earlier last year "Allow superfluous commas in build-dependency lines" https://salsa.debian.org/apt-team/apt/-/commit/d7e3d28412c5269276d8d7cd72427ab88ee3e3d1 That is all about 'apt build-dep .' through which ist mostly done by humans. Official build infrastructure uses still mostly temporary packages to achieve the same thing… and in those these values would indeed be unsupported as its the task of the tool creating the dummy package + archive and so on to clean fields then. So, could it be that you use some (own) tool which doesn't and feeds bad data to apt? (The provisioning Niels quoted is for debian/control files, not for DEBIAN/control inside binary packages or stanzas in Packages and Sources files… those aren't written by hand, so a nice clean machine readable format is assumed and expected for speed reasons.) I am closing this bugreport hence as the provided information is at best misleading and certainly not helping in identifying a culprit. While e.g. the "E:" lines are certainly from apt, apt isn't really involved with debhelper and neither prints "ERROR: Something went wrong with automatic dependency resolution." Feel free to reopen or report a new bug if you can provide details about how to reproduce your problem. The more details the better as if this problem is fixed you will still need a compelling case for having it backported… Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---