On Tue, Feb 9, 2021 at 9:16 PM Simon Lees
On 2/10/21 4:18 AM, L A Walsh wrote:
On 2021/02/09 05:34, bugzilla_noreply@suse.com mailto:bugzilla_noreply@suse.com wrote:
Richard Brown mailto:rbrown@suse.com changed bug 1180367 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367 <http://bugzilla.opensuse.org/show_bug.cgi?id=1180367 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367> What Removed Added Status REOPENED RESOLVED CC rbrown@suse.com mailto:rbrown@suse.com Resolution --- INVALID
*Comment # 7 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367#c7 <http://bugzilla.opensuse.org/show_bug.cgi?id=1180367#c7 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367#c7> on bug 1180367 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367 <http://bugzilla.opensuse.org/show_bug.cgi?id=1180367 https://bugzilla.opensuse.org/show_bug.cgi?id=1180367> from Richard Brown mailto:rbrown@suse.com *
Due to the following reasons, this bug is INVALID
1) Title is factually incorrect - complete sources are shipped. This alone makes this bug INVALID.
--- The rpms are supposed to include the source needed to regenerate a package. Using the source rpm for a specific binary doesn't allow for generation. Thus the claim that the complete sources for generating a given binary package. That users cannot generate a given binary rpm from the source rpm has been been noted by others on the public lists.
The source rpm's should include all the source needed to regenerate a package, under the right environment which involves a version of rpm that is new enough, and having the right macro's / defines for leap you can find them here https://build.opensuse.org/projects/openSUSE:Leap:15.2/prjconf I guess someone could make an argument that the project config could go in source rpm's however this would make it harder to rebuild a source rpm for a different distro.
Actually, we should be migrating macros and definitions from the OBS prjconf into packages. Most macros defined in the prjconf *are* already migrated to macros packages, with the notable exception of the release macros (%suse_version, %sle_version, etc. which should be in openSUSE-release or rpm-config-SUSE) and the compiler macros (which should be in rpm-config-SUSE). When I first created rpm-config-SUSE, I *had* migrated these into that package[1][2][3], but that work was not carried over by the final version of the package that was shipped into openSUSE. Part of the reason I had done that migration was to enable doing builds of distribution packages properly *without* being connected to the openSUSE Build Service. As it stands today, you actually *cannot* build packages in openSUSE the same way they're done in OBS because the compiler macro definitions are not available in the distribution itself. This was particularly a problem for me when I tried to do CI or test builds of packages (which would be outside of OBS). I would like to have this fixed someday before SUSE Linux Enterprise 16 is branched from Tumbleweed, but I don't know if I want to push that boulder up that mountain again... [1]: https://github.com/openSUSE/rpm-config-SUSE/blob/neal/macros.d/suse_dist_mac... [2]: https://github.com/openSUSE/rpm-config-SUSE/blob/neal/suse/macros [3]: https://github.com/openSUSE/rpm-config-SUSE/blob/neal/suse/rpmrc -- 真実はいつも一つ!/ Always, there's only one truth!