On Sun, Apr 07, 2013 at 08:35:19 +0800,
Christopher Meng cicku...@gmail.com wrote:
I think after migrating to cgit there comes a lot if errors like this.
How would cgit bit related to EVR errors? EVR errors typically come from
doing an update in one branch, but not later ones.
--
devel
I mean the error script URL
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Sunday, April 07, 2013 10:23 PM, Christopher Meng wrote:
I mean the error script URL
Please keep some context with your emails.
Try quoting the actual parts of the emails you are answering to, as it
avoids this kind of misunderstandings.
--
Mathieu
--
devel mailing list
On 06/04/13 01:47, build...@fedoraproject.org wrote:
Broken upgrade path report for tags f19 - f20:
[...]
kalev:
vala:
f19 f20 (vala-0.20.0-1.fc19 vala-0.19.0-1.fc19)
Vala build dies with:
+ /usr/bin/emacs -batch --no-init-file --no-site-file --eval '(progn (setq
load-path
This report generated by Fedora Release Engineering, using
http://git.fedorahosted.org/git/?p=releng;a=blob;f=scripts/check-upgrade-paths.py;hb=HEAD
Where is the script really located?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
On Sat, 6 Apr 2013 19:09:49 -0400
Rahul Sundaram methe...@gmail.com wrote:
This report generated by Fedora Release Engineering, using
http://git.fedorahosted.org/git/?p=releng;a=blob;f=scripts/check-upgrade-paths.py;hb=HEAD
Where is the script really located?
I think after migrating to cgit there comes a lot if errors like this.
Sent from Subor Gameplayer
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Broken upgrade path report for tags f19 - f20:
BitchX:
f19 f20 (BitchX-1.2.1-1.fc19 BitchX-1.2-21.fc19)
a2ps:
f19 f20 (a2ps-4.14-18.fc19 a2ps-4.14-17.fc19)
bind10:
f19 f20 (bind10-1.0.0-2.fc19 bind10-1.0.0-1.fc19)
cgnslib:
f19 f20 (cgnslib-3.2-1.fc19 cgnslib-3.1-5.r4.fc19)
