FS#2290 - flag out of date additional comment

Attached to Project: Arch Linux
Opened by Nikos Kouremenos (zeppelin) - Saturday, 26 February 2005, 11:32 GMT
Last edited by eliott (cactus) - Tuesday, 04 September 2007, 06:35 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Simo Leone (neotuli)
eliott (cactus)
Architecture All
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I often find myself in this situation:
"I want to run A package that depends on FOO package"
FOO gets updated so A doesn't work anymore, and it's just a matter of just re-compliling the package [think python etc]
Now for this simple reason it can be annoying to use flyspray. I wonder if you could put an addition field below the email address that will say:

"Additional Comment: (if any)"

so I and other can inform the kind packager that it's just a recompilation. (he's one makepkg away of making it work that is).

If you fear that this will end up in not using flyspray, then you're right. That's why I propose this:

Email Address:
and then
[] Additional Info (not checked by default)
if checked it enables ONE_CHOICE
[] A pkg's dep is newer and broke it (so simple recompilation)
[] Others in the future to make the life easier.

If you don't agree I can understand it :)
This task depends upon

Closed by  eliott (cactus)
Tuesday, 04 September 2007, 06:35 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented comment field on 'flag package out of date'.
Comment by Andreas Radke (AndyRTR) - Wednesday, 27 December 2006, 06:13 GMT
you can mail the maintainer or file a bugreport - but i'm with you that a small comment could make life much easier.
Comment by Dan McGee (toofishes) - Monday, 13 August 2007, 14:30 GMT
In addition, why don't these emails include the package name in the email subject?
Comment by eliott (cactus) - Friday, 31 August 2007, 07:19 GMT
Regarding original filing: That really *is* what the bugtracker is for though.

I do think adding a 'comment' field to the flag out of date interface may have some merit...
Comment by Roman Kyrylych (Romashka) - Friday, 31 August 2007, 07:23 GMT
Sometimes there is a new version for the package but not on official site (e.g. it's on FTP and announced on ML as stable but no news on website; or development was continued by another dev on another site), so user that flags package out of date may want to notify maintainer about this. (in fact there *were* such facts)

Loading...