Proper steps to get to testing
by Russ Hubbard
Hello all,
What steps do I need to take to get to the current testing version of the
distro. Is it as simple as installing Core 1, and doing a yum or up2date
with the development packages? Any help at all would be much appreciated.
Thanks!
Russ
20 years, 4 months
Fedora Core 1 Testing Update: glibc-2.3.2-101.4
by Jakub Jelinek
---------------------------------------------------------------------
Fedora Update Notification
FEDORA-2003-045
2004-01-07
---------------------------------------------------------------------
Name : glibc
Version : 2.3.2
Release : 101.4
Summary : The GNU libc libraries.
Description :
The glibc package contains standard libraries which are used by
multiple programs on the system. In order to save disk space and
memory, as well as to make upgrading easier, common system code is
kept in one place and shared between programs. This particular package
contains the most important sets of shared libraries: the standard C
library and the standard math library. Without these two libraries, a
Linux system will not function.
---------------------------------------------------------------------
Update Information:
This glibc update fixes lots of bugs in the regular expression
matcher and speeds it up. It fixes a couple of other bugs as well.
---------------------------------------------------------------------
* Tue Jan 06 2004 Jakub Jelinek <jakub(a)redhat.com> 2.3.2-101.4
- some further regex speedups
- fix re.translate handling in regex (#112869)
- change regfree to match old regex behaviour (what is freed
and clearing of freed pointers)
* Tue Dec 30 2003 Jakub Jelinek <jakub(a)redhat.com> 2.3.2-101.3
- fix pmap_set fd and memory leak (#112726)
- fix backreference handling in regex
* Tue Dec 30 2003 Jakub Jelinek <jakub(a)redhat.com> 2.3.2-101.2
- fix to make pthread_setcancelstate (PTHREAD_CANCEL_DISABLE, )
really disable cancellation (#112512)
- lots of regex fixes and speedups (#110401)
- fix nextafter*/nexttoward*
- handle 6th syscall(3) argument on AMD64
- handle memalign/posix_memalign in mtrace
- fix linuxthreads memory leak (#112208)
- remove throw () from cancellation points in linuxthreads (#112602)
- fix NPTL unregister_atfork
- fix unwinding through alternate signal stacks
- fix atan2
- fix pshared condvars in NPTL
- fix pthread_attr_destroy for attributes created with
pthread_attr_init(a)GLIBC_2.0
- add BuildPrereq texinfo (#110252)
- fix ceill/floorl on AMD64
- work around IA64 gas bug with unwind info and .align
- fix NPTL configure
- allow dlopen after fork () in threaded programs
- compute IA-64 default thread stack size correctly
- fix thread stacks with ulimit -s not a multiple of a page size
- randomize PIE shared libraries, honor LD_USE_LOAD_BIAS env variable
- fix execstack handling on kernels without exec-shield
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/1/
cdf53b3e82b4b18f0ff3b7b05204e4ff SRPMS/glibc-2.3.2-101.4.src.rpm
deb41a4107321ad9e5d67adde39c1ee5 i386/glibc-2.3.2-101.4.i386.rpm
46c90bab86b550cd7f43c15e21491892 i386/glibc-devel-2.3.2-101.4.i386.rpm
d8d3efcfda021f075e6a26c5a8532146 i386/glibc-headers-2.3.2-101.4.i386.rpm
ef60bc1717e7341d67a59081cd7f7a0c i386/glibc-profile-2.3.2-101.4.i386.rpm
2ab49196e7b586d269cb4fbdc9fa5681 i386/glibc-common-2.3.2-101.4.i386.rpm
adbc0ef23edbb23dcc87d77163e4ea50 i386/nscd-2.3.2-101.4.i386.rpm
82fb788ea6777d9c4c18caf6f388b8d3 i386/glibc-debug-2.3.2-101.4.i386.rpm
187ed7af5b2c09d8cda76000fd5d443b i386/glibc-utils-2.3.2-101.4.i386.rpm
6694ac4caa7ae01cf94282c3c721b4a0 i386/debug/glibc-debuginfo-2.3.2-101.4.i386.rpm
674950ebd9ae3deef47f2ddb90e0ef13 i386/debug/glibc-debuginfo-common-2.3.2-101.4.i386.rpm
41062334adb203c37ee2c141883c5b5a i386/glibc-2.3.2-101.4.i686.rpm
5bf19599f529a271e54fae4455be9337 i386/nptl-devel-2.3.2-101.4.i686.rpm
dad036887d3a9dda20e78c9eb7db9582 i386/debug/glibc-debuginfo-2.3.2-101.4.i686.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command.
---------------------------------------------------------------------
20 years, 4 months
Fedora Core 1 Testing Update: gcc-3.3.2-5
by Jakub Jelinek
---------------------------------------------------------------------
Fedora Update Notification
FEDORA-2003-044
2004-01-07
---------------------------------------------------------------------
Name : gcc
Version : 3.3.2
Release : 5
Summary : Various compilers (C, C++, Objective-C, Java, ...)
Description :
The gcc package contains the GNU Compiler Collection version 3.3.2.
You'll need this package in order to compile C code.
---------------------------------------------------------------------
* Fri Dec 19 2003 Jakub Jelinek <jakub(a)redhat.com> 3.3.2-5
- update from gcc-3_3-branch
- PRs target/11992, target/13122, optimization/13037,
target/13256, target/12598, optimization/13318,
optimization/13060, optimization/12965, target/13354,
optimization/4490, target/13150, middle-end/10060,
driver/13211, target/13302, target/11322, target/12467,
12969, target/8407, 10239, 11640, c++/12253,
c++/13262, c++/13323, fortran/12633, libstdc++/6243,
libstdc++/11612, libstdc++/12496, libstdc++/13290,
libstdc++/9371, libstdc++/9546, libstdc++/10093,
libstdc++/10095
- fix __builtin_expect in C++ code
- fix unwinding through SA_ONSTACK signal frames on IA-64
* Fri Dec 12 2003 Jakub Jelinek <jakub(a)redhat.com> 3.3.2-4
- fix unwinding through signal frames on IA-64
* Wed Dec 03 2003 Jakub Jelinek <jakub(a)redhat.com> 3.3.2-3
- update from gcc-3_3-branch
- PRs optimization/11634, other/12505, optimization/13041,
target/12900, optimization/12926, optimization/12953,
target/12865, optimization/10467, optimization/11741,
c++/2094, libobjc/11433, c++/2094, libstdc++/12297,
libstdc++/12594
- BuildRequire texinfo (#111168)
- Require /sbin/install-info for libgcj (#110904)
- fix structure initialization with const fields and mostly zeros
in the initializer (#110966)
- fix gcj on PPC64 not emitting needed nop after branch and link
to non-local Java method (Richard Henderson)
- some more > 2GB handling fixes (Jan Hubicka)
* Mon Nov 10 2003 Jakub Jelinek <jakub(a)redhat.com> 3.3.2-2
- update from gcc-3_3-branch
- PRs bootstrap/12666, target/11598, libgcj/10610, target/12654,
target/12690, target/12712
- fix ICE with C++ initializers (Jason Merrill, #109283, PR c++/12726)
- fix handling of functions with > 2GB stack frames
- fix handling of objects larger than 2GB or 4GB (Jan Hubicka and others)
- fix Fortran COMMONs bigger than 2GB (#106542)
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
b514d749a559fe3e4f9013bc97d696d9 SRPMS/gcc-3.3.2-5.src.rpm
c2a551a2f40c4fd5c0473ade5c03fb28 i386/gcc-3.3.2-5.i386.rpm
834d868612f51526d6b214591dbffbdc i386/libgcc-3.3.2-5.i386.rpm
dae4a95954641cc8e63ff09bbb490dd5 i386/gcc-c++-3.3.2-5.i386.rpm
6366a364a85244f116e394f85e356403 i386/libstdc++-3.3.2-5.i386.rpm
e8b2060705fdc0060850be1829f73fb2 i386/libstdc++-devel-3.3.2-5.i386.rpm
847cdf82326360cbb0bd063a04e0fd52 i386/gcc-objc-3.3.2-5.i386.rpm
acdfdb4aaadc6ac0f0766d1775fea322 i386/libobjc-3.3.2-5.i386.rpm
d7dc2ac508ce55a785938767bc51e63a i386/gcc-g77-3.3.2-5.i386.rpm
034737a81f67efbb758b592b72de0ca5 i386/libf2c-3.3.2-5.i386.rpm
dea57844e754ee6c59b68d603968d9b8 i386/gcc-java-3.3.2-5.i386.rpm
b5d98773111b09e824b625dd3045eea8 i386/libgcj-3.3.2-5.i386.rpm
91f855112f414307672dc4933eea7633 i386/libgcj-devel-3.3.2-5.i386.rpm
967d01bf80d9a296c15175d2d615c0b5 i386/cpp-3.3.2-5.i386.rpm
bbf3e5ce71f130c4de5e60401196e92a i386/gcc-gnat-3.3.2-5.i386.rpm
95042e9032fc4cd10e32a28151288180 i386/libgnat-3.3.2-5.i386.rpm
63a3d046fa9a9ff060637a0b3c46497d i386/debug/gcc-debuginfo-3.3.2-5.i386.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command.
---------------------------------------------------------------------
20 years, 4 months
Updated kernel package needs testing.
by Dave Jones
Quite a few changes here, especially to ext2/3 and fs/vm subsystems.
Handle with care for now.
Dave
---------------------------------------------------------------------
Fedora Update Notification
FEDORA-2003-048
2004-01-07
---------------------------------------------------------------------
Name : kernel
Version : 2.4.22
Release : 1.2149.nptl
Summary : The Linux kernel (the core of the Linux operating system)
Description :
The kernel package contains the Linux kernel (vmlinuz), the core of your
Fedora Core Linux operating system. The kernel handles the basic functions
of the operating system: memory allocation, process allocation, device
input and output, etc.
---------------------------------------------------------------------
* Wed Jan 07 2004 Dave Jones <davej(a)redhat.com>
- Merge several EXT2/3 fixes from 2.4.25pre
- EXT2/3 fixes.
- Reclaim pages in truncate
- 2.6 EA symlink compatibility
- forward-compatibility: online resizing
- Allow filesystems with expanded inodes to be mounted
- Handle j_commit_interval == 0
- IDE timeout race fix
- Merge some 2.4.23pre patches that were missed.
- Make root a special case for per-user process limits.
- out_of_memory() locking
- Drop module count if lockd reclaimer thread failed to start
- Fix potential fsync() race condition
- s/Red Hat/Fedora/ in specfile (#112992)
- Add PCI ident for new Intel e1000 card. (#105046)
- Actually wire up 3c59x ethtool ioctl.
- Fix up numeric sysctls to match mainline.
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/1/
0528ff2ef4b077e34a6e9f0bdc4c4c43 SRPMS/kernel-2.4.22-1.2149.nptl.src.rpm
cf2da4c300650d6a68aeb3141e8de93e i386/kernel-source-2.4.22-1.2149.nptl.i386.rpm
b6ffe91b11cb64af23f08de19c965677 i386/kernel-doc-2.4.22-1.2149.nptl.i386.rpm
37bdb02f23cd936fc6a68c8b2f176275 i386/kernel-BOOT-2.4.22-1.2149.nptl.i386.rpm
fe89710f267b238c9e5fcdf3d2658383 i386/debug/kernel-debuginfo-2.4.22-1.2149.nptl.i386.rpm
68de6d015862dfc63d40b68a8fa1affa i386/kernel-2.4.22-1.2149.nptl.i586.rpm
9714ae57c042a42400336c06ae07f2c3 i386/debug/kernel-debuginfo-2.4.22-1.2149.nptl.i586.rpm
ccc831fbb9ffa04ed7504f058411febc i386/kernel-2.4.22-1.2149.nptl.i686.rpm
257145cc01f1ea38fbcf22304b93d566 i386/kernel-smp-2.4.22-1.2149.nptl.i686.rpm
baff2d70eb4e24b626511b9f3feacccd i386/debug/kernel-debuginfo-2.4.22-1.2149.nptl.i686.rpm
70b1314d932ff4283cab39a289b7aedc i386/kernel-2.4.22-1.2149.nptl.athlon.rpm
af27b81477979c6ff42a9e1475adaf3b i386/kernel-smp-2.4.22-1.2149.nptl.athlon.rpm
307fb0efbbc54a55e3d0c2a4b134c691 i386/debug/kernel-debuginfo-2.4.22-1.2149.nptl.athlon.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command.
---------------------------------------------------------------------
20 years, 4 months
second fresh install broken after update - gnome broken
by Vanco, Don
Well, I've got me second system in as many weeks that has had something
broken by updating it. I cannot get gnome to start, and sadly it gives no
error output.
Details:
Fresh install of FC1 - gnome / X works fine (Compaq DL320, ATI Rage XL
Chipset)
Tried to update system via up2date - this lead to a cyclical redundancy
where the RPMs would not installed because they failed both MD5 check and
appropriate key signature (after installing key???), and no combination of
--nosignature and/or --nomd5 could satisfy RPM to install.
So - "apt-get update" and let it do it's thing.
Now the system will not let a user start X. I can run gdm, but if root or a
user tries to log in or even launch X via "startx" (where their default
session is gnome) they're immediately bounced out. KDE appears fine.
Adding a new user or deleting the .gnom* stuff does nothing. Starting X and
then trying to use "gnome-session" rewards me with an immediate seg fault.
Aside from this gnome mess - when will the update process stop breaking
systems? Pretty much all of my peers (and me if it's not obvious) are
tiring of Fedora because of it's inability to provide a stable
platform...... and relying solely on an apt repository or yum repository is
still to immature for Fedora - they're just not a single site I've found
that doesn't have issues of some kind... Using multiple apt/yum
repositories appears to be disastrous - I've loaded 4 systems with FC1
(after numerous beta machines) and have a "50 percent failure rate" on
machines that have been subsequently rendered problematic (at best) or
broken (at worst) by the upgrade process in one fashion or another.....
Fedora - the new Mandrake!
Don
20 years, 4 months
Bug Day 10 : Jan 7th : Happy New Year!
by Jef Spaleta
I hope everyone had a restful holiday. I would have, but my little
sister decided to take and hide the playstation 2 memory card from me
over the break so i couldn't finish building all the ultimate coasters
in rollercoaster tycoon and unlock the hidden theme park...but enough
about me.
Well to be perfectly honest with everyone, my attempt at finding a theme
for this week went up in smoke when someone who will rename nameless (
his initials are Dave Jones) decided the specific testing i was going to
ask people to help out with wasn't needed.
But let's recap on where things stand with general bug busting issues,
that you, as an enthusiastic Fedora community member can make a
difference in.
* Fedora.us QA:
Fedora.us still needs continuing help with community QA efforts to get
packages published. There are 314 packages in the QA list waiting for
community input before they are ready to be pushed out to the
repositories for general use. (http://www.fedora.us/QA)
I want to remind everyone that until Fedora Extras exists, the fedora.us
repositories are the place the Fedora leadership is encouraging people
to contribute extra packages. But submitting packages isn't enough. It
is important for community members to check over the submitted packages
and make sure they are good enough to be released to the general public.
Making a commitment to help QA packages waiting to be published at
fedora.us is a very good to get involved in development as a community
member. References:
http://www.fedora.us/wiki/PackageSubmissionQAPolicy
http://www.fedora.us/wiki/FedoraDocuments
* Vesa Driver Testing: http://www.fedora.us/wiki/VesaDriverTesting :
Mike Harris has asked for testing of the Vesa video driver, which could
be used for a "safe mode" in Fedora. The problem is that many BIOS's
Vesa modes are broken, so he needs a good blacklist of broken situations
with the Vesa driver. Please follow the instructions at the url given
above and test your video hardware with the vesa driver, and file a bug
report if vesa does not work with your video hardware.
*Fedora Bugzilla Triage:
An effort to to be able to organize Fedora community into a nimble
bugzilla strike force who can take the burden of day to day bugzilla
maintenance from the core developers. What that means in less humourous
terms is...finding a way to have community members going into bugzilla
and closing things like duplicate bugs, and finding the easyfix bugs and
marking them, so its easier for the developers to find and work on
bugreports. If we can help save developers time searching through
bugreports by helping organize the reports, developers can spend more
time actually fixing bugs. Here's a basic sketch of how its going to
work:
1)you search through the Fedora bugs at bugzilla.redhat.com looking for
things like duplicates and easyfix bugs.
2)you find a bug report that you think is a duplicate
3)stop into #fedora-bugs irc channel and discuss whether the bug is
actually a duplicate or not with people there
4)add a comment triage->duplicate #bugnumber-of-duplicate
5)a trusted triage community member will search for the
triage->duplicate string and then close the bug as being a duplicate
I promise to spend tomorrow's bug day going in and taking care of as
many of the community supplied triage comments sitting in bugzilla at
the moment. And please, if you are interested in helping out with triage
please hop on #fedora-bugs channel on the freenode irc network tomorrow
during 9am-5pm EST or drop me an email message. And if you are already
made an effort to help out experimenting with triage->comments, find me
tomorrow or send me an email so I can get a head count. I'm serious
about starting to follow up on the comments tomorrow as part of the days
bug day activities.
-jef
20 years, 4 months
RE: New test kernel.
by Randal, Phil
> > But, trying to boot a single processor Dell PowerEdge 2650
> with it was not
> > successful - it hung at some point in the startup. As it
> happened at 6:30pm
> > last night I haven't any detailed documentation, and it is
> unlikely that
> > I'll have the time to investigate further. The same box runs
> > kernel-2.4.22-2129 happily.
>
> Does 2135 behave normally ?
>
> Dave
I've reflashed the PE2650 BIOS from release A15 to A17 and happily booted it
with the latest kernel-2.4.22-1.2138.nptl and .nptlsmp kernels.
So far so good.
Cheers,
Phil
---------------------------------------------
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK
20 years, 4 months
Installing the development branch?
by Charlie Lesh
Hey all:
What is the best way to install and run the development branch?
Should I install core 1, then update all of my RPMs with a rawhide source?
Is there a more elegant and direct solution?
Is there a way (script?) to make the install CDs from a locally mirrored
copy?
This seems like it might be a FAQ, but I couldn't find the answer anywhere.
I don't really want to wait until the release of test1 in February to
start playing!
Thanks in advance,
-Charlie
20 years, 4 months
SCSI errors on cd burning
by Alan
ide-scsi has been a real pain in the ass.
I am using the current Fedora kernel kernel-smp-2.4.22-1.2138.nptl built
for Athlon. I am using a dual athlon 2100+MP system with 512M and a
Pioneer A-05 DVD burner.
cdrecord-2.01-0.a19.2
When I try and use k3b to burn a bin/cue disc or DVD, I get errors.
Here is the output from cdrecord. Notice the SCSI errors. What is
weird is I get the same scsi errors if I am not using ide-scsi!
cdrecord
-----------------------
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.25
/usr/bin/cdrecord: Warning: using inofficial libscg transport code
version (schily - Red Hat-scsi-linux-sg.c-1.75-RH '@(#)scsi-linux-sg.c
1.75 02/10/21 Copyright 1997 J. Schilling').
SCSI buffer size: 64512
/usr/bin/cdrecord: This version of cdrecord does not include
DVD-R/DVD-RW support code.
/usr/bin/cdrecord: If you need DVD-R/DVD-RW support, ask the Author for
cdrecord-ProDVD.
Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003
Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.7'
Driveropts: 'burnfree'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER '
Identifikation : 'DVD-RW DVR-105 '
Revision : '1.21'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x0014
Profile: 0x0013
Profile: 0x0011
Profile: 0x0010
Profile: 0x000A
Profile: 0x0009 (current)
Profile: 0x0008
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P
RAW/R96R
Drive buf size : 1267712 = 1238 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 1 MB
Track 02: data 803 MB
Total size: 804 MB (79:39.65) = 358474 sectors
Lout start: 804 MB (79:41/49) = 358474 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11634 (97:26/66)
ATIP start of lead out: 359848 (79:59/73)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 1374
Starting to write CD/DVD at speed 16 in real SAO mode for single
session.
Last chance to quit, starting real write in 2 seconds.
1 seconds.
0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Performing OPC...
Sending CUE sheet...
/usr/bin/cdrecord: CUE sheet not accepted. Retrying with minimum
pregapsize = 1.
/usr/bin/cdrecord: Input/output error. send_cue_sheet: scsi sendcmd: no
error
CDB: 5D 00 00 00 00 00 00 00 30 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0E 00 00 00 00 26 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x26 Qual 0x00 (invalid field in parameter list) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.010s timeout 200s
/usr/bin/cdrecord: Cannot send CUE sheet.
/usr/bin/cdrecord: Could not write Lead-in.
Writing time: 6.569s
/usr/bin/cdrecord: fifo had 64 puts and 0 gets.
/usr/bin/cdrecord: fifo was 0 times empty and 0 times full, min fill was
100%.
cdrecord comand:
-----------------------
/usr/bin/cdrecord -v gracetime=2 dev=0,0,0 speed=16 -dao
driveropts=burnfree cuefile=/export2/home/alan/News/Pan/Movies/ww107.cue
-eject
Ideas?
--
"I say to you that the VCR is to the American film producer and the
American public as the Boston strangler is to the woman home alone."
- Jack Valenti in 1982 in testimony to the House of Representatives on
why the VCR should be illegal.
20 years, 4 months
