Your message dated Mon, 19 Jan 2026 03:48:36 +0000
with message-id <[email protected]>
and subject line Bug#1090070: fixed in debmake 5.0.0
has caused the Debian Bug report #1090070,
regarding debmake: Allow use of debmake to update existing packages instead of
only creating new ones
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.)
--
1090070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090070
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debmake
Version: debmake/4.5.1-1
Severity: wishlist
Debmake creates a lot of useful template files, and has a bunch of
automation to ensure debian/control etc are correct. List of files
debmake creates on default setting currently:
README.Debian
README.source
changelog
clean
control
copyright
dirs
entr.bug-control.ex
entr.bug-presubj.ex
entr.bug-script.ex
entr.conffiles.ex
entr.cron.d.ex
entr.cron.daily.ex
entr.cron.hourly.ex
entr.cron.monthly.ex
entr.cron.weekly.ex
entr.default.ex
entr.emacsen-install.ex
entr.emacsen-remove.ex
entr.emacsen-startup.ex
entr.lintian-overrides.ex
entr.service.ex
entr.tmpfile.ex
gbp.conf
install
links
maintscript.ex
manpage.1.ex
manpage.asciidoc.ex
manpage.md.ex
manpage.sgml.ex
manpage.xml.ex
patches
postinst.ex
postrm.ex
preinst.ex
prerm.ex
rules
salsa-ci.yml
source
tests
upstream
watch
Debmake also has commands such as --judge that can be used to update
build dependencies, and --kludge for updating copyright info.
Much of this is useful not only when creating new packages, but also
when maintaining existing packages (e.g. after new upstream release).
Perhaps debmake could have some kind of --update or --validate flag
that could run some of apply some of its logic to update existing
pacakges?
--- End Message ---
--- Begin Message ---
Source: debmake
Source-Version: 5.0.0
Done: Osamu Aoki <[email protected]>
We believe that the bug you reported is fixed in the latest version of
debmake, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Osamu Aoki <[email protected]> (supplier of updated debmake package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 16 Jan 2026 22:59:08 +0900
Source: debmake
Architecture: source
Version: 5.0.0
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki <[email protected]>
Changed-By: Osamu Aoki <[email protected]>
Closes: 924658 1090069 1090070 1124821
Changes:
debmake (5.0.0) unstable; urgency=medium
.
* black+isort
* Remove unused code and data
* Rename scanfiles.py -> scanext.py
* Reorganize template files in data/*
* Refactor src/debmake/*.py (Closes: #1090069, #924658, #1090070, #1124821)
* Update packaging and documentation
Checksums-Sha1:
c2408bfc33f1dc79756c750fc66da333adce4d53 1787 debmake_5.0.0.dsc
7c2e7d53492d5e871cd2dac4ab6a7b275853379a 54544 debmake_5.0.0.tar.xz
Checksums-Sha256:
b5456557d109da5851acc6ecd353511f4ceb037d1db6d0a5745b94c16bb6e68a 1787
debmake_5.0.0.dsc
254213352b315befd2718399a5e0a257aafb7223a453fc09fb7317be721231cf 54544
debmake_5.0.0.tar.xz
Files:
5308bc2b18299860e4fa99dd6934533b 1787 devel optional debmake_5.0.0.dsc
ca087802b85163c305da9d145a5160c8 54544 devel optional debmake_5.0.0.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAmltpVcRHG9zYW11QGRl
Ymlhbi5vcmcACgkQHhNWiB3Y15HLWg//ejV91Y/5T9VxKsez+KbsGtjhq2bwFQVm
7gi2l1uyaAm+fCdK0kfldPyBVwZH1pVmcfnwriWpJcOIEqWI1WBiM27lVt7tQS8e
MQ3NlfAKVRM6ITLwXDSwIVQSbTXPASZCAtDLz+Pl46nnQsS9hpTnlN6yz8aGQ/1g
nzkqiKBOojwIS05Ld3Py5/2AR7MmqDZG50BO/QjkJXbdWO+VjoosVb1DCV7e/AUp
NwTnLM4bD9LtTA8zykhjH+fgVc2P0ejbJPFBAJu20Q6uxA5RLLtfKfb0+WnFQnxQ
CCn7XDOoVlyjQq0G/XXlA8TcpZ3Yst5qZb76Tmyb1KxF341WGzE+sbD4FbrxOmNI
aASNFvZjEel8+55Z+hVnAaY3vjTIHwjSFIflq/X1tlgFxHxeT4tW5R3yvlYg9qLR
OSATxNv+XcTYgJI5dh1YSDG1OfY6kpC0R/QRq8t8JatxESfWrFGuL3/Aq9x4I7o/
shKlp2WGCewJDMdE6t/siEpcn/y4G9ki46AaKvujX632Pzf/oUKtRwZ0C3bD1UD/
FVOKZbMo7gr2wsat3EyonS4AwV+JaCQzLFjatHlPgewH8w2u8svIeu7HjnzT80xF
FIKC6K7jzcRN8lXno3yusJcGB5XEU6vjZSXxpY4gJRwMlJHZFNOh3FiFfbWGOEyZ
9SxxF+qBLp0=
=Z0cv
-----END PGP SIGNATURE-----
pgpPvJ_14SJbv.pgp
Description: PGP signature
--- End Message ---
