On Wed, Nov 24, 2010 at 8:32 AM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 11/24/2010 12:45 AM, Jesse Keating wrote:
On 10/5/10 3:27 PM, Jesse Keating wrote:
snip
Here is a list of the current known potentially bad builds and what
action could be or has been taken:
wildmidi - my
Here is a list of the current known potentially bad builds and what
action could be or has been taken:
The below I either maintain or co-maintain.
Ignore, I have another build that needs to be pushed:
syncevolution - update in testing
Fine to tag for F-14, its obsolete in F-15 (I thought it
On Wednesday 24 November 2010, Jesse Keating wrote:
ccache - my build can be tagged
I'll most likely push an update to ccache soon so no need to tag this one.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On 10/5/10 3:27 PM, Jesse Keating wrote:
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have undefined behavior, which
could lead to data corruption.
On Tue, Nov 23, 2010 at 03:45:26PM -0800, Jesse Keating wrote:
gcc - update in -candidate, ping jakub
Just remove gcc from your list. gcc is bootstrapped, so
the installed gcc only builds first stage, everything else
is built by (one of the) newly built compiler(s).
So, gcc in f14 surely
On 11/23/2010 03:45 PM, Jesse Keating wrote:
Here is a list of the current known potentially bad builds and what
action could be or has been taken:
Please alphabetize such a list, always! _PLEASE_?
An alphabetized list is several times more effective at communication
because advanced readers
On 11/23/10 5:04 PM, John Reiser wrote:
Please alphabetize such a list, always! _PLEASE_?
An alphabetized list is several times more effective at communication
because advanced readers can process it more quickly by eye
than a list that is in random order. Most mail user agent (MUA) software
Hi,
On 11/24/2010 12:45 AM, Jesse Keating wrote:
On 10/5/10 3:27 PM, Jesse Keating wrote:
snip
Here is a list of the current known potentially bad builds and what
action could be or has been taken:
wildmidi - my rebuild can be tagged
tecnoballz - my build can be tagged
These 2 are mine
Hello:
Jesse Keating wrote, at 10/06/2010 07:27 AM +9:00:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/10 8:09 AM, Mamoru Tasaka wrote:
Hello:
Jesse Keating wrote, at 10/06/2010 07:27 AM +9:00:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/6/10 1:44 AM, Tim Waugh wrote:
On Tue, 2010-10-05 at 15:27 -0700, Jesse Keating wrote:
PPS I did not modify my bump script yet to attempt a commit to master
and merge to the f14 branch. In the interest of time, I took the easy
route and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/6/10 1:34 AM, Peter Robinson wrote:
What happens in a case where the packager is about to push a new
version, or there has been a rebuild since the 26th?
In this case my script will detect a new build in either
dist-f14-updates-candidate or
On Tue, Oct 5, 2010 at 11:27 PM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with
On Tue, 2010-10-05 at 15:27 -0700, Jesse Keating wrote:
PPS I did not modify my bump script yet to attempt a commit to master
and merge to the f14 branch. In the interest of time, I took the easy
route and just did commits to the f14 branch. Maintainers can do a
merge and fixup after the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have undefined behavior, which
could lead to data corruption.
Hi,
2010/10/6 Jesse Keating jkeat...@redhat.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have undefined
Jesse Keating jkeat...@redhat.com writes:
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have undefined behavior, which
could lead to data corruption.
...
I
Jesse Keating wrote, at 10/06/2010 07:27 AM +9:00:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As you might be aware, there was a period of roughly two weeks where a
gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and
Fedora 15. Items built with this could have undefined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/10 3:43 PM, Micha? Piotrowski wrote:
Is there somewhere a list of packages potentially broken on F14?
http://fpaste.org/7dvk/ is a list of broken F14 builds. The syntax is:
packagename : detected bad build : tag that build is in
This was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/10 3:56 PM, Tom Lane wrote:
Could you provide a list of the packages you are intending to rebuild?
See my reply to Michal
Or at least the exact dates where the bad gcc was in use?
The bad gcc was tagged into dist-f14 on Fri Sep 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/10 3:59 PM, Mamoru Tasaka wrote:
To handle the F14 scene I've come up with this strategy:
* For things tagged in dist-f14 and no newer build elsewhere, do a bump,
build and tag directly into dist-f14. While there is some risk of
2010/10/6 Jesse Keating jkeat...@redhat.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/10 3:43 PM, Micha? Piotrowski wrote:
Is there somewhere a list of packages potentially broken on F14?
http://fpaste.org/7dvk/ is a list of broken F14 builds. The syntax is:
Thanks. I hope
22 matches
Mail list logo
