[aur-general] Disown requests
Could anyone help me to get the permission to adopt 'fossil'. I've created a 'fossil-fossil' PKGBUILD. But, I want to adopt the 'fossil' too. I've reported the out-date and e-mailed the current maintainer, but no reply for at least one or two weeks. (Check the outdate time, it is more than one month).
On Wed, Jan 02, 2013 at 01:47:23PM +0800, Daniel YC Lin wrote:
Could anyone help me to get the permission to adopt 'fossil'. I've created a 'fossil-fossil' PKGBUILD.
You should not do this. Instead post a link to the updated PKGBUILD in the comments. I will delete this duplicate.
But, I want to adopt the 'fossil' too. I've reported the out-date and e-mailed the current maintainer, but no reply for at least one or two weeks.
Check your sent items and reply once it has been two weeks with no response.
(Check the outdate time, it is more than one month).
There may be good reasons why a package has not been updated, so an email to the maintainer is what we go on. -- Jonathan Steel
On Wed, Jan 02, 2013 at 01:47:00PM +0000, Jonathan Steel wrote:
On Wed, Jan 02, 2013 at 01:47:23PM +0800, Daniel YC Lin wrote:
Could anyone help me to get the permission to adopt 'fossil'. I've created a 'fossil-fossil' PKGBUILD.
You should not do this. Instead post a link to the updated PKGBUILD in the comments. I will delete this duplicate.
On further inspection, your package should be fossil-git. Please upload with this new name and I will merge it. fossil should follow the stable version.
But, I want to adopt the 'fossil' too. I've reported the out-date and e-mailed the current maintainer, but no reply for at least one or two weeks.
Check your sent items and reply once it has been two weeks with no response.
(Check the outdate time, it is more than one month).
There may be good reasons why a package has not been updated, so an email to the maintainer is what we go on.
-- Jonathan Steel
I've post an updated PKGBUILD on fossil & fossil-fossil. If you insist it should be rename to fossil-git, let me know, I'll upload a new PKGBUILD. On Wed, Jan 2, 2013 at 9:56 PM, Jonathan Steel <mail@jsteel.org> wrote:
On Wed, Jan 02, 2013 at 01:47:00PM +0000, Jonathan Steel wrote:
On Wed, Jan 02, 2013 at 01:47:23PM +0800, Daniel YC Lin wrote:
Could anyone help me to get the permission to adopt 'fossil'. I've created a 'fossil-fossil' PKGBUILD.
You should not do this. Instead post a link to the updated PKGBUILD in the comments. I will delete this duplicate.
On further inspection, your package should be fossil-git. Please upload with this new name and I will merge it. fossil should follow the stable version.
But, I want to adopt the 'fossil' too. I've reported the out-date and e-mailed the current maintainer, but no reply for at least one or two weeks.
Check your sent items and reply once it has been two weeks with no response.
(Check the outdate time, it is more than one month).
There may be good reasons why a package has not been updated, so an email to the maintainer is what we go on.
-- Jonathan Steel
On Sun, Jan 20, 2013 at 09:50:09AM +0800, Daniel YC Lin wrote:
I've post an updated PKGBUILD on fossil & fossil-fossil. If you insist it should be rename to fossil-git, let me know, I'll upload a new PKGBUILD.
Yes, please upload it with the right name; git packages should end with -git. https://wiki.archlinux.org/index.php/Arch_CVS_%26_SVN_PKGBUILD_guidelines Please also do not top-post.
On Wed, Jan 2, 2013 at 9:56 PM, Jonathan Steel <mail@jsteel.org> wrote:
On Wed, Jan 02, 2013 at 01:47:00PM +0000, Jonathan Steel wrote:
On Wed, Jan 02, 2013 at 01:47:23PM +0800, Daniel YC Lin wrote:
Could anyone help me to get the permission to adopt 'fossil'. I've created a 'fossil-fossil' PKGBUILD.
You should not do this. Instead post a link to the updated PKGBUILD in the comments. I will delete this duplicate.
On further inspection, your package should be fossil-git. Please upload with this new name and I will merge it. fossil should follow the stable version.
But, I want to adopt the 'fossil' too. I've reported the out-date and e-mailed the current maintainer, but no reply for at least one or two weeks.
Check your sent items and reply once it has been two weeks with no response.
(Check the outdate time, it is more than one month).
There may be good reasons why a package has not been updated, so an email to the maintainer is what we go on.
-- Jonathan Steel
participants (2)
-
Daniel YC Lin
-
Jonathan Steel