how to have mock use arch i686?
by Matt Domsch
This post suggests I need to be building packages using arch i686
instead of i386 as mock does by default. If so, how do I go about
doing so?
Thanks,
Matt
----- Forwarded message from bugzilla(a)redhat.com -----
Date: Tue, 16 Feb 2010 07:23:46 -0500
Subject: [Bug 565074] FTBFS opencv-2.0.0-4.fc13
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=565074
Karel Klíč <kklic(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |RAWHIDE
--- Comment #5 from Karel Klíč <kklic(a)redhat.com> 2010-02-16 07:23:43 EST ---
The -march=i386 is added by /usr/lib/rpm/redhat/rpmrc
The FTBFS system uses i386 build architecture. Koji uses i686 architecture
which has no problem with the compilation.
I fixed it by overriding CXXFLAXS on i386:
%ifarch i386
export CXXFLAGS="%{__global_cflags} -m32 -fasynchronous-unwind-tables"
%endif
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.
----- End forwarded message -----
14 years, 2 months
Fedora Talk - Asterisk
by Jon Masters
Folks,
Perhaps someone can use this to update the wiki if they have time.
The current recommendations for Fedora Talk "talking" to a private
Asterisk server are incorrect for recent versions. The following
snippets are sufficient for two-way friendly chat, and are a
simplification of the system I use for forwarding to my cell. You dial
an internal Fedora number using a prefix of "5", followed by the
extension, but you can replace that with whatever you like. I have DISA
support on my Asterisk, so I can call myself and enter a password to
access SIP from any phone - can send an example if requested.
Note the hack to munge in a "valid" 10 digit number for the outgoing
caller ID to the cellphone. Depending upon your locality, you may or may
not be able to do this, but your provider may enforce that CID must be a
valid looking 10 digit NANPA allocation as in this case. I explicitly
don't use the DNS records to lookup the correct server, ever.
Jon.
# /etc/asterisk/sip.conf:
register => FAS_USERNAME:VOIP_PASSWORD@talk.fedoraproject.org
...
[fedora]
type=friend
username=FAS_USERNAME
secret=VOIP_PASSWORD
authuser=FAS_USERNAME:VOIP_PASSWORD@fedoraproject.org
host=talk.fedoraproject.org
fromuser=FAS_USERNAME
fromdomain=fedoraproject.org
nat=yes
context=incomingfedora
insecure=very
canreinvite=no
dtmfmode=rfc2833
# /etc/asterisk/extensions.conf:
# "internal" is the local context for e.g. outgoing trusted calls
[internal]
...
exten => _5.,1,Set(CALLERID(number)=VOIP_EXTENSION)
exten => _5.,2,Set(CALLERID(name)="FAS_USERNAME Fedora Talk")
exten => _5.,3,Dial(SIP/${EXTEN:1}@fedora,300,trWw)
exten => _5.,4,PlayBack(invalid)
exten => _5.,5,Hangup
# The above supports call forwarding, recording, and other options
...
[incomingfedora]
# only do this if you have rules for call recording and forwarding
include => parkedcalls
exten => h,1,HangUp()
exten => s,1,Answer()
exten => s,2,Wait(1)
exten => s,3,PlayBack(call-forwarding)
exten => s,4,Goto(VOIP_EXTENSION,1)
exten => s,5,HangUp()
exten => 3,1,VoiceMail(VOICEMAIL_EXTENSION)
exten => 3,2,HangUp()
exten => _5100570,1,Answer()
exten => _5100570,2,WaitExten(1)
exten => _5100570,3,BackGround(one-moment-please)
exten => _5100570,4,WaitExten(1)
exten => _5100570,5,Set(CallerIDNumber=15550000000${CALLERID(number)})
exten => _5100570,6,Set(CallerIDNumber=1${CallerIDNumber:-10:10})
exten => _5100570,7,Set(CALLERID(number)=${CallerIDNumber})
exten => _5100570,8,Dial(IAX2/SIP_PROVIDER/CELL_NUMBER,300,tdmWw)
exten => _5100570,9,HangUp()
exten => *,1,Goto(3,1)
exten => *,2,HangUp()
# Have various fun
Jon.
14 years, 2 months
Might need to orphan glade3
by Adam Miller
Hello all,
Recently glade3 was orphaned and I left it alone for about a week
and nobody had picked it up yet and since I use it I decided to snag
it up. I felt it was long enough that nobody really seemed to want to
take it over themselves, I figured I would take it and try to triage
bugs and maintain the package in general. I have however hit an
unfortunate realization about glade3, I lack the time to devote to the
this package that it really deserves and I feel that the package (and
thus the distro/repos) are lacking because of it. I've just been
really busy lately and I'd hate to be the reason the package isn't
being kept up. There have been more bugs against glade3 in the last
week than all my other packages combined and I just don't know that I
could really keep up with it.
If there are any individuals willing to share some of the work
load I will continue to hold ownership, or if there is a brave sole
out there who is willing to take ownership over completely I will be
willing to help out as much as I am able.
Many thanks to all,
-AdamM
--
http://maxamillion.googlepages.com
---------------------------------------------------------
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
14 years, 2 months
ABRT unusable again
by Christoph Wickert
What's wrong with ABRT? ALl the backtraces I get are unusable again. If
Thunar crashes, not even Thunar-debuginfo gets installed.
abrt 1.0 worked here, then came 1.0.2 which was broken. 1.0.3 was
working again, but got superseded be 1.0.4 only a few of days later.
This means that most of the time, all the bugs submitted are basically
useless.
For me as the maintainer it is a lot of work to reply to all these
useless reports and for our users it's just frustrating if all their
reports get closed INSUFFICIENT_DATA.
If the situation doesn't change any time soon, we IMHO should consider
disabling abrt until the issues are fixed.
Regards,
Christoph
14 years, 2 months
Fedora 13 Software Translation
by Noriko Mizumoto
It is 16-Feb today, Software String Freeze.
All Fedora translators are expecting NO more String change in any
Fedora13 packages, and looking at to complete as many translation as
possible from now on till the translation deadline. Please make sure
that POT is up-to-date with latest strings.
noriko
Fedora Localization Project
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
14 years, 2 months
Fedora 13 Branching (and thus freezing) tomorrow
by Jesse Keating
Tomorrow (or well the day after tomorrow to some of you) we will be
branching off F-13 in CVS. This will start at 00:00 UTC on Feb 17.
After this point, when the outage ends, all builds for Fedora 13 will
happen from the F-13/ branch in CVS. All builds must go through bodhi
in order to make it into Fedora 13. When you submit your build to
bodhi, please push to testing first, as it will allow your peers to test
your update before it makes it into the Fedora 13 tree.
For those of you who maintain a critical-path package, net positive
karma from releng and/or QA plus at least one more net positive karma is
required before your package can move out of testing and into Fedora 13.
We're still working on the wiki documentation for all of this, but hope
to have a good chunk in place tomorrow.
Builds from devel/ will continue to be pushed to rawhide each night and
devel/ can be considered open for Fedora 14 development items.
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan has some
info about the upcoming change and base information we'll use when
editing the other wiki pages.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
14 years, 2 months
Upcoming Fedora 13 Schedule Tasks
by John Poelstra
Start End Name
Thu 11-Feb Wed 17-Feb Test Alpha 'Test Compose'
Mon 15-Feb Mon 15-Feb Package Alpha Wallpaper
Tue 16-Feb Tue 16-Feb Software String Freeze
Tue 16-Feb Tue 16-Feb Development: Start Alpha Freeze
Tue 16-Feb Tue 02-Mar Development: Alpha Freeze
Thu 18-Feb Thu 18-Feb Start Alpha Compose
Thu 18-Feb Thu 18-Feb Compose Alpha Candidate
Thu 18-Feb Thu 25-Feb Test Alpha Candidate
Fri 19-Feb Fri 19-Feb Alpha Blocker Meeting (F13Alpha) #3
Wed 24-Feb Wed 24-Feb Alpha Go/No-Go Meeting (20:00 EST)
Thu 25-Feb Thu 25-Feb Alpha Project Wide Release Readiness Meeting
Thu 25-Feb Thu 25-Feb Start Stage & Sync Alpha to Mirrors
Thu 25-Feb Tue 02-Mar Stage & Sync Alpha to Mirrors
Fri 26-Feb Fri 26-Feb Alpha Export Control Reporting
Tue 02-Mar Tue 02-Mar Allow Pre-branch Fedora 13
Tue 02-Mar Tue 02-Mar Alpha Public Availability
Tue 02-Mar Tue 02-Mar End Alpha Freeze
Tue 02-Mar Tue 23-Mar Alpha Testing
14 years, 2 months
