[aur-general] out of date packages?
What are proper criteria for flagging a package out of date? My reason for asking has to do with: http://www.floodgap.com/software/ttytter/ --
On 05/05/2016 09:16 AM, Jude DaShiell wrote:
What are proper criteria for flagging a package out of date? My reason for asking has to do with: http://www.floodgap.com/software/ttytter/
--
Well, it is currently flagged out of date: https://www.archlinux.org/packages/community/any/ttytter/ But I don't know why, since upstream is apparently dead and the community package is already on the latest (ancient) upstream release. Is this because it got forked to continue support? I think that qualifies as new software, and therefore a new package. -- Eli Schwartz
On Thu, 5 May 2016 10:14:13 -0400 Eli Schwartz <eschwartz93@gmail.com> wrote:
On 05/05/2016 09:16 AM, Jude DaShiell wrote:
What are proper criteria for flagging a package out of date? My reason for asking has to do with: http://www.floodgap.com/software/ttytter/
--
Well, it is currently flagged out of date: https://www.archlinux.org/packages/community/any/ttytter/
But I don't know why, since upstream is apparently dead and the community package is already on the latest (ancient) upstream release.
Is this because it got forked to continue support? I think that qualifies as new software, and therefore a new package.
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
On 05/05/2016 10:22 AM, Doug Newgard wrote:
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
Naturally I am aware that people can do whatever ridiculous things they want. :) Of course, I don't know why they would do something so silly, but apparently they do anyway... The "this" was Jude's reason for asking, though. ... The AUR can now show you the message left when flagging an out-of-date package in addition to the out-of-date status itself. Pity you can't see that in the repos as well. -- Eli Schwartz
On 05/05, Eli Schwartz wrote:
On 05/05/2016 10:22 AM, Doug Newgard wrote:
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
Naturally I am aware that people can do whatever ridiculous things they want. :) Of course, I don't know why they would do something so silly, but apparently they do anyway...
The "this" was Jude's reason for asking, though.
...
The AUR can now show you the message left when flagging an out-of-date package in addition to the out-of-date status itself. Pity you can't see that in the repos as well.
It's possible, but you have to be logged into archweb to do it. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
Le 05/05/2016 à 20:00, Johannes Löthberg a écrit :
On 05/05, Eli Schwartz wrote:
On 05/05/2016 10:22 AM, Doug Newgard wrote:
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
Naturally I am aware that people can do whatever ridiculous things they want. :) Of course, I don't know why they would do something so silly, but apparently they do anyway...
The "this" was Jude's reason for asking, though.
...
The AUR can now show you the message left when flagging an out-of-date package in addition to the out-of-date status itself. Pity you can't see that in the repos as well.
It's possible, but you have to be logged into archweb to do it.
I might sound a bit stupid, but how does one do that? I search a bit around, but found nothing… Thanks, Bruno
On Thu, 5 May 2016 20:07:14 +0200 Bruno Pagani <bruno.pagani@ens-lyon.org> wrote:
Le 05/05/2016 à 20:00, Johannes Löthberg a écrit :
On 05/05, Eli Schwartz wrote:
On 05/05/2016 10:22 AM, Doug Newgard wrote:
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
Naturally I am aware that people can do whatever ridiculous things they want. :) Of course, I don't know why they would do something so silly, but apparently they do anyway...
The "this" was Jude's reason for asking, though.
...
The AUR can now show you the message left when flagging an out-of-date package in addition to the out-of-date status itself. Pity you can't see that in the repos as well.
It's possible, but you have to be logged into archweb to do it.
I might sound a bit stupid, but how does one do that? I search a bit around, but found nothing…
Thanks, Bruno
AFAIK, accounts are for staff only.
On 05/05/2016 02:00 PM, Johannes Löthberg wrote:
The AUR can now show you the message left when flagging an out-of-date package in addition to the out-of-date status itself. Pity you can't see that in the repos as well.
It's possible, but you have to be logged into archweb to do it.
Technically true, but not very helpful for most people. -- Eli Schwartz
On Thu, 5 May 2016, Doug Newgard wrote:
Date: Thu, 5 May 2016 10:22:45 From: Doug Newgard <scimmia@archlinux.info> Reply-To: "Discussion about the Arch User Repository (AUR)" <aur-general@archlinux.org> To: aur-general@archlinux.org Subject: Re: [aur-general] out of date packages?
On Thu, 5 May 2016 10:14:13 -0400 Eli Schwartz <eschwartz93@gmail.com> wrote:
On 05/05/2016 09:16 AM, Jude DaShiell wrote:
What are proper criteria for flagging a package out of date? My reason for asking has to do with: http://www.floodgap.com/software/ttytter/
--
Well, it is currently flagged out of date: https://www.archlinux.org/packages/community/any/ttytter/
But I don't know why, since upstream is apparently dead and the community package is already on the latest (ancient) upstream release.
Is this because it got forked to continue support? I think that qualifies as new software, and therefore a new package.
You're right, but people can flag it out of date for whatever reason they want (and doing this a lot causes maintainers to ignore the flag). In this case, yes, it is because of a fork.
The fork is called oysttyer and was taken over by the oysttyer organization and the original author created another package called texapp to run on the adn social network. --
participants (5)
-
Bruno Pagani
-
Doug Newgard
-
Eli Schwartz
-
Johannes Löthberg
-
Jude DaShiell