[aur-general] Notify by e-mail when PKGBUILD updated by maintainer?
Hello, I went to through this AUR wiki page but did not get the answer. https://wiki.archlinux.org/index.php/AUR Is there a way to get notified when "Maintainer" updates new PKGBUILD? We already have way to notify for new comments on AUR package. So possibly it would be easy to extend that without much coding and send notification when new PKGBUILD is uploaded. New Comment => send e-mail to those who subscribed for comments New Update => send e-mail to those who voted AND subscribed for comments (or we can have a link called "Notify of new update") In my opinion getting notified for Update is more important than getting notified for comments. I see similar discussion on Google around 2012, but I really am surprised that not many have asked for this feature which I thought should be a basic need. :) PS: I am not looking for solution like pkgbuild-watch. I am looking for option on AUR itself. Thanks, Amish.
On 2014-05-07 09:11, Amish wrote:
Hello,
I went to through this AUR wiki page but did not get the answer. https://wiki.archlinux.org/index.php/AUR
Is there a way to get notified when "Maintainer" updates new PKGBUILD?
We already have way to notify for new comments on AUR package. So possibly it would be easy to extend that without much coding and send notification when new PKGBUILD is uploaded.
New Comment => send e-mail to those who subscribed for comments
New Update => send e-mail to those who voted AND subscribed for comments (or we can have a link called "Notify of new update")
In my opinion getting notified for Update is more important than getting notified for comments.
I see similar discussion on Google around 2012, but I really am surprised that not many have asked for this feature which I thought should be a basic need. :)
PS: I am not looking for solution like pkgbuild-watch. I am looking for option on AUR itself.
Thanks,
Amish.
No, there is not currently a way. It has been requested: https://bugs.archlinux.org/task/30109 I believe cryptocrack has said that the entire notification system needs an overhaul, and things like this won't get implemented until that happens.
On Wed, May 7, 2014 at 5:56 PM, Doug Newgard <scimmia@archlinux.info> wrote:
I believe cryptocrack has said that the entire notification system needs an overhaul, and things like this won't get implemented until that happens.
On 05/08/2014 02:21 AM, Marcel Korpel wrote:
On Wed, May 7, 2014 at 5:56 PM, Doug Newgard <scimmia@archlinux.info> wrote:
I believe cryptocrack has said that the entire notification system needs an overhaul, and things like this won't get implemented until that happens.
I added one line in package update Guidelines for Maintainer. Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag... Here is the line added: "After submitting the update, leave a comment on AUR page of the package so users following the package get notified." Hopefully that can be a temporary workaround. Amish
On 2014-05-08 10:50 +0530 Amish wrote:
On 05/08/2014 02:21 AM, Marcel Korpel wrote:
On Wed, May 7, 2014 at 5:56 PM, Doug Newgard <scimmia@archlinux.info> wrote:
I believe cryptocrack has said that the entire notification system needs an overhaul, and things like this won't get implemented until that happens.
I added one line in package update Guidelines for Maintainer.
Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag...
Here is the line added:
"After submitting the update, leave a comment on AUR page of the package so users following the package get notified."
Hopefully that can be a temporary workaround.
Amish
Please remove that. Commenting every single update will clutter up the comments page and make it harder to follow discussions. If you want to track AUR updates in the absence of a built-in notification system, write a script or use one of the existing AUR trackers or helpers. I generally only care about updates to packages that I use, so paconky[1] is good enough for me. To give another example, I have attached a very simple script that accepts a list of package names and prints out their last modification times in a sorted list. It depends on python3-aur. [1] https://bbs.archlinux.org/viewtopic.php?id=68104
On 2014-05-08 14:10 +0000 Xyne wrote:
To give another example, I have attached a very simple script that accepts a list of package names and prints out their last modification times in a sorted list. It depends on python3-aur.
The attachments seems to have been stripped. You can find the script here: http://xyne.archlinux.ca/scripts/aur/list_aur_mtimes.py
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530 Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag...
Here is the line added:
"After submitting the update, leave a comment on AUR page of the package so users following the package get notified."
Please remove that. Commenting every single update will clutter up the comments page and make it harder to follow discussions.
I am ok with removing it. But I would like if more people give opinion. Because: 1) Its just a guideline, not every maintainer will follow it. 2) Maintainer can add one more point in guideline: to "delete" his older update comment when new update is uploaded. 3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned. Please think over point 2, If maintainer follows guideline and posts update comment, he will also delete older update comment. If maintainer does not follow guideline, no need to delete anything either! Both ways, comment system will remain clean. Regards, Amish
On Thu, May 08, 2014 at 08:06:15PM +0530, Amish wrote:
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530 Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag...
Here is the line added:
"After submitting the update, leave a comment on AUR page of the package so users following the package get notified."
Please remove that. Commenting every single update will clutter up the comments page and make it harder to follow discussions.
I am ok with removing it. But I would like if more people give opinion.
Because:
1) Its just a guideline, not every maintainer will follow it.
2) Maintainer can add one more point in guideline: to "delete" his older update comment when new update is uploaded.
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
Please think over point 2, If maintainer follows guideline and posts update comment, he will also delete older update comment.
If maintainer does not follow guideline, no need to delete anything either!
Both ways, comment system will remain clean.
Regards,
Amish
As a maintainer, I would never notify my packages' users. Why? Because as a user, I would never want such notifications in the first place. All it would do is clutter up my inbox and thus make me want to turn off notifications for the package in question. Seeing as how useful discussions actually occur in the AUR comments, I would prefer to keep notifications active, but that wouldn't stop me if maintainers started doing this. Essentially, this is the flip side of the highly-annoying "a new update is available" comment, when the flag out-of-date link is right there. -- David J. Haines djhaines@gmx.com 0xAFB3D16D - F929 270F B7C3 78AE A741 434F A7C6 F264 AFB3 D16C
* Amish <ammdispose-arch@yahoo.com> [2014-05-08 20:06:15 +0530]:
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530 Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag...
Here is the line added:
"After submitting the update, leave a comment on AUR page of the package so users following the package get notified."
Please remove that. Commenting every single update will clutter up the comments page and make it harder to follow discussions.
I am ok with removing it. But I would like if more people give opinion.
Because:
1) Its just a guideline, not every maintainer will follow it.
2) Maintainer can add one more point in guideline: to "delete" his older update comment when new update is uploaded.
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
Please think over point 2, If maintainer follows guideline and posts update comment, he will also delete older update comment.
If maintainer does not follow guideline, no need to delete anything either!
Both ways, comment system will remain clean.
Regards,
Amish
As both a maintainer and user of quite a few AUR packages: I'll get annoyed and unsubscribe from notifications for all the packages I use which do this, and I'll certainly not do it myself. There *are* already a lot of tools which allow you to opt-in to update notifications, why don't you simply use these? With your guideline change, you're forcing everyone to get update notifications even if they aren't interested. For me, seeing the updates in my AUR helper is more than enough, I don't want an email on every update, but I want mails on comments. Florian -- () ascii ribbon campaign - stop html mail www.asciiribbon.org /\ www.the-compiler.org | I love long mails http://email.is-not-s.ms/ Schmidt's Observation: All things being equal, a fat person uses more soap than a thin person.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If we ever have a proper notifocation system inbuilt, I hope it will be optional per user because I don't want to be flooded with emails about package updates. Seeing them in my AUR helper before updating is also enough for me - -- nekinie On 08/05/14 15:48, Florian Bruhin wrote:
* Amish <ammdispose-arch@yahoo.com> [2014-05-08 20:06:15 +0530]:
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530 Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link: https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packag...
Here is the line added:
"After submitting the update, leave a comment on AUR page of the package so users following the package get notified."
Please remove that. Commenting every single update will clutter up the comments page and make it harder to follow discussions.
I am ok with removing it. But I would like if more people give opinion.
Because:
1) Its just a guideline, not every maintainer will follow it.
2) Maintainer can add one more point in guideline: to "delete" his older update comment when new update is uploaded.
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
Please think over point 2, If maintainer follows guideline and posts update comment, he will also delete older update comment.
If maintainer does not follow guideline, no need to delete anything either!
Both ways, comment system will remain clean.
Regards,
Amish
As both a maintainer and user of quite a few AUR packages: I'll get annoyed and unsubscribe from notifications for all the packages I use which do this, and I'll certainly not do it myself.
There *are* already a lot of tools which allow you to opt-in to update notifications, why don't you simply use these?
With your guideline change, you're forcing everyone to get update notifications even if they aren't interested.
For me, seeing the updates in my AUR helper is more than enough, I don't want an email on every update, but I want mails on comments.
Florian
- -- regards, James Bulmer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTa5oaAAoJEEaOSVAnZGA3HKYQAJiLB4yOlUV5uTrJ3KqMf7sn s1zKd54LujYhXus7geDreXGAWrOJwtxPMUV75A0ZjikLYKTmPeTLQge2ylMJ3BlV l6w+xiRsX9HR9RxOlr2nLXTaAa4dBgdDNoPH2iIkGfegDRpqQnDPoNE520jNJ/a3 b0uFMFSVlUWaLMe0mIdgR6KLom+7HvLRAOa+ei3e7KV8oGesO7dWw/ptYC4aPGYT 3t6ltMt4lkMweabH0yrH+a0C/BntpPkT2reuKDPuSG4ND666SBTwUt4r6trafUBz nYxZiekLc3+1vnkY3F5g5GVJyIj4Qx6yg6zqyKsoXM7tqrLVHVP9t3zCrJYPBo/K F6r+vPpUovt5zl8WmcgUQX/fIWOdKnQMyLVjaFNNcvXTBLM6JulhCMANpmCsBsBa owu2QrMOniB5Qh/fJvQqhskXKG2m5kXPySVlyb1waRPg1NZJMNFv0RASjkpOrar9 CNTNzeri9yHxhP/6bwMLx8bpFP1+vgLDQeYwbQ/ZM8F21zAiGKp8dwnzmxH3yaWj VQN8Viie/HQpaVjczg8Goxk84Rw2QhIIBsUFlOtOwwqtoPMkDZcA2gg+MRlHoquO BjvQRwcgEk2gblFbHPBx9+NJymyxKfmAYcW8m/jaw7PQDLH7WQyXiFa3YW8Kbx0l 8zCpDCc0Y08NxCWXsx+X =lkR6 -----END PGP SIGNATURE-----
On 05/08/2014 08:22 PM, James Bulmer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If we ever have a proper notifocation system inbuilt, I hope it will be optional per user because I don't want to be flooded with emails about package updates. Seeing them in my AUR helper before updating is also enough for me
- -- nekinie
With many people saying NO, I have removed it! :) Amish.
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
This is true, but should not be implemented like that. That's good it has been reverted. AUR could keep track of the updates, e.g. have a new field named "Updates" that would list all versions and their release dates. It could be expandable with a single click, so it doesn't clutter the interface. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
On 8 May 2014 17:09, Nowaker <enwukaer@gmail.com> wrote:
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
This is true, but should not be implemented like that. That's good it has been reverted.
AUR could keep track of the updates, e.g. have a new field named "Updates" that would list all versions and their release dates. It could be expandable with a single click, so it doesn't clutter the interface.
This seems like a pointless feature to me. As a user I'm only interested in two things: 1) what version have I got installed now, and 2) what version is available on the AUR now. Perhaps I am in a minority here though. A function that sends a notification to subscribers when a new src.tar.gz is uploaded seems like the best way of fulfilling the original request. Though perhaps a new option to "subscribe to update notifications" would be preferable to sending them to people who just want to be informed when a package is removed/merged. Cheers, WorMzy
-- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I agree with the subscription suggestion, users can then be imformed of package updates that are relevent to them - -- nekinie On 08/05/14 17:20, WorMzy Tykashi wrote:
On 8 May 2014 17:09, Nowaker <enwukaer@gmail.com> wrote:
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
This is true, but should not be implemented like that. That's good it has been reverted.
AUR could keep track of the updates, e.g. have a new field named "Updates" that would list all versions and their release dates. It could be expandable with a single click, so it doesn't clutter the interface.
This seems like a pointless feature to me. As a user I'm only interested in two things: 1) what version have I got installed now, and 2) what version is available on the AUR now. Perhaps I am in a minority here though.
A function that sends a notification to subscribers when a new src.tar.gz is uploaded seems like the best way of fulfilling the original request. Though perhaps a new option to "subscribe to update notifications" would be preferable to sending them to people who just want to be informed when a package is removed/merged.
Cheers,
WorMzy
-- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
- -- regards, James Bulmer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTa7EAAAoJEEaOSVAnZGA36fAP/37aqh+/QsDpUpCFsx4/+Qnl 0NUUIOm/EKErk3n86VZP8PsgRnOE/hjjHdps0b3LCGdMuZN5M5myUUjwjW2wqDPz c9OxQjw6oAoMxg3922Gy7SLe3ccK4lwk63ocBRknM/eqIaKamq2vlQn1h78EGvA8 p2XNTh12NNKfc8Iyi5guwTI5nQKB5n65UD28P5dJSmhgvfC4W5qGAX9taMCaLo4Z MhMkzHQSmQ92NS5+XmNyMrbKG8npdgvsVHyRk3D4wsw+JcnSJzkJzJ/xFVlhhbG5 FiDsYQHYkB2UpkR5SBNVXTiJyam2CoBMKU4Cjz8YuCM5JZm5AwSMHheui9yI+Kcv W4QEHR7/ajhr6PQV8+MsnWV57eacqtDR2pj24nWrUVqwDsMZSO0BlpZTjo1Or/15 suCgK26/VtbB7Dt7EiaSF2K+HA5bF5AsoB4RcaBAk5MsLSHnHDBQP6XxaMwJioif XjpqhRGlurm500fHcDtxb483/mUmpHmvXDV4LpaR3CSH77ukPZooYNfn6m97kE9L W8CLwHmEDGFxtW7N21AU9k3k6WRBMRtewyBXR07holVoF+Wu7gLyM7Gmrx/OCByT XoJjP78BGMk5+ImWRvC/ynRZa1e6sSjfVnqMEWXHO4iUs87A7g4ltXD2GRiIsfXP IQvba9fHIR1mN+IPv997 =+T8J -----END PGP SIGNATURE-----
On 2014-05-08 18:09 +0200 Nowaker wrote:
3) I think commenting about update will involve more people and bring awareness that the AUR package is active and not orphaned.
This is true, but should not be implemented like that. That's good it has been reverted.
AUR could keep track of the updates, e.g. have a new field named "Updates" that would list all versions and their release dates. It could be expandable with a single click, so it doesn't clutter the interface.
The AUR lists the current version and the date of the last package modification. That is enough. You really don't need a full history of changes prior to the previous one. If you really want to follow package history for some reason, you can check out the AUR Git repo.
participants (9)
-
Amish
-
David J. Haines
-
Doug Newgard
-
Florian Bruhin
-
James Bulmer
-
Marcel Korpel
-
Nowaker
-
WorMzy Tykashi
-
Xyne