12:58 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All, With branching for f18 happening on Tuesday next week we still
have quite a large number of failures and packages needing rebuilt.
the list of 415 current failures can be found at
http://ausil.fedorapeople.org/f18-failures.html
while the total rebuild list of 545 can be found at
http://ausil.fedorapeople.org/f18-needsbuilt.html
please fix them before branching. anything not built will start on the
process of being removed from fedora.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlAbaKEACgkQkSxm47BaWfe/DACfUg4i7NNMjVLYkq4u25pZAnBF
SzkAn3B6hMuQNV7KQa49XSTnzS0HyCb3
=yreK
-----END PGP SIGNATURE-----
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11:02 a.m.
On Fri, 2012-08-03 at 00:58 -0500, Dennis Gilmore wrote:
while the total rebuild list of 545 can be found at
http://ausil.fedorapeople.org/f18-needsbuilt.html
I don't understand why insight is still in this list: I fixed the mass
rebuild failure and already produced a successful build: Koji says:
insight-7.4.50-3.20120403cvs.fc18 monnerat 2012-07-20 12:47:51 complete
insight-7.4.50-2.20120403cvs.fc18 ausil 2012-07-20 05:18:10 failed
Some more action needed on my side ?
6:41 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El Fri, 03 Aug 2012 18:02:26 +0200
Patrick Monnerat <pm(a)datasphere.ch> escribió:
On Fri, 2012-08-03 at 00:58 -0500, Dennis Gilmore wrote:
> while the total rebuild list of 545 can be found at
> http://ausil.fedorapeople.org/f18-needsbuilt.html
I don't understand why insight is still in this list: I fixed the mass
rebuild failure and already produced a successful build: Koji says:
insight-7.4.50-3.20120403cvs.fc18 monnerat 2012-07-20 12:47:51
complete insight-7.4.50-2.20120403cvs.fc18 ausil 2012-07-20
05:18:10 failed
Some more action needed on my side ?
the issue is that you built it using dist-rawhide which has not been
used by the tools for quite awhile, you should make sure you are using
the latest fedpkg, ive updated the script to consider dist-rawhide as
well. so it should drop off next run
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlAcYaoACgkQkSxm47BaWfcw8wCeK7ydzh5vbyyamz5CqKLihPU3
mY4An3cS1VvRiU26uDeKrchGe5sTHxxd
=+Aun
-----END PGP SIGNATURE-----
4:49 p.m.
On 08/02/2012 11:58 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All, With branching for f18 happening on Tuesday next week we still
have quite a large number of failures and packages needing rebuilt.
the list of 415 current failures can be found at
http://ausil.fedorapeople.org/f18-failures.html
while the total rebuild list of 545 can be found at
http://ausil.fedorapeople.org/f18-needsbuilt.html
please fix them before branching. anything not built will start on the
process of being removed from fedora.
FWIW - I just built a new tcsh package which fixed a problem with it not being
able to source files (mainly on x86_64). This was causing problems building
gridengine (though not the only problem alas). If your package uses csh
scripts during build (*shudder*), you may have been affected.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
7:21 a.m.
Hi,
On Fri, Aug 3, 2012 at 11:28 AM, Dennis Gilmore <dennis(a)ausil.us> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All, With branching for f18 happening on Tuesday next week we still
have quite a large number of failures and packages needing rebuilt.
the list of 415 current failures can be found at
http://ausil.fedorapeople.org/f18-failures.html
while the total rebuild list of 545 can be found at
http://ausil.fedorapeople.org/f18-needsbuilt.html
please fix them before branching. anything not built will start on the
process of being removed from fedora.
Can you please fix the script so that it will ignore the new packages
that just got their SCM request completed but package not yet built on
koji from neeedsbuilt list? I am still confused over the meaning of
needsbuilt list. Does that mean packages missed by mass rebuild script
as well as failed builds from mass rebuild need to be only listed in
needsbuilt list?
Regards,
Parag.
7:39 p.m.
On Sat, 4 Aug 2012 17:51:58 +0530
Parag N(पराग़) <panemade(a)gmail.com> wrote:
Can you please fix the script so that it will ignore the new
packages
that just got their SCM request completed but package not yet built on
koji from neeedsbuilt list?
Why wouldn't they be built as soon as they were added?
I am still confused over the meaning of
needsbuilt list. Does that mean packages missed by mass rebuild script
as well as failed builds from mass rebuild need to be only listed in
needsbuilt list?
I think it's any package that doesn't have a successfull build in f18
since the mass rebuild was started.
kevin
9:51 p.m.
Hi,
On Sun, Aug 5, 2012 at 6:09 AM, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Sat, 4 Aug 2012 17:51:58 +0530
Parag N(पराग़) <panemade(a)gmail.com> wrote:
> Can you please fix the script so that it will ignore the new packages
> that just got their SCM request completed but package not yet built on
> koji from neeedsbuilt list?
Why wouldn't they be built as soon as they were added?
You are right but I am still finding the answer on what to do in such
situations as we have no policy for that. In the past I have done some
reviews where even a package SCM is done but reporter didn't import
the package at all. For some packages I did it after waiting long.
Can we have any solution like block the packages after some time if
reporter will not import the package. That way such rel-eng scripts
can avoid listing those packages. If anyone want to takeover such
package ownership then he can just re-add the package SCM request or
submit a fresh review request.
Another thing, Its not always possible for a package owner to
instantly import the package once the package SCM is done. So, if we
still need to show such packages in needsbuilt then I see no solution
for this case.
> I am still confused over the meaning of
> needsbuilt list. Does that mean packages missed by mass rebuild script
> as well as failed builds from mass rebuild need to be only listed in
> needsbuilt list?
I think it's any package that doesn't have a successfull build in f18
since the mass rebuild was started.
I see that even if I will get my new package SCM done today and this
script is run, I can see my package appeared in needsbuilt list
whereas it has nothing to do with f18 mass rebuild as my package is
totally a new package. Isn't it a regular package process where we
actually have no restrictions on when to have a new package process
completed?
Thanks,
Parag.
10:36 p.m.
On Sun, 5 Aug 2012 08:21:16 +0530
Parag N(पराग़) <panemade(a)gmail.com> wrote:
You are right but I am still finding the answer on what to do in
such
situations as we have no policy for that. In the past I have done some
reviews where even a package SCM is done but reporter didn't import
the package at all. For some packages I did it after waiting long.
Can we have any solution like block the packages after some time if
reporter will not import the package. That way such rel-eng scripts
can avoid listing those packages. If anyone want to takeover such
package ownership then he can just re-add the package SCM request or
submit a fresh review request.
Another thing, Its not always possible for a package owner to
instantly import the package once the package SCM is done. So, if we
still need to show such packages in needsbuilt then I see no solution
for this case.
Well, yeah, I would say in this case after some reasonable time if the
submitter hasn't built the new package and you haven't heard from them
you could revoke your fedora-review:+ on the review, and close it. If
they come back they can resubmit it.
I see that even if I will get my new package SCM done today and this
script is run, I can see my package appeared in needsbuilt list
whereas it has nothing to do with f18 mass rebuild as my package is
totally a new package. Isn't it a regular package process where we
actually have no restrictions on when to have a new package process
completed?
Sure, there's going to be some small number of packages in that state.
The thing is: If you get a package built and tagged into f18 before the
mass branch it's easily. If for whatever reason you wait until after
that you will need to not only fix rawhide, but the f18 branched
version and deal with an update in bodhi, etc.
So, it's to your advantage to fix everything you can now before that
happens and save yourself some more work later.
IMHO.
kevin
9:24 a.m.
Fixed mine:
infinispan
jboss-connector-1.6-api
jboss-jacc-1.4-api
jboss-jaspi-1.0-api
jboss-naming
jboss-transaction-spi
picketbox
picketbox-commons
picketbox-xacml
--
Ricardo Arguello (ricardo)
On Fri, Aug 3, 2012 at 12:58 AM, Dennis Gilmore <dennis(a)ausil.us> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All, With branching for f18 happening on Tuesday next week we still
have quite a large number of failures and packages needing rebuilt.
the list of 415 current failures can be found at
http://ausil.fedorapeople.org/f18-failures.html
while the total rebuild list of 545 can be found at
http://ausil.fedorapeople.org/f18-needsbuilt.html
please fix them before branching. anything not built will start on the
process of being removed from fedora.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlAbaKEACgkQkSxm47BaWfe/DACfUg4i7NNMjVLYkq4u25pZAnBF
SzkAn3B6hMuQNV7KQa49XSTnzS0HyCb3
=yreK
-----END PGP SIGNATURE-----
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
4296
days inactive
4300
days old
8 comments
6 participants
participants (6)
-
Dennis Gilmore -
Kevin Fenzi -
Orion Poplawski -
Parag Nemade -
Patrick Monnerat -
Ricardo Argüello