Search Criteria
Package Details: dh-make 2.202304-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/dh-make.git (read-only, click to copy) |
---|---|
Package Base: | dh-make |
Description: | Tool that converts source archives into Debian package source |
Upstream URL: | https://salsa.debian.org/debian/dh-make |
Licenses: | GPL |
Submitter: | None |
Maintainer: | lamaral |
Last Packager: | lamaral |
Votes: | 15 |
Popularity: | 0.000000 |
First Submitted: | 2011-12-31 08:16 (UTC) |
Last Updated: | 2024-03-30 21:06 (UTC) |
Latest Comments
1 2 3 Next › Last »
Bustel commented on 2021-01-04 13:17 (UTC)
Package version needs to be updated.
l0b0 commented on 2020-09-04 01:30 (UTC) (edited on 2020-09-04 01:48 (UTC) by l0b0)
Ralf_Mardorf commented on 2018-06-22 17:26 (UTC) (edited on 2018-06-22 17:30 (UTC) by Ralf_Mardorf)
It makes much sense, somebody might have experienced that 2.201801-1 didn't build. The user is monitoring the package and expects that the fixed version is > 2.201801-1, so assuming the pkgver should be the same, it should be 2.201801-1+. If you don't increase the pkgrel, how should the user notice that the issue is fixed, by monitoring each change to the URL? Keep in mind, if the content of the URL does change, it just could be an additional comment, it not necessarily is a fix.
z3ntu commented on 2018-06-22 08:01 (UTC)
@Ralf_Mardorf: If you're going to link to that page I'm going to quote from it:
The fix of the source url was neither a fix nor an additional feature nor anything that influences the resulting package. It doesn't make sense to bump the pkgrel there, if the build didn't even work before. And for those where it worked (e.g. downloaded the source manually) there is no reason to rebuild the package as nothing has changed. And just because you bump the pkgrel to 100 doesn't mean I have to do that as well...
Ralf_Mardorf commented on 2018-06-22 04:44 (UTC) (edited on 2018-06-22 04:46 (UTC) by Ralf_Mardorf)
The missing underscores might be a copy and paste related mistake.
Please care about the pkgrel. There might be different ways users monitor webpages for updates, IOW users might not use an AUR helper. While an AUR helper might not provide an option to monitor updates like this one, when building a package failed, a tool to watch URLs does. Another reason to increase the pkgrel is that a user like me fixed the package and informed the maintainer. To distinguish the broken build from the new build, I increased the pkgrel, since you didn't bump the pkgrel, I will not notice when you change to pkgrel 2 for another reason.
z3ntu commented on 2018-06-21 19:00 (UTC)
Sorry, fixed it now :)
hnicke commented on 2018-06-21 18:47 (UTC)
Instead of what Ralf_Mardorf said, I replaced the source with http://ftp.debian.org/debian/pool/main/d/${pkgname}/${pkgname}_${pkgver}.tar.xz
Note the underscore between ${pkgname} and ${pkgver}. This works for me.
Ralf_Mardorf commented on 2018-06-21 18:40 (UTC)
I get "Could not resolve host: http.debian.org". Replacing pkgrel=1 by pkgrel=2 and replacing http://http.debian.org/debian/pool/main/d/${pkgname}/${pkgname}${pkgver}.tar.xz by http://ftp.debian.org/debian/pool/main/d/${pkgname}/${pkgname}${pkgver}.tar.xz solves the issue.
1 2 3 Next › Last »