From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject: Re: [PATCH 0/8] debian: Mitigate bulk of Lintian issues
Date: Sun, 11 Jul 2021 20:21:54 +0300 [thread overview]
Message-ID: <CA+sCei32VnZeb01xXmiNc5-yr01P36GEuXdHP6pwUgEVR+5PGA@mail.gmail.com> (raw)
In-Reply-To: <C9C7CCD4-5D71-4E08-9C9C-A34AA803100F@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Tue, May 11, 2021 at 12:41 PM Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> I have attached the log files of the build on my machine using the build scripts provided with the package.
>
> Hopefully they have what you are looking for.
Regarding the 'no binaries'/empty location-importer package - that
still seems to be a problem with the 0.9.7 release visible on
packages.ipfire.org. They only contain changelog.Debian.gz and
copyright for all architectures.
This doesn't feel like it should be environment specific, as it
invokes a chroot. I am not able to reproduce this (running the
debian/build.sh) on my Ubuntu Focal (20.04) installation, which runs
the buster target, and produces a location-importer package with a
usr/bin/location-importer and other files.
Is the build environment itself up-to-date? Any available updates for
sbuild, or any other tooling on the host by any chance?
Will have to spin up a Debian Buster VM to test this out then. I have
some sneaking suspicion that buster-backports might be beneficial to
enable on the host.
--Valters
next parent reply other threads:[~2021-07-11 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C9C7CCD4-5D71-4E08-9C9C-A34AA803100F@ipfire.org>
2021-07-11 17:21 ` Valters Jansons [this message]
2021-07-14 16:33 ` Michael Tremer
2021-04-16 13:06 Valters Jansons
2021-04-19 13:10 ` Michael Tremer
2021-04-27 9:28 ` Valters Jansons
2021-05-04 14:50 ` Michael Tremer
2021-05-04 18:40 ` Valters Jansons
2021-05-06 15:12 ` Michael Tremer
2021-05-06 17:37 ` Valters Jansons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+sCei32VnZeb01xXmiNc5-yr01P36GEuXdHP6pwUgEVR+5PGA@mail.gmail.com \
--to=valter.jansons@gmail.com \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox