Hi, I am filing this as a minor report because reading another package's configuration might be controvrsial, I still would find it helpful. I am using gbp to build my packages, and have set [buildpackage] export-dir=../build-area tarball-dir=../tarballs because I'd like to have the parent directory clean. debmake --tar places the generated tar files in the parent directory, where gbp doesn't find them. I am wondering whether it would be a good idea if debmake would honor gbp's configuration in this case. Greetings Marc
Hi, This is my response to your BTS report: I am trying to reduce non-essential features as much as possible. As you noticed, reading another package's configuration is risky path towards over-complicating this code. * There are many places to place such configuration option. * Parser is non-trivial. * There may be similar another packages which needs to be checked if we atart doing this So, if I ever address your needs, I prefer to add an new option to pass download path for debmake itself. That still seems to be complicating code. Of course, if you bother to write a clean path to implement such a feature, I will consider including it. So I mark this as moreinfo I think it is easier for you to write a simple shell wrapper of debamke to address your need, for now. If you send me such example, I will include it to README.Debian. Osamu
Hi, This is my response to your BTS report: I am trying to reduce non-essential features as much as possible. As you noticed, reading another package's configuration is risky path towards over-complicating this code. * There are many places to place such configuration option. * Parser is non-trivial. * There may be similar another packages which needs to be checked if we atart doing this So, if I ever address your needs, I prefer to add an new option to pass download path for debmake itself. That still seems to be complicating code. Of course, if you bother to write a clean path to implement such a feature, I will consider including it. So I mark this as moreinfo I think it is easier for you to write a simple shell wrapper of debamke to address your need, for now. If you send me such example, I will include it to README.Debian. Osamu
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.
debmake run in /path/to/project/ creates following files and directories in /path/to * package-version/ * package-version.tar.xz * package_version.orig.tar.xz (symlink) So if you wish to keep parent directory clean, you need to do it with a wrapper along. * copy entire source project/ to ../build-area/debmake/project/ * run debmake in ./build-area/debmake/project/ * open interactive subshell to edit source * commit changes as needed * copy ./build-area/debmake/project-version.tar.?z to ./tarballs Let's not make debmake too complicated. Osamu
debmake run in /path/to/project/ creates following files and directories in /path/to * package-version/ * package-version.tar.xz * package_version.orig.tar.xz (symlink) So if you wish to keep parent directory clean, you need to do it with a wrapper along. * copy entire source project/ to ../build-area/debmake/project/ * run debmake in ./build-area/debmake/project/ * open interactive subshell to edit source * commit changes as needed * copy ./build-area/debmake/project-version.tar.?z to ./tarballs Let's not make debmake too complicated. Osamu
Sorry, this bug was not closed by 5.1.5 upload. I will fix this soon.
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 1003106@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Osamu Aoki <osamu@debian.org> (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 ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Sat, 14 Feb 2026 13:07:12 +0900 Source: debmake Architecture: source Version: 5.1.5 Distribution: unstable Urgency: medium Maintainer: Osamu Aoki <osamu@debian.org> Changed-By: Osamu Aoki <osamu@debian.org> Closes: 1003106 Changes: debmake (5.1.5) unstable; urgency=medium . * Proof shell code for quotation (Closes: #1003106) Checksums-Sha1: 1089871dafcd696917e725e8bd2ecf60d62b6477 1787 debmake_5.1.5.dsc 551e3f89390e2f39862a6c45c061c3f4b96c2e15 52108 debmake_5.1.5.tar.xz Checksums-Sha256: 04194cd8b45a2ccbc542f16da6d0f8b4e3cced5fdd035a8eb9a8216087ecc21d 1787 debmake_5.1.5.dsc 4e317bbc8ef146019e4070276a5a4715c0299d5f39c8d2c59fc71539d494cbf4 52108 debmake_5.1.5.tar.xz Files: c7a7cd25aa670349e52e4ce429456892 1787 devel optional debmake_5.1.5.dsc 88633ec8c0e879167eb8acf47cf4b2ef 52108 devel optional debmake_5.1.5.tar.xz -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAmmP/jERHG9zYW11QGRl Ymlhbi5vcmcACgkQHhNWiB3Y15GVnhAAt7dcEBGDmjwpQQVe6ngYPZjZezJFfn8W L1MXHt8vEGyXDmW2MivXo0LTcHfYcN7FBJe4KIF8EcwMNZiH/3JmszvHZA43ZiKi 2izhQdbOg3F+nZMAvAkloNFNRAxgrbHeAIExXj2kLXbVj3L9YL0rEPpgIGcI9tjL YgNHIQEsEz8iwvbM4IyFA/Q3sY4T/mptF696qkg87BJo9OxksPPSGmf9hA/Q1rZG LqL/eKYlGXdYJ+l+TEqZjJ11xarryttRJqDzoZsiZ0upZqJlzDZ2BasR09svVKCU FxrIhTiJIA6R/nzUwmvjGCfc/wmEQrJD06FEQjhhRvY8DSsl5MGwgmYYmUloM8YC QPXYapffko2e4lPRUOwlP/TW65zmRori1tbNLJt7wi5wrfizDF1ceDdMD2Ioy+1X TxcCIPmNiBaIE4Igr4pfyYODONsG+/M/sXOIhkIIsEAmwFSQJLyL3Avfe0eCCg0A czaP+GpBQMSzxKLU+yqXQP3DoizqGFajFH+24oWtc/NZ17jbqrzdmygJdPFQTRzn sG6YYZHAMCKpeuUanS8qErURr9KI6Ps68+oCCP87Qy4r7q5LW4kLZoIKBgESNRRQ UDrruVjgK2afCGqcfXGVif733Isx62zBroMbcE0jZcxk4QQr+1zvp363V1Xi9TCe 1vodFlnANHQ= =kYIQ -----END PGP SIGNATURE-----