[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1079185: marked as done (wine-development: Removes and generates debian/control at build time)

Your message dated Sat, 24 May 2025 18:38:30 +0000
with message-id <[🔎] E1uItlO-000Thk-4E@fasolo.debian.org>
and subject line Bug#1103851: Removed package(s) from unstable
has caused the Debian Bug report #1079185,
regarding wine-development: Removes and generates debian/control at build time
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.)


-- 
1079185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079185
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: wine-development
Source-Version: 8.21~repack-1
Severity: important

Hi!

This package regenerates the debian/control file on each build, from my
reading of the archive https://ftp-master.debian.org/REJECT-FAQ.html,
this is not allowed.

I realize the regeneration is supposed to not change the content of
the file unless the packaging is for stable or development source
packages. But the above would still seem to apply.

In, practical terms this is causing the following error:

  ,---
  /usr/bin/make -f debian/rules debian/control
  make[2]: Entering directory '/tmp/bd/wine-9.0~repack'
  dpkg-buildapi: error: cannot read debian/control: No such file or directory
  /bin/sh: 1: test: Illegal number: 
  sed "s/VERSION//g;s/DEBSUFFIX/-stable/g" < debian/control.in > debian/control
  `---

Because the debian/control file gets removed before it gets
regenerated. Besides the regeneration issue, I think the control file
should not be removed.

I think, that the current handling might have multiple intents. One
perhaps to generate the debian/control file from debian/control.in if
the former is missing, this can be accomplished as of now with a make
target. Then there is the generation of the file depending on the
source, but that should not change often, or when it changes would be
due to changes in control.in, which would trigger the usual target as
well, but a new target could be created as well to forcibly touch the
source and then depend on the usual target. And finally, perhaps as a
check to make sure that the file always contains the expected result.
For this latter case I guess adding a new target that generates the
file as a temporary, and compares against the canonical
debian/control, and then fails if there's any difference, would
accomplish the check, while not generating it.

Thanks,
Guillem

--- End Message ---
--- Begin Message --- 
Version: 8.21~repack-1+rm

Dear submitter,

as the package wine-development has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1103851

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---
Reply to: