Your message dated Wed, 08 Apr 2026 07:06:54 +0000
with message-id <[email protected]>
and subject line Bug#1132889: Removed package(s) from unstable
has caused the Debian Bug report #202385,
regarding Configuration variable to load modules instead of using include
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 [email protected]
immediately.)


-- 
202385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cdbs
Version: 0.4.4
Severity: wishlist

First of all, cdbs is really cool, thanks for making it :)

I have a suggestion for the way classes/modules are included.  Instead
of including the modules for every file, define a variable similar to
DEB_BUILD_OPTIONS that contains the list of modules to load, and then
use a single include line:

  include /usr/share/cdbs/1/rules/debhelper.mk
  include /usr/share/cdbs/1/class/autotools.mk
  include /usr/share/cdbs/1/rules/simple-patchsys.mk

becomes for example:

  CDBS_MODULES=debhelper,autotools,simple-patchsys
  include /usr/share/cdbs/1/rules/buildcore.mk

And in buildcore, or even another file if you prefer, you create stanzas
such as:

  ifneq (,$(findstring debhelper,$(CDBS_MODULES)))
    include $(_cdbs_rules_path)/debhelper.mk
  endif

  ifneq (,$(findstring autotools,$(CDBS_MODULES)))
    include $(_cdbs_class_path)/autotools.mk
  endif

  ifneq (,$(findstring debhelper,$(CDBS_MODULES)))
    include $(_cdbs_rules_path)/simple-patchsys.mk
  endif

This should make it easier to write rules files (if cdbs didn't make it
easy enough already :), and I think will prevent some potential
problems:

 * Because you get to decide in which order the files are included, you
   prevent users from forgetting to do this:
     Incidentally, you should usually include debhelper.mk first, before
     other rules.  This will turn on optional Debhelper-using parts of
     other rules, if any, which is usually what you want. (README.gz)

   So future changes of such requirements can be implemented more
   transparently to the users, because the complete list of modules is
   available from the start. 

 * The version-specific subdirectory is only declared once in the user
   rules file, so you can't get inconsistencies like this:

  include /usr/share/cdbs/1/rules/debhelper.mk
  include /usr/share/cdbs/2/class/autotools.mk

Chris



--- End Message ---
--- Begin Message ---
Version: 0.4.182+rm

Dear submitter,

as the package cdbs 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/1132889

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
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to