public inbox for [email protected]  

help / color / mirror / Atom feed

From: Devrim Gündüz <[email protected]>
To: Marcin Cieslak <[email protected]>
Cc: [email protected]
Subject: Re: Empty %files file debugsourcefiles.list
Date: Wed, 23 Apr 2025 11:19:20 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Hi,

On Wed, 2025-04-23 at 06:38 +0000, Marcin Cieslak wrote:
> I found the problem. In short, the problem are symbolic links in the
> repository.
> They not only confuse the shell but also the debugedit utility
> does not list the source files, because the path provided by the
> compiler
> is in some other directory.
> 
> When I 'make rpm17' in the pgrpms/redhat/17/postgresql-17/F-41
> directory
> debugedit gets -b option that looks like
> 
> /home/saper/src/pgrpms/rpm/redhat/17/postgresql-17/F-41/postgresql17-
> 17.4-build/postgresql-17.4
> 
> but there are no files with that path, all source files are in
> 
> /home/saper/src/pgrpms/rpm/redhat/main/non-common/postgresql-17/F-
> 41/postgresql17-17.4-build/postgresql-17.4
> 
> and therefore debugedit finds zero files to list.

Thanks for the analysis -- but please note that we don't have this
problem on the buildfarm instances which have the same symlinks.

> 
> A somewhat related question, what is the purpose of
> 
> --define "_buildrootdir $(HOME)/rpm17/BUILDROOT"
> 
> does it do anything? (it does not seem to have any affect for me)

I've written the initial version of those makefiles about 15 years ago.
Cannot remember the details but I think I explicitly defined everything
statically so that even the distro changes a default, we are not
affected (hopefully). It is the same with _specdir, _builddir and etc.

Regards,

-- 
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
BlueSky: @devrim.gunduz.org , @gunduz.org


Attachments:

  [application/pgp-signature] signature.asc (858B, 2-signature.asc)
  download

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Empty %files file debugsourcefiles.list
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox