FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 10-05-2010, 10:59 PM
Mamoru Tasaka
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

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 behavior, which
> could lead to data corruption.
>
<snip>
>
> 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
> breakage, it is quite minimal and with discussion from QA we are willing
> to take that chance. This work is ongoing.
>
> * For things tagged in dist-f14-updates-testing, do a bump, build and
> then edit the bodhi ticket to add the new build, and re-push to
> updates-testing. This work will begin soon.
>
> * for things tagged in dist-f14-updates-candidate, do a bump and build.
> Then look for an open bodhi ticket for that package, adjusting as
> needed. If no bodhi ticket is found, do not create a new one, just
> leave the build as is. This work will begin soon.
>

How does this strategy go for packages that the latest dist-f14 one
was rebuilt using gcc-4.5.1-3.fc14, and there is newer dist-f14-updates-candidate
one rebuilt using gcc-4.5.1-3.fc14 but no bodhi submission yet?

Regards,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-05-2010, 11:19 PM
Jesse Keating
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

-----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
>> > breakage, it is quite minimal and with discussion from QA we are willing
>> > to take that chance. This work is ongoing.
>> >
>> > * For things tagged in dist-f14-updates-testing, do a bump, build and
>> > then edit the bodhi ticket to add the new build, and re-push to
>> > updates-testing. This work will begin soon.
>> >
>> > * for things tagged in dist-f14-updates-candidate, do a bump and build.
>> > Then look for an open bodhi ticket for that package, adjusting as
>> > needed. If no bodhi ticket is found, do not create a new one, just
>> > leave the build as is. This work will begin soon.
>> >
> How does this strategy go for packages that the latest dist-f14 one
> was rebuilt using gcc-4.5.1-3.fc14, and there is newer dist-f14-updates-candidate
> one rebuilt using gcc-4.5.1-3.fc14 but no bodhi submission yet?

Hrm. I'll have to check for this specific scenario and tease out
anything which fits. In these cases I think I'll have to look by hand
at what the differences are between the dist-f14 build and the
dist-f14-updates-candidate build is, and then work with the maintainer
on whether an update should be pushed or a build with the only change
being the gcc update done and pushed instead.

- --
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyrsn8ACgkQ4v2HLvE71NVhlACfUyXs6f2tP0 0/cwc6rZkyyaSB
F/gAnRHUZ46X9gBDODfTBDCCp+8kcMcs
=ffJI
-----END PGP SIGNATURE-----
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-25-2010, 03:09 PM
Mamoru Tasaka
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

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 undefined behavior, which
> could lead to data corruption.
>
> Unfortunately I'm told that it is impossible to look at a generated
> binary and detect whether or not the binary would be effected by this
> bug. The only reliable way to tell would be to re-create the build
> environment exactly, except replace GCC with one that will detect the
> error scenario and print something. As this is a significant amount of
> work, I decided instead to just rebuild the potential problem builds.
>

Would you update the current status of this issue?

For example I checked the current status of ruby-gnome2 (because
I was going to upgrade ruby-gnome2 on F-14) and
- still the latest ruby-gnome2 on F-14 is ruby-gnome2-0.90.2-1.fc14
- this one uses the problematic gcc
- while it seemed that ruby-gnome2 was rebuilt against newer gcc
(with EVR: ruby-gnome2-0.90.2-1.fc14.1), this new ruby-gnome2 was
never pushed into dist-f14 or submitted on bodhi.

So are there any list file which suggests what packages still need
repush (after rebuild or update) for this gcc issue?

Regards,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-25-2010, 10:42 PM
Jesse Keating
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

