Fedora developers running Rawhide and having source upload issues...
by Jesse Keating
Curl was recently modified to link against nss instead of openssl for
it's ssl capabilities. For some reason, this does not work with our
source look aside cache. If you are having issues uploading new
sources in your packages and you're using rawhide, make sure that
you're using a curl no newer than 7.16.4-2. If you have a newer
version, downgrade using the packages found at
http://koji.fedoraproject.org/koji/buildinfo?buildID=13319
We'll work with the curl developers to resolve this issue as soon as
possible.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 6 months
Heads up, slight tree path change
by Jesse Keating
As part of a continuing effort to make derivative distributions of
Fedora easier, we're making the path names within the tree a bit more
generic. Instead of os/Fedora/<packages> the path will now be
os/Packages/<packages>. This may cause you some shuffle or churn when
syncing, and I apologize for the late notice. We've been having a heck
of a time getting a rawhide to compose and I hadn't taken the time to
send a mail about this.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 6 months
Scripted rebuilds coming up for ppc32 selinux fix.
by Jesse Keating
There are still a number (237 as of this morning) of packages that need
to be rebuilt so that their ppc32 binaries will not cause selinux
denials. This is very important to having a successful Fedora 8 Test 2
release for ppc. As such, Fedora Release Engineering will be doing a
scripted rebuild of the remaining packages left to rebuild. We will
not be fixing any open bugs, doing any license audit, or any other
manual type work, it will merely be a scripted bump of the spec file
and a build (failures will be investigated). We are not scripting the
rebuilds of anything else at this time, just those packages marked as
needing rebuild for ppc32 at
http://jkeating.fedorapeople.org/really-need-to-rebuild
These builds will begin shortly, after the next update to the
really-need-to-build list.
We apologize for any inconvenience these automated builds may cause
you, especially given such short notice, however it is necessary that we
complete these builds in time for Test2.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 6 months
Bugzilla Server Outage Announcement
by Dave Lawrence
S E R V E R O U T A G E A N N O U N C E M E N T
=================================================
Scheduled Date:
8/24/2007
Scheduled Time:
19:00 EDT (-0400)
Estimated Time Required:
8-10 Hours
Performed By:
Red Hat Engineering Operations
People/Groups Impacted:
Bugzilla/Hardware Catalog Users
Site/Services Affected:
Bugzilla.redhat.com, Hardware.redhat.com
Impact:
Bugzilla/Hardware db and web will be completely unavailable until
migration is complete.
Description:
We will be doing the final migration to a new external co-located
Bugzilla environment.
Changes
- Now using native MySQL replication. Master w/ Slave hot
backup
- Now utilizing two fail over web servers
- Login names lowercased: no longer permit mixed case.
All duplicates have been removed.
- Cookies: authentication has been modified since it is no
longer
possible to authenticate based on ip address.
Everyone will need to re-login.
Contact
Please email us at bugzilla-owner(a)redhat.com if you have any concerns.
16 years, 7 months
Perl hiccup in rawhide buildroots
by Jesse Keating
A malfunctioning build of perl landed in the rawhide buildroots a few
minutes ago. This caused almost every build that started afterward to
fail with a mock error 100 (unable to init the build root). I've
untagged the bad build of perl and a newRepo task has started that has
a better build of perl on it. Once this task
(http://koji.fedoraproject.org/koji/taskinfo?taskID=113051 ) is done,
you'll need to resubmit your builds for rawhide.
Very sorry for the interruption in service.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 7 months
String Freeze Policy effective from today
by Dimitris Glezos
Hey all.
A quick announcement that from today we have a String Freeze Policy active:
http://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
Maintainers of packages that get translated by the Localization Project would
want to take a look at the policy, as it describes what to do if you really need
to break the freeze date.
Reminding that the string freeze for Fedora 8 is the 28th of August, as noted on
the Release Schedule. For more information on String Freezes, jump to:
http://fedoraproject.org/wiki/L10N/Freezes#string
On this page there is also a section for Translation Freezes (#translation),
which basically is a date where we guarantee translators that all contributions
done up to that point will be included in the final Release.
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
16 years, 7 months
Notice: Fedora 8 Feature Freeze - 2 WEEKS LEFT
by Warren Togami
http://fedoraproject.org/wiki/Releases/8/Schedule
Feature Freeze for Fedora 8 is coming soon on August 28th. The goal of
the feature freeze is to be sure that the components are in a known and
tested state before the release of Fedora 8.
Notes
=====
1) Top Priority for the freeze are components within the default
installations.
2) Secondary in freeze importance are packages within the entire Fedora
Collection. Major changes after the Feature Freeze date are highly
discouraged.
3) New packages may continue to be added to the devel branch during this
period, as long as they do not require major changes of existing packages.
4) Contact FESCo if you need clarification or permission for an
exception to the Feature Freeze.
5) If your feature misses the deadline, don't feel too disheartened.
The F9 feature freeze is coming ~6 months later.
6) At some (yet to be determined) point we have to stop additions of new
packages to F8 when we reach the DEEP FREEZE. This is when we stop the
churn of new and updated packages in order to check consistency of the
repository prior to the final release. By the calendar, F8 Final devel
freeze is currently scheduled for October 23rd.
If you have any questions about the Feature Freeze, please ask on
fedora-devel-list.
Thanks,
Warren Togami
wtogami(a)redhat.com
16 years, 7 months
F8 packagers note: new find-debuginfo.sh script
by Roland McGrath
Coming soon to a dist-f8 near you will be an rpm-build package that
includes a revamped find-debuginfo.sh script. This will be a new
rpm-build > 4.4.2.1-3. You can find an unofficial build with the new
script right now in http://koji.fedoraproject.org/scratch/roland/task_94236/
Most maintainers should not need to worry about the new script.
It should silently do the right thing without any attention from you.
If you see any new problems, please harrass me immediately.
For any packages doing special non-default debuginfo packaging,
please talk to me directly. I've taken care of kernel and glibc,
which are the only special cases I know of.
The only problem I know to expect is improperly built DSOs, where broken
package makefiles run ld -shared directly instead of via gcc. I just
posted about the details of this:
https://www.redhat.com/archives/fedora-maintainers/2007-August/msg00135.html
If this hits you, it was already a bug in your package, and now the tools
are telling you about it early.
If you see any messages like:
*** ERROR: No build ID note found in ...
then look into how the named binaries are linked. If it's not a simple
case of changing ld -shared to $(CC) -shared, you can always contact me
for help figuring it out.
If anything else about the find-debuginfo.sh part of your build.log, or the
-debuginfo rpm that results, looks suspect to you, don't hesitate to
contact me. The intended changes are the build-id magic, smart handling of
hard links and symlinks, and generating all the correct %dir lines.
Thanks,
Roland
16 years, 7 months