Dear all, not sure if this bug fix is just about dh_make or the full process to make a package for Launchpad that is documented on the Ubuntu documentation.
The former now works, the latter still fails further down the process.
Here is what now works:
$ bzr dh-make 1fichierfs 1.9.2~Focal /tmp/1fichierfs.tar
Fetching tarball
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
Type of package: (single, indep, library, python)
[s/i/l/p]?
Maintainer Name : ....
Email-Address : ....@....fr
Date : Thu, 26 May 2022 13:50:43 +0200
Package Name : 1fichierfs
Version : 1.9.2~Focal
License : blank
Package Type : single
Are the details correct? [Y/n/q]
Skipping creating ../1fichierfs_1.9.2~Focal.orig.tar.gz because it already exists
Currently there is not top level Makefile. This may require additional tuning
Done. Please edit the files in the debian/ subdirectory now.
(Note the "missing" warning is not an issue, that is because I purposefully removed these files that I didn't fill with useful information so far)
You can notice here that there is no "compat" file although I provided one in the debian directory.
echo 10 >debian/compat
Then further it seems to complain for compatibility level:
$ bzr builddeb -- -us -uc
Building using working tree
Building package in merge mode
Looking for a way to retrieve the upstream tarball
Using the upstream tarball that is present in /tmp/build
Building the package in /tmp/build/build-area/1fichierfs-1.9.2~Focal, using debuild -us -uc
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: paquet source 1fichierfs
dpkg-buildpackage: info: version source 1.9.2~Focal-1
dpkg-buildpackage: info: distribution source focal
dpkg-buildpackage: info: source changé par .... <...@...fr>
dpkg-source --before-build .
dpkg-buildpackage: info: architecture hôte amd64
fakeroot debian/rules clean
dh clean
dh: error: Please specify the compatibility level in debian/compat
make: *** [debian/rules:18 : clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed
brz: ERROR: The build failed.
This was working as of 16.04, although it seemed to use compatibility level 9, and nowadays this seems obsolete.
What am I doing wrong (which is then probably missing in the documentation)?
Or is there something broken elsewhere with "compat" not being committed although it is present?
Dear all, not sure if this bug fix is just about dh_make or the full process to make a package for Launchpad that is documented on the Ubuntu documentation.
The former now works, the latter still fails further down the process.
Here is what now works:
$ bzr dh-make 1fichierfs 1.9.2~Focal /tmp/1fichierfs.tar 1.9.2~Focal. orig.tar. gz because it already exists
Fetching tarball
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
Type of package: (single, indep, library, python)
[s/i/l/p]?
Maintainer Name : ....
Email-Address : ....@....fr
Date : Thu, 26 May 2022 13:50:43 +0200
Package Name : 1fichierfs
Version : 1.9.2~Focal
License : blank
Package Type : single
Are the details correct? [Y/n/q]
Skipping creating ../1fichierfs_
Currently there is not top level Makefile. This may require additional tuning
Done. Please edit the files in the debian/ subdirectory now.
Package prepared in /tmp/build/ 1fichierfs
That's fine.
Then further down the process we have
$ bzr commit -m "This is a test" 1fichierfs/ 1fichierfs- docs.docs README. Debian README. source source/ format
Committing to: /tmp/build/
added debian
added debian/
missing debian/
missing debian/
added debian/changelog
added debian/control
added debian/copyright
added debian/rules
added debian/source
added debian/
Committed revision 2.
(Note the "missing" warning is not an issue, that is because I purposefully removed these files that I didn't fill with useful information so far)
You can notice here that there is no "compat" file although I provided one in the debian directory.
echo 10 >debian/compat
Then further it seems to complain for compatibility level:
$ bzr builddeb -- -us -uc build-area/ 1fichierfs- 1.9.2~Focal, using debuild -us -uc
Building using working tree
Building package in merge mode
Looking for a way to retrieve the upstream tarball
Using the upstream tarball that is present in /tmp/build
Building the package in /tmp/build/
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: paquet source 1fichierfs
dpkg-buildpackage: info: version source 1.9.2~Focal-1
dpkg-buildpackage: info: distribution source focal
dpkg-buildpackage: info: source changé par .... <...@...fr>
dpkg-source --before-build .
dpkg-buildpackage: info: architecture hôte amd64
fakeroot debian/rules clean
dh clean
dh: error: Please specify the compatibility level in debian/compat
make: *** [debian/rules:18 : clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed
brz: ERROR: The build failed.
This was working as of 16.04, although it seemed to use compatibility level 9, and nowadays this seems obsolete.
What am I doing wrong (which is then probably missing in the documentation)?
Or is there something broken elsewhere with "compat" not being committed although it is present?