Not able to update

2011-08-23 Thread Nathan O.
I am not able to submit packages as an update through bodhi web interface
nor via fedpkg update. I have the package in F15, but I am trying to send it
to F16 and both ways give me the error that newlisp not tagged as an update
candidate

Also I get a weird error for clex when I run fedpkg build BuildError:
package clex is blocked for tag f16-updates-candidate.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Not able to update

2011-08-23 Thread John5342
On Tue, Aug 23, 2011 at 18:22, Nathan O. ndowen...@gmail.com wrote:
 I am not able to submit packages as an update through bodhi web interface
 nor via fedpkg update. I have the package in F15, but I am trying to send it
 to F16 and both ways give me the error that newlisp not tagged as an update
 candidate

 Also I get a weird error for clex when I run fedpkg build BuildError:
 package clex is blocked for tag f16-updates-candidate.

If i had to guess i would say it was one of the packages that was
orphaned and retired for F-16 just before the branch as was announced
some time back on this list [1]. If you claimed it after it was
retired/blocked then you will have to follow the relevant procedure
(which i believe also includes a re-review) to get it unblocked again.
Until it is unblocked it won't be possible to tag the build in F-16
(as indicated in the error) or submit it as an update. To the best of
my knowledge the procedure is outlined under Claiming Ownership of a
Deprecated Package at [2].

[1] - http://lists.fedoraproject.org/pipermail/devel/2011-July/154154.html
[2] - https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers

-- 
There are 10 kinds of people in the world: Those who understand binary
and those who don't...
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: Not able to update

2011-08-23 Thread Nathan O.
I searched the first link for my packages I am trying to send as an update
and neither showed up. Newlisp wasn't retired, it is one of them that I
started from scratch. Clex I adopted and went through the review request to
request ownership and which was granted. I am able to submit the spec file
through git. The problem is getting bodhi to accept the package as an update
for F16.


On Tue, Aug 23, 2011 at 5:57 PM, John5342 john5...@gmail.com wrote:

 On Tue, Aug 23, 2011 at 18:22, Nathan O. ndowen...@gmail.com wrote:
  I am not able to submit packages as an update through bodhi web interface
  nor via fedpkg update. I have the package in F15, but I am trying to send
 it
  to F16 and both ways give me the error that newlisp not tagged as an
 update
  candidate
 
  Also I get a weird error for clex when I run fedpkg build BuildError:
  package clex is blocked for tag f16-updates-candidate.

 If i had to guess i would say it was one of the packages that was
 orphaned and retired for F-16 just before the branch as was announced
 some time back on this list [1]. If you claimed it after it was
 retired/blocked then you will have to follow the relevant procedure
 (which i believe also includes a re-review) to get it unblocked again.
 Until it is unblocked it won't be possible to tag the build in F-16
 (as indicated in the error) or submit it as an update. To the best of
 my knowledge the procedure is outlined under Claiming Ownership of a
 Deprecated Package at [2].

 [1] - http://lists.fedoraproject.org/pipermail/devel/2011-July/154154.html
 [2] -
 https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers

 --
 There are 10 kinds of people in the world: Those who understand binary
 and those who don't...
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel