FS#7460 - sudo PKGBUILD missing arch and license vars
Attached to Project:
Arch Linux
Opened by Alex Heck (nesl247) - Monday, 18 June 2007, 23:55 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 26 June 2007, 18:51 GMT
Opened by Alex Heck (nesl247) - Monday, 18 June 2007, 23:55 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 26 June 2007, 18:51 GMT
|
Details
Description:
The sudo PKGBUILD is missing arch and license vars - at least it was when I ran abs and looked at it. If we're not supposed to report bugs like this, please tell me. I have no idea on reporting bugs about PKGBUILDS missing stuff that is changed, such as option=(!option) stuff. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Dan McGee (toofishes)
Tuesday, 26 June 2007, 18:51 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in new release
Tuesday, 26 June 2007, 18:51 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in new release
Comment by
Roman Kyrylych (Romashka) - Tuesday,
19 June 2007, 11:27 GMT
in fact, there seems to be a lot of packages with missing/wrong
license/md5sum fields in official repos :(
Comment by Alex Heck (nesl247) -
Wednesday, 20 June 2007, 07:45 GMT
Yeah. And almost all, if not all gnome packages which haven't been
updated recently seem to have NOLIBTOOL or nolibtool instead of
!libtool, and other such things.
Comment by Dan McGee (toofishes) -
Wednesday, 20 June 2007, 23:33 GMT
The switch from no to ! is very recent, and makepkg purposely
works with both. It will take some time to change all of them, and
it isn't worth changing unless the package is actually being
updated.
Comment by Alex Heck (nesl247) -
Wednesday, 20 June 2007, 23:36 GMT
Didn't know it was that recent. And I know it works for both, just
annoying at times to have to change it to remove the warning.
Comment by Dan McGee (toofishes) -
Tuesday, 26 June 2007, 18:43 GMT
Fixing this one in CVS now. There are a lot of small issues like
this, and I wouldn't worry about reporting it unless you see the
package just got updated and it was missed. With makepkg enforcing
the license and arch thing a bit more now, this shouldn't be too
big of an issue.