-----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 (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.
>>
>> Unfortunately I'm told that it is impossible to look at a generated
>> binary and detect whether or not the binary would be effected by this
>> bug. The only reliable way to tell would be to re-create the build
>> environment exactly, except replace GCC with one that will detect the
>> error scenario and print something. As this is a significant amount of
>> work, I decided instead to just rebuild the potential problem builds.
>>
>
> Would you update the current status of this issue?
>
> For example I checked the current status of ruby-gnome2 (because
> I was going to upgrade ruby-gnome2 on F-14) and
> - still the latest ruby-gnome2 on F-14 is ruby-gnome2-0.90.2-1.fc14
> - this one uses the problematic gcc
> - while it seemed that ruby-gnome2 was rebuilt against newer gcc
> (with EVR: ruby-gnome2-0.90.2-1.fc14.1), this new ruby-gnome2 was
> never pushed into dist-f14 or submitted on bodhi.
>
> So are there any list file which suggests what packages still need
> repush (after rebuild or update) for this gcc issue?
>
> Regards,
> Mamoru


Current status is that almost all the builds are done and in the proper
location. There are a few stragglers, and you may have identified one.
The effort was put on hold as we get Fedora 14 ready for release.
Anything in F14 GA that could be effected will see a post-release update.

As for ruby-gnome2, the build you have in updates-testing, if it goes
stable, will suffice.

- --
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzGB7kACgkQ4v2HLvE71NXX/gCfasPcIg7JV9OchitCGWVMpRl7
dnwAoKZ1oUR/GUDotEgdo87EA7uwRHKU
=V1qH
-----END PGP SIGNATURE-----
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-24-2010, 12:04 AM
John Reiser
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

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 can process it more quickly "by eye"
than a list that is in random order. Most mail user agent (MUA) software
provides tools for string search, but using that often takes more time
than a scan-and-PageDown.

apcupsd - my build can be tagged
apiextractor - my build can be tagged
atanks - my build can be tagged
avr-gcc - my build can be tagged
awn-extras-applets - my build can be tagged
bluefish - update in testing
busybox - update in testing
calf - my build can be tagged
ccache - my build can be tagged
celt - my build can be tagged
chktex - my build can be tagged
clutter-gtk - fixed build in updates
clutter - my build can be tagged
contacts - my build can be tagged
dspam - my build can be tagged
dssi - my build can be tagged
elfutils - my build can be tagged
flowcanvas - my build can be tagged
folks - my build can be tagged
frepple - my build can be tagged
fuse-convmvfs - my build can be tagged
gappa - my build can be tagged
gcc - update in -candidate, ping jakub
gedit-vala - my build can be tagged
generatorrunner - my build can be tagged
ghc-Boolean - my build can be tagged
ghc-gio - no build
ghc-pango - my build can be tagged
ghc-terminfo - my build can be tagged
ghostscript - update in candidate, ping owner
glib-java - my build can be tagged
gnustep-examples - my build can be tagged
gretl - update in testing
gridsite - my build can be tagged
gstreamer-plugins-bad-free - my build can be tagged
gtk+extra - my build can be tagged
http-parser - my build can be tagged
igraph - update in testing
jack_capture - my build can be tagged
jana - my build can be tagged
koffice - my build can be tagged
ldc - removed from updates-testing
ledger - my build can be tagged
lensfun - my build can be tagged
libass - my build can be tagged
libclaw - my build can be tagged
libeio - my build can be tagged
libglade-java - no build
libgnome-java - no build
libgtk-java - no build
liblastfm - my build can be tagged
libmutil - my build can be tagged
libnfc - my build can be tagged
libnxt - my build can be tagged
libpst - my build can be tagged
libselinux - update in testing
libunicapgtk - my build can be tagged
libvte-java - spots build can be tagged
mailman - update in testing
matahari - my build can be tagged
meego-panel-datetime - update in testing
midori - my build can be tagged
minicom - my build can be tagged
moblin-panel-applications - my build can be tagged
moblin-panel-myzone - my build can be tagged
moblin-panel-people - my build can be tagged
moblin-panel-status - my build can be tagged
mutter-moblin - my build can be tagged (and tag into dist-f15)
mutt - my build can be tagged
nasm - update in testing
nxtrc - my build can be tagged
openchange - my build can be tagged
perl-Text-Hunspell - my build can be tagged
plee-the-bear - my build can be tagged
pspp - my build can be tagged
pycryptopp - my build can be tagged.
python-crypto - my build can be tagged
python - potential update in -candidate; pinged dmalcolm
python-storm - my build can be tagged
raul - my build can be tagged
R-ROC - my build can be tagged
rtpproxy - my build can be tagged
setuptool - my build can be tagged
shiboken - my build can be tagged
spamass-milter - my build can be tagged
syncevolution - update in testing
tar - Update in testing
tecnoballz - my build can be tagged
tigervnc - my build can be tagged
usermode - my build can be tagged
wildmidi - my rebuild can be tagged
wireshark - Update pending

--
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-24-2010, 02:42 AM
Jesse Keating
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

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
> provides tools for string search, but using that often takes more time
> than a scan-and-PageDown.

This wasn't a list of things maintainers needed to perform an action
upon. If it were, I would have sorted it, by package owner. This was
more of just a listing of the actions that /I/ would be doing, a list of
the packages.

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-24-2010, 06:32 AM
Hans de Goede
 
Default Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

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 and FWIW, I'm ok with directly tagging
the rebuilds into updates

Regards,

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

Thread Tools




All times are GMT. The time now is 01:41 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org