correct spec file creation
by Stefan Schulze Frielinghaus
I found some differences in the building process of a spec file.
I will refer to the following document as A
http://docs.fedoraproject.org/developers-guide/ch-rpm-building.html
and this one as B
http://fedoraproject.org/wiki/Packaging/Guidelines
A suggests to use %makeinstall (as seen in the example and in the
description of the example) while B says exactly the opposite _not_ to
use %makeinstall ("Why the %makeinstall macro should not be used").
Another difference ist the use of PreReq (and maybe BuildPreReq too?)
which is used in A and B suggests _not_ to use it.
While I'm new to RPM and I just wanted to setup my first packet, could
someone point out the difference and just say what is right and wrong?
cheers,
Stefan
16 years, 7 months
Koji Garbage Collection
by Jesse Keating
We are about to roll out garbage collection for Koji. Please review the
document linked below.
http://fedoraproject.org/wiki/Koji/GarbageCollection
As part of garbage collection, builds that are no longer needed will be
deleted. The owner of the build will receive an email notification of
the impending deletion and there is a grace period. To reduce the amount
of email, multiple notifications to the same user will be combined into
one message.
If you receive such a notification, deleting the builds is most likely
the right thing. If you feel differently, please see the document linked
above for instructions.
The initial collection of builds that can be deleted will happen tonight.
Because there is an urgent need to free space on the Koji server, we
will be shortening the grace period during the initial rollout. This
means that you will need to act fast if you need to save a build that
you receive a notification about. The first round of deletions will kick
in late Friday evening.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
16 years, 7 months
dwysocha : User unknown in local recipient table
by Michael Schwendt
Somebody's mail address in the Fedora Account System refuses delivery
of mail:
Traceback (most recent call last):
File "./upgradecheckspam.py", line 267, in ?
main()
File "./upgradecheckspam.py", line 258, in main
s.sendmail(mail_from, [owner], msg.as_string())
File "/usr/lib64/python2.3/smtplib.py", line 687, in sendmail
raise SMTPRecipientsRefused(senderrs)
smtplib.SMTPRecipientsRefused: {'dwysocha': (550, '<dwysocha>: Recipient address rejected: User unknown in local recipient table')}
16 years, 7 months
Re: Some thoughts about firmware inclusion.
by Nicolas Mailhot
Le Mar 23 octobre 2007 12:56, Peter Lemenkov a écrit :
> 2007/10/23, Nicolas Mailhot <nicolas.mailhot(a)laposte.net>:
>
>> That probably means you need to package "firmware" building tools in
>> fedora and use them to build the "firmware" source in the "firmware"
>> package. And we may have been lax on the subject in the past for
>> games
>> but as the OP message shows it's a quick path to shipping pre-built
>> closed java or.Net binaries and effectively having a non-free
>> system.
>
> Firmware and ROMs for virtual machines is the same thing as graphics
> and music for games.
No it's not. One is code the other content.
> We don't package them from sources but we package
> existing *prebuilt* graphics/music/maps /etc.
This is IMHO a misinterpretation of Fedora guidelines, and leads to
shipping (for example) a pre-built Eclipse or any proprietary
Java/.Net app because they're "bytecode" executed in "virtual
machines"
It's clearly more convenient for you not to have to untangle ROM build
systems but it's not what Fedora is supposed to be.
Regards,
--
Nicolas Mailhot
16 years, 7 months
Packaging doc/xls-files?
by Peter Lemenkov
Hello All!
Trying to package one software piece I found that there is one
*.doc-file between documentation. There is also its html-source
created with Microsoft Word so I may simply drop non-standard file
format in this particular case, but what should someone do later in
such cases? Are any RFC's or policies for handling such situations?
I personally vote against proprietary doc-format, but we include some
software to deal with so maybe its just my personal paranoia.
--
With best regards!
16 years, 7 months
repoview & templates in Fedora site
by Fernando Lopez-Lezcano
Hi all, is there a place where the "modified" repoview used in the
Fedora site could be found? I really could use the layout (where package
pages do not include the version in their name). I'm trying to tweak the
original 0.5.2 to get the same result but it is not that easy...
Thanks...
-- Fernando
16 years, 7 months
FESCo Meeting Summary for 2007-10-25
by Brian Pepple
= Members Present =
* Brian Pepple (bpepple)
* Jason Tibbitts (tibbs)
* Jesse Keating (f13)
* Dennis Gilmore (dgilmore)
* Bill Nottingham (notting)
* Tom Callaway (spot)
* Warren Togami (warren)
* Jeremy Katz (jeremy)
* Christopher Aillon (caillon)
= Members Absent =
* David Woodhouse (dwmw2)
* Christian Iseli (c4chris)
* Josh Boyer (jwb)
* Kevin Fenzi (nirik)
= Summary =
== Branch Policy for Packages on Soon-to-be-EOL Releases ==
* FESCo members were pretty sure this had already decided. bpepple
will search the wiki to verify this.
== NetworkManager ==
* FESCo received an update on the status of NM for F8 from Dan
Williams:
* Reached feature parity with 0.6.x from F7.
* Multiple device support won't be finished in time for F8
gold, but can come in as an F8 update.
Misc
* Brief discussion on when the feature process for F9 will start,
and what changes to the process needs to be made.
* Rahul Sundaram (mether) asked if the FESCo mailing list archive
could be opened. bpepple will check with the other FESCo members
to see if anyone objecFESCo Meeting Summary for 2007-10-18ts to
that.
IRC log can be found at:
http://bpepple.fedorapeople.org/fesco/FESCo-2007-10-25.html
Thanks,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
16 years, 7 months
Announcing Opyum 0.0.3 for Fedora
by Debarshi Ray
I hereby announce the second stable release of Opyum, the Fedora
Offline Package Manager, version 0.0.3.
Opyum (pronounced 'opium') provides a set of tools to enable users,
who do not have a good network (eg., Internet) connection at their
ready disposal, to easily install new packages or update existing ones
through the conventional package management system available in
Fedora.
Tar ball: http://rishi.fedorapeople.org/opyum/opyum-0.0.3.tar.gz
MD5SUM: 693bc38845aaef5ecf599d7564483f09
SHA1SUM: c21186d6b1f31ff8e7a4b9b9fa57dba74f12adae
New features:
Installing or updating from Yum-Packs is easier now with the
introduction of system-install-yumpacks. Apart from that, there is a
new repository manager to let users to add, remove, edit, enable and
disable repositories.
Installation instructions:
# yum install opyum
Documentation page:
https://fedoraproject.org/wiki/DebarshiRay/Opyum
Project page:
https://hosted.fedoraproject.org/projects/opyum/
Bug reports:
https://bugzilla.redhat.com/
Happy hacking,
Debarshi
--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
16 years, 7 months
Upgrade a USB thumb drive image
by semi linux
I've CC'ed the devel list as they might have already written a script
to do this...
I'm trying to create a USB install image like diskboot.img from and
for FC4. The thing is, I have to replace the default kernel with a
new tree to accommodate a new RAID card and Ethernet card which isn't
supported by the standard default kernel. I've got my upgrade drivers
in - no problems there; the kernel boots and finds the newer cards w/o
problem. The problem seems to be with updating the diskboot.img...
I'm using a FC4-updated kernel image (2.6.12-1.1447_FC4smp).
I've created the script below to help, but I can't figure-out why the
new kernel or the installer can't find my Ethernet card... Any tips
or suggestions on how to debug this would be great.
BTW> I'm planning to write this into a how-to once I finish for
everyone to follow as it's quite an involved process.
cp /media/cdrecorder/images/diskboot.img ~/
mkdir ~/bootwork
cd ~/bootwork
mkdir -p initrd-old initrd-new/modules diskboot-old floppy 2.6.12-1.1447_FC4smp
dd if=/dev/zero of=initrd bs=512 count=128000
/sbin/mke2fs -F -m0 initrd
dd if=/dev/zero of=floppy.img bs=512 count=128000
/sbin/mkfs.vfat floppy.img
syslinux floppy.img
mount -o loop ~/diskboot.img diskboot-old
mount -o loop floppy.img floppy
cp diskboot-old/*.msg diskboot-old/syslinux.cfg diskboot-old/splash.lss floppy/
cp /boot/vmlinuz-2.6.12-1.1447_FC4smp floppy/vmlinuz
gunzip -dc diskboot-old/initrd.img > initrd.old
cd initrd-old
cpio -i -d -m < ../initrd.old
cd -
find /lib/modules/2.6.12-1.1447_FC4smp/ -name *.ko | xargs -n 1 -I {}
cp {} 2.6.12-1.1447_FC4smp
cp -a initrd-old/bin initrd-new
cp -a initrd-old/dev initrd-new
cp -a initrd-old/etc initrd-new
cp -a initrd-old/proc initrd-new
cp -a initrd-old/sbin initrd-new
cp -a initrd-old/selinux initrd-new
cp -a initrd-old/sys initrd-new
cp -a initrd-old/tmp initrd-new
cp -a initrd-old/var initrd-new
cp -a initrd-old/modules/module-info initrd-new/modules
cp -a /lib/modules/2.6.12-1.1447_FC4smp/modules.dep initrd-new/modules
cp -a /lib/modules/2.6.12-1.1447_FC4smp/modules.pcimap initrd-new/modules
TMPFILE="pcitable.$$"
OUTFILE="pcitable"
INFILE="/lib/modules/2.6.12-1.1447_FC4smp/modules.pcimap"
# Loop through the PCI map
cat "$INFILE" | while read line; do
MODULE=`echo "$line" | awk '{ print $1 }'`
# Skip the comments
if [ "$MODULE" != "#" ]; then
VENDOR="0x"`echo "$line" | awk '{ print $2 }' | cut -c 7-`
DEVICE="0x"`echo "$line" | awk '{ print $3 }' | cut -c 7-`
SUBVENDOR="0x"`echo "$line" | awk '{ print $4 }' | cut -c 7-`
SUBDEVICE="0x"`echo "$line" | awk '{ print $5 }' | cut -c 7-`
DESCRIPTION=`modinfo "$MODULE" | grep "^description:" | cut -c 17-`
if [ "$VENDOR" != "0xffff" ] && [ "$DEVICE" != "0xffff" ]; then
if [ "$SUBVENDOR" == "0xffff" ] && [ "$SUBDEVICE" == "0xffff" ]; then
# Print two IDs
echo -ne "$VENDOR\t$DEVICE\t\"$MODULE\"" >> "$TMPFILE"
if [ "$DESCRIPTION" != "" ]; then echo -e "\t\"$DESCRIPTION\""
>> "$TMPFILE"
else echo >> "$TMPFILE"
fi
elif [ "$SUBDEVICE" == "0xffff" ]; then
# Print three IDs
echo -ne "$VENDOR\t$DEVICE\t$SUBVENDOR\t\"$MODULE\"" >> "$TMPFILE"
if [ "$DESCRIPTION" != "" ]; then echo -e "\t\"$DESCRIPTION\""
>> "$TMPFILE"
else echo >> "$TMPFILE"
fi
else
# Print all four IDs
echo -ne
"$VENDOR\t$DEVICE\t$SUBVENDOR\t$SUBDEVICE\t\"$MODULE\"" >> "$TMPFILE"
if [ "$DESCRIPTION" != "" ]; then echo -e "\t\"$DESCRIPTION\""
>> "$TMPFILE"
else echo >> "$TMPFILE"
fi
fi
fi
fi
done
sort "$TMPFILE" -o "$TMPFILE".sorted
uniq "$TMPFILE".sorted "$OUTFILE"
rm -f "$TMPFILE" "$TMPFILE".sorted
cp -a pcitable initrd-new/modules
find 2.6.12-1.1447_FC4smp | cpio -o -H crc | gzip -c9 > modules.cgz
cp -a modules.cgz initrd-new/modules
cd initrd-old
find . | cpio -o -H newc -O ../initrd
cd -
gzip -c9 initrd > initrd.img
cp initrd.img floppy
sync
umount floppy
umount diskboot-old
dd if=floppy.img of=/dev/sdb
cd
Thanks,
- G.
16 years, 7 months