Re: F9 - DPMS not working
On Thu, 2008-05-29 at 22:56 +0100, John Horne wrote: On Thu, 2008-05-29 at 18:30 +, Matthew Saltzman wrote: On Thu, 2008-05-29 at 18:29 +0100, John Horne wrote: Hello, Using F9, with KDE 4.0.4 desktop, my LCD display never seems to enter power-saving mode. I have a screensaver configured to kick in after 5 mins, and that works fine. The Xorg log file shows that DPMS is enabled, as does 'xset -q'. Running 'xset dpms force off' (or standy/suspend) and the screen turns off, so it can do it. I have left the system for nearly an hour, but the monitor is still on. This occurred under the vesa driver, but I have today installed the latest Nvidia drivers and the problem still exists. F8, using the same hardware, had no such problem. Any ideas, suggestions? Generate some traffic here: https://bugzilla.redhat.com/show_bug.cgi?id=351661 and let's see if we can't get some action on the vesa driver. If you can, update the version to 9, otherwise, include the fact that it is F9 in your comment. Not sure that will help. Now that I have installed the nvidia stuff, if I run vesa again it reports as coming from nvidia, not from the Fedora supplied one. I suspect the Fedora people will not accept that. Nope. But you can remove the nvidia stuff (I think by running nvidia-installer, if you didn't install the Livna packages) and set up the vesa driver again. John. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: f9: x86_64: Missing C++ runtime support for g++ (/usr/bin/g++).
Il giorno gio, 29/05/2008 alle 18.49 -0400, Jakub Jelinek ha scritto:
The above is not valid C++98, you need to use
#include iostream
using namespace std;
int main() { cout Hello World! endl; return 0; }
g++34 provides backwards support for deprecated pre-ISO C++ headers,
g++ doesn't any longer.
See http://gcc.gnu.org/gcc-4.3/porting_to.html
Removal of Pre-ISO headers for more info.
Ok, thank Jakub, but now, how I can rebuild hylafax?
I must patch hylafax (but i'm not a 'C++' guru) or there are other
solution?
Thanks.
--
Dario Lesca [EMAIL PROTECTED]
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: More Qlogic driver madness.
Mark Haney wrote: This is really getting silly. How is it possible that an initrd will not USE the firmware included with it to allow me to initialize my Qlogic FC card? I've built my own, I've read everything I can about initrd and initramfs and I'm still stuck. Are there tools included with Fedora that let me edit/muck initramfs settings? Or do I have to roll my own? I just don't get it, between FC6 2.6.20 and 2.6.22 kernels in FC6 this capability was broken and no one's complained? I'm really very tempted to file a bug report on this for F8 and hope it gets fixed that way, since I'm unable to find an answer. Mark, Try something like, 1. Add your qlogic entries to your /etc/modprobe.conf (so that step 3 below will include and load the drivers) 2. Backup your current initrd image mv /boot/initrd-$(uname -r).img mv /boot/initrd-$(uname -r).img-OLD 3. Create a new initrd mkinitrd -v /boot/initrd-$(uname -r).img $(uname -r) If the card has a newer firmware version than the driver, it should not use the driver version - normally. Question: Why the need to build your own - they are included in Fedora, check with: ls -la /lib/modules/$(uname -r)/kernel/drivers/scsi/qla* Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 and Security
Andras Simon wrote: On 5/28/08, Alan Cox [EMAIL PROTECTED] wrote: You can use uuids, labels or device names. Nothing has changed there. The defaults the installer uses have changed, and it makes no sense for the installer to ask new users questions like Use UUID, LABEL or device name ? How about old users? Perhaps in this new-user-friendly form: Use UUID (recommended), LABEL or device name ? Disclaimer: I've never heard of uuids before. But perhaps it'd make sense for those of us who are using older releases of Fedora, have several partitions, and would like to install F9 in a separate partition so we can go back to F8 or F7 in case something goes wrong, to chose LABEL. Unless the new install has the same LABEL as one of the old ones. I know three people who have been bitten by using LABEL and getting duplicates, the beauty of UUID is that you won't get a dup with multiple installs, you won't copy a filesystems only or off of a USB drive and plug the drive with the old duplicate name back in a year later. UUID is ugly, but useful. Because the answer in 99.99% cases is uh ?? Or: OK, let me chose the default. And the reason it's default is that it's least likely to fail if the user starts replugging drives, moving them, etc. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 and Security
Amadeus W.M. wrote: On Thu, 29 May 2008 01:02:12 +0100, Alan Cox wrote: Because the answer in 99.99% cases is uh ?? Or: OK, let me chose the default. Why even ask the question - if you know what you are doing you can change it later on. What if you don't know what you're doing, but simply do not want the newly introduced feature X for whatever reason? We don't go around asking Preferred Emailer What inode size should we use on ext3 Adjust raid readahead so why ask about what to most users are internal details about how we make sure their data reappears next reboot ? Where do you draw the line? Is which ports do you want to open in the firewall less technical? Is creating custom partitions less technical? How about package selection? We do have a choice there (for now). Incidentally and for my own understanding: I am able to mount/umount /dev/sdaX and such, if I wanted to, so the system can and does know the partitions by labels. Why do I have to see the UUID garbage in /etc/fstab though? This is not a rant, it's an actual question. The system does not know partitions by label. Partitions don't have labels (unless they're elements of an md array and have something in the superblock). Partitions have device names, but they can change, drives are named by the order of detection. So you can't always count on the device name. Filesystems have labels, and unlike partition device names or UUIDs, they need not be unique, so two installs on different drives or partitions can leave you with two filesystems names /. Only the UUID is (a) not going to change and (b) not going to be duplicated by anything like normal system operation. It is therefore the least likely to lead to an unwanted learning experience. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 nfs and autofs instable?
David Jansen wrote: Since switching to fedora 9 (fresh install, no upgrade), both nfs and autofs seem to crash on an almost daily basis. nfs mountd is just gone, no errors in the logs. autofs is even more enigmatic: the daemon is still running, but nothing gets mounted untill I restart the service. And here also, nothing is mentioned in the logs. So, when I noticed this, I have switched SELinux off, but the results are still the same, this morning both services were again not working. The thing I suspect is my rsync backup script, which runs at night and makes heavy use of nfs mounted directories. has anyone else seen such crashes, and does anyone know a solution or a way to learn more about the problem? I hasve not seen any indications of problems in that area, but I do backups over ssh. I do have a lot of heavily used filesystems mounted and used, and a fair bunch of ISO images exported, and I haven't had an issue of any kind. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: f9: x86_64: Missing C++ runtime support for g++ (/usr/bin/g++).
Il giorno gio, 29/05/2008 alle 18.49 -0400, Jakub Jelinek ha scritto:
The above is not valid C++98, you need to use
#include iostream
using namespace std;
int main() { cout Hello World! endl; return 0; }
g++34 provides backwards support for deprecated pre-ISO C++ headers,
g++ doesn't any longer.
See http://gcc.gnu.org/gcc-4.3/porting_to.html
Removal of Pre-ISO headers for more info.
Ok.
I have produce the follow patch to original hylafax-4.4.4-1.src.rpm
( ftp://ftp.hylafax.org/binary/linux/redhat/SRPMS/hylafax-4.4.4-1rhel5.src.rpm )
and rebuild the package without error.
Thanks Jakub
[EMAIL PROTECTED] ~]$ diff -Naur rpmbuild-old/ rpmbuild
diff -Naur rpmbuild-old/SOURCES/c++.patch rpmbuild/SOURCES/c++.patch
--- rpmbuild-old/SOURCES/c++.patch 1970-01-01 01:00:00.0 +0100
+++ rpmbuild/SOURCES/c++.patch 2008-05-30 01:15:56.0 +0200
@@ -0,0 +1,13 @@
+diff -Naur old/hylafax-4.4.4/configure hylafax-4.4.4/configure
+--- old/hylafax-4.4.4/configure2007-11-21 15:45:23.0 +0100
hylafax-4.4.4/configure2008-05-30 01:15:53.0 +0200
+@@ -1418,7 +1418,8 @@
+ CheckForCXXRuntime()
+ {
+ catt.c++EOF
+-#include iostream.h
++#include iostream
++using namespace std;
+ int main(){ cout Hello World! endl; return 0;}
+ EOF
+ runMake t t:; \${C++F} \${C++FILE} t.c++${MAKECXXOVERRIDE}
diff -Naur rpmbuild-old/SPECS/hylafax.spec rpmbuild/SPECS/hylafax.spec
--- rpmbuild-old/SPECS/hylafax.spec 2007-10-19 15:23:37.0 +0200
+++ rpmbuild/SPECS/hylafax.spec 2008-05-30 01:21:27.0 +0200
@@ -44,7 +44,7 @@
%define ostag sles%{sles_version}
%endif
-%define release 1%{ostag}
+%define release 2%{ostag}
%define serial %(echo `date +%Y%m%d`)
%define faxspool%{_var}/spool/hylafax
@@ -73,6 +73,7 @@
Source11: hylafax_FaxDispatch
Source12: hylafax_jobcontrol.sh
Source13: hylafax_sysconfig
+Patch14: c++.patch
BuildPrereq: libjpeg-devel, libtiff-devel, zlib-devel
Requires:ghostscript = 5.5
@@ -97,6 +98,7 @@
%prep
%setup -q
+%patch14 -p1
%build
# - Can't use the configure macro because HylaFAX configure script does
[EMAIL PROTECTED] ~]$
Hope this help someone.
Bye
--
Dario Lesca [EMAIL PROTECTED]
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: livna nvidia at last!
Now if only the nv driver would work on my system long enough to just do the install I would be really happy. https://bugzilla.redhat.com/show_bug.cgi?id=439609 Unfortunately the text based installer doesn't allow you to pick and choose your packages or I would use it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: livna nvidia at last!
On Thu, 29 May 2008 18:44:17 -0500 Erich Zigler [EMAIL PROTECTED] wrote: Unfortunately the text based installer doesn't allow you to pick and choose your packages or I would use it. You can use yum search to get a list of matching packages, then yum install to install exactly the one you want once you know the full names. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: updating USB flash drive MBR to allow boot
On Thu, 29 May 2008 17:45:38 -0400 Bill Davidsen [EMAIL PROTECTED] wrote: In theory you used fdisk -l to see if the partition was bootable or not, how about the practice? Thank you for that. These days mailing lists are becoming progressively more drab to read without these touches of wit. -- das ddts.randomink.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: gecko-mediaplayer?
On Thu, 2008-05-29 at 18:05 -0700, Knute Johnson wrote: I installed F9 and was trying to listen to my favorite radio station but I couldn't find mplayerplug-in. Some of you said to get gecko-mediaplayer instead. I downloaded it with no problems and it shows up in the plugins list but it doesn't work. There is also a Mozplugger at the top that appears not to be configured properly. MozPlugger 1.10.1 handles QuickTime and Windows Media Player Plugin File name: nswrapper_32_32.mozplugger.so MozPlugger version 1.10.1, written by Fredrik Hübinette, Louis Bavoil and Peter Leese. For documentation on how to configure mozplugger, check the man page. (type man mozplugger) Configuration file: Not found! Helper binary: Not found! Controller binary: Not found! It lists al the mime types below this and they are all enabled. Any ideas where to start trying to figure out why it doesn't work? Try removing mozplugger. I don't have it and am not sure it's necessary (plus it's apparently not configured correctly). Since it's at the top of the plugin list it might be interfering with gecko-mediaplayer. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
EDAC i5000 NON-FATAL ERRORs
I noticed that after upgrading the kernel on a Fedora 7 x86_64 box is the latest kernel (the box hadn't been rebooted for some months) that I am now seeing the following in my messages log... May 25 04:30:56 fourier kernel: EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x1 May 25 04:30:56 fourier kernel: EDAC MC0: CE row 1, channel 0, label : (Branch=0 DRAM-Bank=3 RDWR=Read RAS=14339 CAS=672, CE Err=0x1) These messages always occur on DRAM-Bank 3 and are always NON-FATAL. The messages appear roughly once an hour and are rarely repeated immediately. This machine contains a Tyan Tempest i5000XL motherboard with ECC memory installed. Does anyone know if the recent kernels had any changes which made these motherboard chipset report ECC memory errors which were not reported in the past? I haven't been able to reproduce these errors in memtest86 yet with or without ECC. So I am wondering if I am seeing noise from the EDAC driver or real ECC errors. Thanks in advance for any insights on this. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: updating USB flash drive MBR to allow boot
On Thu, May 29, 2008 at 4:45 PM, Bill Davidsen [EMAIL PROTECTED] wrote: Javier Perez wrote: On Thu, May 29, 2008 at 2:58 PM, das [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: On Thu, 29 May 2008 14:13:25 -0500 Javier Perez [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I cannot make a bootable USB drive. Did you try fdisk to make the partition bootable before using livecd-iso-to-disk? no In theory the livecd_to_usb program was supposed to make it bootable as part of the process. At least that is my understanding. In theory you used fdisk -l to see if the partition was bootable or not, how about the practice? -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Ok I just arrived back home. In practice it was marked as bootable. I downloaded the testdisk program and noticed a couple of interesting things. As I said, my flash drive is a Kingston Data Traveler 8GB Look at this extract of the created log TestDisk 6.9, Data Recovery Utility, February 2008 Christophe GRENIER [EMAIL PROTECTED] http://www.cgsecurity.org Linux version (ext2fs lib: 1.40.8, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 2) Hard disk list Disk /dev/sda - 163 GB / 152 GiB - CHS 19929 255 63, sector size=512 - ATA Maxtor 6L160P0 Disk /dev/sdb - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - ATA WDC WD2500BB-55R Disk /dev/sdc - 8011 MB / 7640 MiB - CHS 1021 247 62, sector size=512 - Kingston DataTraveler 2.0 Disk /dev/sdc - 8011 MB / 7640 MiB - Kingston DataTraveler 2.0 Partition table type: Intel Analyse Disk /dev/sdc - 8011 MB / 7640 MiB - CHS 1021 247 62 Geometry from i386 MBR: head=16 sector=32 BAD_RS LBA=32 62 FAT32 at 0/0/33 Info: size boot_sector 15646688, partition 15646688 FAT1 : 2256-17511 FAT2 : 17512-32767 start_rootdir : 32768 root cluster : 2 Data : 32768-15646687 sectors : 15646688 cluster_size : 8 no_of_cluster : 1951740 (2 - 1951741) fat_length 15256 calculated 15248 heads/cylinder 16 (FAT) != 247 (HD) sect/track 32 (FAT) != 62 (HD) *Current partition structure: Warning: Incorrect number of heads/cylinder 16 (FAT) != 247 (HD) Warning: Incorrect number of sectors per track 32 (FAT) != 62 (HD) 1 * FAT32 LBA0 0 33 1021 179 28 15646688 [LITTLE OWL] * I wonder if that might have something to do with it? maybe if I reformat and repartition the drive This inconsistency might be what makes the drive non bootable, because maybe the BIOS is expecting something (cylinders, heads) and the drive is givng it something that it cannot make sense of. JP -- -- /\_/\ |O O| [EMAIL PROTECTED] Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4.0/Nvidia not running/Dual monitors ?
On Wed, 2008-05-28 at 00:22 -0400, Todd Zullinger wrote: linuxguy wrote: Why is the nvidia module throwing an error during boot ? How do I fix it ? https://fedoraproject.org/wiki/Bugs/Common#Proprietary_.28third-party.29_video_drivers_do_not_work All I get is a blank page. :) Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. Linux user# 44256 Sign up at: http://counter.li.org/ http://www.sourceforge.net/projects/oar http://www.wayward4now.net ---down4now too -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4.0/Nvidia not running/Dual monitors ?
Ric Moore wrote: On Wed, 2008-05-28 at 00:22 -0400, Todd Zullinger wrote: linuxguy wrote: Why is the nvidia module throwing an error during boot ? How do I fix it ? https://fedoraproject.org/wiki/Bugs/Common#Proprietary_.28third-party.29_video_drivers_do_not_work All I get is a blank page. :) Ric Fixed. Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: livna nvidia at last!
On Thu, 2008-05-29 at 18:44 -0500, Erich Zigler wrote: Now if only the nv driver would work on my system long enough to just do the install I would be really happy. https://bugzilla.redhat.com/show_bug.cgi?id=439609 Unfortunately the text based installer doesn't allow you to pick and choose your packages or I would use it. You should be able to use the vesa driver. I think you enter linux vesa on the prompt line when you boot the installer. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4.0/Nvidia not running/Dual monitors ?
Todd Zullinger: https://fedoraproject.org/wiki/Bugs/Common#Proprietary_.28third-party.29_video_drivers_do_not_work Ric Moore: All I get is a blank page. :) Ric Rahul Sundaram: Fixed. The page, itself, uses this URI: https://fedoraproject.org/wiki/Bugs/Common#Proprietary_.28third-party.29_video_drivers The URI mentioned above doesn't point to any anchor on the page. -- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: PGP signatures.
On Thu, 2008-05-29 at 15:23 -0500, Aaron Konstam wrote: Let me share that to me the whole discussion of PGP signatures was very unenlightening. I have no idea how to sign e-mail or validate a pgp signed e-mail All the discussion seemed to me to be aimed at people who knew all about this. Before you can make use of pgp in mail, you have to get pgp working. After you've made your own keys, the next thing you'll need is the other party's keys. You've got to be able to manage getting them in some way. *Then* you can move on to actually using them. Though there's probably a understanding how the scheme works process that you need to go through, first, judging by your comments. Start with the documentation, that's where most of the rest of us started, and you're less likely to get given a bum steer by it. -- (This box runs Centos 5.0, my others still run FC 4, 5, 6, 7, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problem with totem
On Thu, 2008-05-29 at 17:44 -0430, Patrick O'Callaghan wrote: The Fedora version works for me (including with commercial DVDs). I never got very far with it. But commercial DVDs isn't a very precise definition. For instance, some commercial discs are encrypted, while others are not. -- (This box runs Centos 5.0, my others still run FC 4, 5, 6, 7, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: USB Install Method?
On Thu, 2008-05-29 at 17:39 -0430, Patrick O'Callaghan wrote: On Thu, 2008-05-29 at 12:58 -0700, Sean Bruno wrote: According the docs, there is a procedure for installing from a USB stick, but Procedure 3.2 Creating Bootable USB Media from Linux appears to be blank? http://docs.fedoraproject.org/install-guide/f9/en_US/sn-making-media.html#id543953 The headings are screwed up. The Windows instructions are in the first section, followed by the Linux instructions under the heading Procedure 3.1: Creating Bootable USB Media with Windows. The section entitled Procedure 3.2. Creating Bootable USB Media with Linux is blank. poc Ok, so using the information from Patrick I was able to use livecd-iso-to-disk to turn the boot.iso file into a bootable USB stick. However, livecd-iso-to-disk requires a vfat or ext2-3 f/s. Do I had to run mkfs on the thumb drive first. Sean -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: livna nvidia at last!
On Thu, May 29, 2008 at 9:58 PM, Matthew Saltzman [EMAIL PROTECTED] wrote: You should be able to use the vesa driver. I think you enter linux vesa on the prompt line when you boot the installer. The vesa driver works correctly. Thank you! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: livna nvidia at last!
On Thu, May 29, 2008 at 9:58 PM, Matthew Saltzman [EMAIL PROTECTED] wrote: You should be able to use the vesa driver. I think you enter linux vesa on the prompt line when you boot the installer. The vesa driver works correctly. Thank you! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: gecko-mediaplayer?
Patrick O'Callaghan wrote: On Thu, 2008-05-29 at 18:05 -0700, Knute Johnson wrote: I installed F9 and was trying to listen to my favorite radio station but I couldn't find mplayerplug-in. Some of you said to get gecko-mediaplayer instead. I downloaded it with no problems and it shows up in the plugins list but it doesn't work. There is also a Mozplugger at the top that appears not to be configured properly. MozPlugger 1.10.1 handles QuickTime and Windows Media Player Plugin File name: nswrapper_32_32.mozplugger.so MozPlugger version 1.10.1, written by Fredrik Hübinette, Louis Bavoil and Peter Leese. For documentation on how to configure mozplugger, check the man page. (type man mozplugger) Configuration file: Not found! Helper binary: Not found! Controller binary: Not found! It lists al the mime types below this and they are all enabled. Any ideas where to start trying to figure out why it doesn't work? Try removing mozplugger. I don't have it and am not sure it's necessary (plus it's apparently not configured correctly). Since it's at the top of the plugin list it might be interfering with gecko-mediaplayer. poc Thanks, I'll try that. -- Knute Johnson [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: [Dovecot] Problem deleting folders with Thunderbird?
Michal Soltys wrote: Scott Silva wrote: You need to clear that checkbox with mbox storage for sure. It might be OK if you are using Maildir. It works perfectly fine with Maildir. So folders in folders works with Maildir? Thanks, -- Knute Johnson [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
thunderbird-2.0.0.14-1.fc8.i386.rpm: installing under f8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
greetings,
thanks to all who provided links and mirrors for thunderbird.
pulled 'thunderbird-2.0.0.14-1.fc8.i386.rpm' from several sites.
found it interesting how size varied between.
used 'yum', similar error on all 3.
+
Yum Version: 3.2.7
COMMAND: yum -v -y install thunderbird-2.0.0.14-1.fc8.i386.rpm 2
Installroot: /
Ext Commands:
thunderbird-2.0.0.14-1.fc8.i386.rpm
2
Reading Local RPMDB
Setting up Package Sacks
Setting up Install Process
Parsing package install arguments
Examining thunderbird-2.0.0.14-1.fc8.i386.rpm: thunderbird - \
2.0.0.14-1.fc8.i386
Marking thunderbird-2.0.0.14-1.fc8.i386.rpm to be installed
Building updates object
putting glibc in complex update
putting openssl in complex update
putting kernel in complex update
processing glibc.i686
processing openssl
processing kernel.i686
Checking for virtual provide or file-provide for 2
Searching pkgSack for dep: 2
No package 2 available.
Resolving Dependencies
1211917649.78
- -- Running transaction check
snip
looking for ('libz.so.1', None, (None, None, None)) as a requirement of \
thunderbird.i386 0-2.0.0.14-1.fc8 - u
- -- Finished Dependency Resolution
Dependency Process ending
Dependencies Resolved
1211917652.31
Package Arch Version Repository Size
Installing:
thunderbird i386 2.0.0.14-1.fc8 thunderbird-2.0.0.14-1.fc8.i386.rpm 45 M
Transaction Summary
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 45 M
Downloading Packages:
Package thunderbird-2.0.0.14-1.fc8.i386.rpm is not signed
+
{{ pcoaa. thank you. }}
questions:
1) do lines 2 and 6 have a '2' floating or is this an indicator?
2) lines 20 - 22 indicates need of 'package 2' for deps.
how is 'package 2' id'ed?
link to find? { searching fedora and 2 mirrors showed no mention }
tia.
i do appreciate all of help that has feed back on and off list.
thanks again.
look out f9...
- --
tc,hago.
g
.
in a free world without fences, who needs gates...
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iD8DBQFIP44wfZb4FyaU51QRAjvPAKC0NMIWjwwDlQCETQW8TNTBiTguRwCgu9ku
R24U75gXnQ03nR/xVZH2o8o=
=+66d
-END PGP SIGNATURE-
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F8 - F9 horror
scm in seattle scmsea at yahoo.com writes: yum repolist shows: Fedora - Rawhide... Then that must be it. Note that Rawhide is actually F10 pre-alpha, not F9, so no wonder it's buggy (but it has KDE 4.1 beta 1, so your complaints about 4.0 are missing the point). Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9/KDE 4 'non kde app'
John Minson minsonj at spawar.navy.mil writes: On all earlier versions of Fedora/kde I was able to add a 'non kde app' and give it any icon I wanted . I suspect I still can but the mechanism obviously is different on Fedora 9/KDE 4 . Any quick pointers ? Surely the right solution is that the app itself should be registering in the menus on its own! If the app is a Fedora package, file a bug against the package for the missing .desktop file, which is required according to: https://fedoraproject.org/wiki/Packaging/Guidelines#Desktop_files If it is a third-party application, complain to wherever you got the application from. If it is your own application, have a look at xdg-desktop-menu, or package it as an RPM and have a look at the packaging guidelines as quoted above. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: [Fedora-livecd-list] [PATCH] -fs.py-kickstart.py-chages-for-mulit-partitions
On Wed, 2008-05-28 at 14:36 -0400, Jeremy Katz wrote: The ability for a tool to create these partitioned disk images via the command like, livecd-creator, is very helpful in reproducing known state appliances, epically with the rising use of visualization. Going through a actual install in a vm limits you to VM container, xen, kvm, vmware and adds extra overhead of building on a machine with extra virt resources. Reproducing known state should work just as well with a kickstart config and doing an install via, eg, virt-install. Yes, it adds overhead, but there are also advantages in functionality and it also means *not* maintaining this sort of code in multiple places. And that's a pretty big win as partitioning code is not in the least bit trivial. Especially as you start trying to handle more and more of the cases. That pretty lame - you're trying to curtail what use cases people make imgcreate support purely because we haven't figured out how to do a better job of sharing code with anaconda. The very least we should be doing is allowing imgcreate to be extended externally in this manner ... but that doesn't fix the multiple copies of this code issue, it merely pushes it elsewhere and makes it less likely it'll ever be fixed. Clearly, one advantage of imgcreate tools over a full blown anaconda install in a VM is that it's far less complex to debug when it all goes wrong. That's a huge advantage to people repeatedly rebuilding images as they develop a LiveCD or an appliance. Cheers, Mark. -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] [PATCH] -fs.py-kickstart.py-chages-for-mulit-partitions
Mark McLoughlin wrote: On Wed, 2008-05-28 at 14:36 -0400, Jeremy Katz wrote: The ability for a tool to create these partitioned disk images via the command like, livecd-creator, is very helpful in reproducing known state appliances, epically with the rising use of visualization. Going through a actual install in a vm limits you to VM container, xen, kvm, vmware and adds extra overhead of building on a machine with extra virt resources. Reproducing known state should work just as well with a kickstart config and doing an install via, eg, virt-install. Yes, it adds overhead, but there are also advantages in functionality and it also means *not* maintaining this sort of code in multiple places. And that's a pretty big win as partitioning code is not in the least bit trivial. Especially as you start trying to handle more and more of the cases. That pretty lame - you're trying to curtail what use cases people make imgcreate support purely because we haven't figured out how to do a better job of sharing code with anaconda. If there were multiple people really clamoring for support to do partitioned images, it would be one thing. But right now, it's one tool. And to then carry the onus outside of that tool for keeping the non-trivial bits working? The very least we should be doing is allowing imgcreate to be extended externally in this manner ... but that doesn't fix the multiple copies of this code issue, it merely pushes it elsewhere and makes it less likely it'll ever be fixed. But we are doing the work to allow an external appliance-creator to carry the functionality if desired. That's why the refactoring patch is reasonable (modulo fixing up the API break). Clearly, one advantage of imgcreate tools over a full blown anaconda install in a VM is that it's far less complex to debug when it all goes wrong. That's a huge advantage to people repeatedly rebuilding images as they develop a LiveCD or an appliance. The reason that it's less complex to debug is the fact that the code is more limited in what it supports than anaconda. Adding more (complicated) pieces is directly in contradiction to keeping things simple to debug Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] livecd-iso-to-disk broken in F9?
Todd N wrote: We are trying to use the livecd-iso-to-disk script in Fedora 9 to create a bootable USB drive. When running this script from a command prompt: # ./livecd-iso-to-disk all we get back is a line showing the command usage. However, the same command entered in Fedora 8, or even in Fedora 9 Beta, works fine. Has anyone else had this issue? Err... you need to give it more arguments than just that :) It's been working fine for me and I use it on a very regular basis Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
[Fedora-livecd-list] Re: [RFC] Livecd-creator and selinux, we can play nice
seth vidal wrote: On Wed, 2008-05-28 at 16:11 -0400, Eric Paris wrote: My concern is this is a normal occurence (needing a chroot) Yes and no sure looks like we'd need to make sure: yum, mock and rpm all know how to set this up given how it would impact chroot creation. If we do so, then we should also make sure that all do things consistently wrt /dev for creating a chroot as well. And /proc and /sys. The reality is that the different applications do have a somewhat different idea of what they need/want out of their chroots and do things (or don't) accordingly. We may want to drop this back to the lowest level chroot creation. Which isn't to say that we might not decide down the road to push it down the stack, but I don't know that livecd-creator is a bad place in the short to medium term as Eric continues looking at SELinux and chroot interactions (Right Eric? :-) Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
[Fedora-livecd-list] Re: [RFC] Livecd-creator and selinux, we can play nice
Eric Paris wrote:
So I've spent a fair bit of time the last 2 weeks trying to get
livecd-creator and an selinux enforcing machine to play nicely together.
It doesn't look like much, but from the point of view of the livecd
creator I think the following patch is all we need. Working with
rawhide as the host system I was able to build F8, F9 and rawhide
livecd's with an enforcing machine.
I wouldn't suggest jumping into enfocing builds just yet as there are
still some policy issues I need to work out with the selinux people but
I would like comments. Basically its quite simple, if selinux is on the
host we create a fake /selinux which tells the install chroot lies.
I've had to make some changes to some selinux libraries to support all
this, but I think we are just about there.
Very cool and definitely long needed. Thanks for taking the time to
really dive into this. And this is far simpler than the approach I had
started looking at once upon a time (... which involved fuse)
A few comments on the patch
diff -Naupr /usr/lib/python2.5/site-packages/imgcreate/creator.py
/root/imgcreate-5-28-08/creator.py
--- /usr/lib/python2.5/site-packages/imgcreate/creator.py 2008-05-06
12:16:08.0 -0400
+++ /root/imgcreate-5-28-08/creator.py 2008-05-28 15:48:30.0 -0400
@@ -460,6 +457,37 @@ class ImageCreator(object):
os.symlink('/proc/self/fd/2', self._instroot + /dev/stderr)
os.umask(origumask)
+# if selinux exists on the host we need to lie to the chroot
+if os.path.exists(/selinux/enforce):
+selinux_dir = self._instroot + /selinux
+
+# enforce=0 tells the chroot selinux is not enforcing
+# policyvers=99 tell the chroot to make the highest version of
policy it can
+files = [('/enforce', '0'),
+ ('/policyvers', '99')]
Does the kernel guarantee that 99 will be the highest version of policy?
Not that it likely matters much. Also, having this as a tuple rather
than a list makes it marginally faster since we're never going to modify it
+for (file, value) in files:
+fd = os.open(selinux_dir + file, os.O_WRONLY | os.O_TRUNC |
os.O_CREAT)
+os.write(fd, value)
+os.close(fd)
+
+# we steal mls from the host system for now, might be best to
always set it to 1
+files = [/selinux/mls]
+for file in files:
+shutil.copyfile(file, self._instroot + file)
+
+# make /load - /dev/null so chroot policy loads don't hurt
anything
+os.mknod(selinux_dir + /load, 0666 | stat.S_IFCHR, os.makedev(1,
3))
This being the big win :)
+# selinux is on whoo hooo
+if kickstart.selinux_enabled(self.ks):
+# label the fs like it is a root before the bind mounting
+cmd = /sbin/setfiles -F -r %s %s %s % (self._instroot,
selinux.selinux_file_context_path(), self._instroot)
+os.system(cmd)
+# these dumb things don't get magically fixed, so make the user
generic
+for f in [/proc, /sys, /selinux]:
+cmd = chcon -u system_u %s % (self._instroot + f)
+os.system(cmd)
os.system is generally not preferred -- using the subprocess module is a
lot safer.
Also, overall it might be nice to encapsulate the /selinux creation here
into its own __create_selinuxfs() method that gets called. /me makes a
note to do that to the /dev creation too.
@@ -853,6 +881,18 @@ class LoopImageCreator(ImageCreator):
(self._image, e))
def _unmount_instroot(self):
+# if the system was running selinux clean up our lies
+if os.path.exists(/selinux/enforce):
+files = ['/enforce',
+ '/policyvers',
+ '/mls',
+ '/load']
Again a tuple versus a list
+for file in files:
+try:
+os.unlink(self._instroot + /selinux + file)
+except OSError:
+pass
And again having it in a method is probably the nice thing to do. And I
know I said to stick it into _unmount_instroot, but seeing where you've
put the mount side, it probably makes more sense in unmount() instead
Jeremy
--
Fedora-livecd-list mailing list
Fedora-livecd-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
[Fedora-livecd-list] Re: [RFC] Livecd-creator and selinux, we can play nice
Daniel J Walsh ([EMAIL PROTECTED]) said: Well I think we need to do a couple of these to figure out the common requirements. I envision mock to be quite different then livecd. I think we need to full the mock chroot to think SELinux is disabled and to do no labeling in the chroot. This would allow us to confine the mock process to be able to write to the chroot and label the chroot mock_rw_t. We could then use SELinux to prevent mock environments from breaking out of the chroot, and stop mock environments from doing evil network things within the chroot. In livecd we need to be able to put down labels that the host machine does not understand. The problem is that mock can be used to do non-build things. (For example, creating the anaconda install images.) Bill -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] [PATCH] -fs.py-kickstart.py-chages-for-mulit-partitions
Jeremy Katz wrote: Mark McLoughlin wrote: On Wed, 2008-05-28 at 14:36 -0400, Jeremy Katz wrote: The ability for a tool to create these partitioned disk images via the command like, livecd-creator, is very helpful in reproducing known state appliances, epically with the rising use of visualization. Going through a actual install in a vm limits you to VM container, xen, kvm, vmware and adds extra overhead of building on a machine with extra virt resources. Reproducing known state should work just as well with a kickstart config and doing an install via, eg, virt-install. Yes, it adds overhead, but there are also advantages in functionality and it also means *not* maintaining this sort of code in multiple places. And that's a pretty big win as partitioning code is not in the least bit trivial. Especially as you start trying to handle more and more of the cases. That pretty lame - you're trying to curtail what use cases people make imgcreate support purely because we haven't figured out how to do a better job of sharing code with anaconda. If there were multiple people really clamoring for support to do partitioned images, it would be one thing. But right now, it's one tool. And to then carry the onus outside of that tool for keeping the non-trivial bits working? The very least we should be doing is allowing imgcreate to be extended externally in this manner ... but that doesn't fix the multiple copies of this code issue, it merely pushes it elsewhere and makes it less likely it'll ever be fixed. But we are doing the work to allow an external appliance-creator to carry the functionality if desired. That's why the refactoring patch is reasonable (modulo fixing up the API break). Clearly, one advantage of imgcreate tools over a full blown anaconda install in a VM is that it's far less complex to debug when it all goes wrong. That's a huge advantage to people repeatedly rebuilding images as they develop a LiveCD or an appliance. The reason that it's less complex to debug is the fact that the code is more limited in what it supports than anaconda. Adding more (complicated) pieces is directly in contradiction to keeping things simple to debug So.. to summarize.. as long as the partitioning code is in the appliance creator only.. we are fine. Is that correct? -- bk -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] [PATCH] -fs.py-kickstart.py-chages-for-mulit-partitions
I've been flat on my back for a while, so if I repeat anything previously sad, apologies. I've got a kickstart that is used to create a two partition solution on a 1G flash device. On the code side, I use a number of shell scripts. But, the main thing that makes is work is that I use a directory structure that looks like this project - files/ - partition_2/ - kickstart file files holds various odds ends (some custom rpms, some specific files, etc). partition_2 holds all the stuff I want on the second partion. I then have a simple script that backbones the livecd creation process and a second script that bundles up everything in the partition 2 directory as another iso. When I'm ready to burn the stuff to flash, I run a second script that handles the partitioning, writes the livecd to the first partition and the partition_2 iso's contents to the second partition. Mark, if this sounds helpful, I'd be happy to tar/zip the scripts in question with some basic directions. If the person who created the livecd creation tool (sorry ... I've forgotten your name and I seem to have accidently deleted the email) is interested, I could turn it into an rpm that could become part of that kickstart. Tim Mark McLoughlin wrote: On Wed, 2008-05-28 at 14:36 -0400, Jeremy Katz wrote: The ability for a tool to create these partitioned disk images via the command like, livecd-creator, is very helpful in reproducing known state appliances, epically with the rising use of visualization. Going through a actual install in a vm limits you to VM container, xen, kvm, vmware and adds extra overhead of building on a machine with extra virt resources. Reproducing known state should work just as well with a kickstart config and doing an install via, eg, virt-install. Yes, it adds overhead, but there are also advantages in functionality and it also means *not* maintaining this sort of code in multiple places. And that's a pretty big win as partitioning code is not in the least bit trivial. Especially as you start trying to handle more and more of the cases. That pretty lame - you're trying to curtail what use cases people make imgcreate support purely because we haven't figured out how to do a better job of sharing code with anaconda. The very least we should be doing is allowing imgcreate to be extended externally in this manner ... but that doesn't fix the multiple copies of this code issue, it merely pushes it elsewhere and makes it less likely it'll ever be fixed. Clearly, one advantage of imgcreate tools over a full blown anaconda install in a VM is that it's far less complex to debug when it all goes wrong. That's a huge advantage to people repeatedly rebuilding images as they develop a LiveCD or an appliance. Cheers, Mark. -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- _ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database more sincesince 1994 www.datawranglers.com -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] livecd-iso-to-disk broken in F9?
Correction: we also tried /dev/live as the input parameter (not /mnt/live). Also, this method worked in Fedora 9 Preview as well. Todd Todd N [EMAIL PROTECTED] wrote: Yes, we use the noverify and reset-mbr options along with /dev/sr0 as the input (and have also tried /mnt/live?) and /dev/sda1 as the output (no hard drive, so this corresponds to the USB). Worked fine previously, but now returns the usage() message. Jeremy Katz [EMAIL PROTECTED] wrote: Todd N wrote: We are trying to use the livecd-iso-to-disk script in Fedora 9 to create a bootable USB drive. When running this script from a command prompt: # ./livecd-iso-to-disk all we get back is a line showing the command usage. However, the same command entered in Fedora 8, or even in Fedora 9 Beta, works fine. Has anyone else had this issue? Err... you need to give it more arguments than just that :) It's been working fine for me and I use it on a very regular basis Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] livecd-iso-to-disk broken in F9?
These are our results. [/dev/sr0 on /mnt/live type iso9660 (ro)] [EMAIL PROTECTED] LiveOS]# sh -x ./livecd-iso-to-disk --reset-mbr --noverify /dev/sr0 /dev/sda1 + export PATH=/sbin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin + PATH=/sbin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin ++ id -u + '[' 0 '!=' 0 ']' + '[' 4 -gt 2 ']' + case $1 in + resetmbr=1 + shift + '[' 3 -gt 2 ']' + case $1 in + noverify=1 + shift + '[' 2 -gt 2 ']' ++ readlink -f /dev/sr0 + ISO=/dev/sr0 + USBDEV=/dev/sda1 + '[' -z /dev/sr0 -o '!' -f /dev/sr0 ']' + usage + echo './livecd-iso-to-disk [--reset-mbr] [--noverify] [--overlay-size-mb size] isopath usbstick device' ./livecd-iso-to-disk [--reset-mbr] [--noverify] [--overlay-size-mb size] isopath usbstick device + exit 1 Jeremy Katz [EMAIL PROTECTED] wrote: Try running it with sh -x... that should at least give you an idea of where it's going wrong Jeremy Todd N wrote: Correction: we also tried /dev/live as the input parameter (not /mnt/live). Also, this method worked in Fedora 9 Preview as well. Todd */Todd N /* wrote: Yes, we use the noverify and reset-mbr options along with /dev/sr0 as the input (and have also tried /mnt/live?) and /dev/sda1 as the output (no hard drive, so this corresponds to the USB). Worked fine previously, but now returns the usage() message. */Jeremy Katz /* wrote: Todd N wrote: We are trying to use the livecd-iso-to-disk script in Fedora 9 to create a bootable USB drive. When running this script from a command prompt: # ./livecd-iso-to-disk all we get back is a line showing the command usage. However, the same command entered in Fedora 8, or even in Fedora 9 Beta, works fine. Has anyone else had this issue? Err... you need to give it more arguments than just that :) It's been working fine for me and I use it on a very regular basis Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: [Fedora-livecd-list] livecd-iso-to-disk broken in F9?
Todd N wrote: These are our results. [/dev/sr0 on /mnt/live type iso9660 (ro)] [snip] + '[' -z /dev/sr0 -o '!' -f /dev/sr0 ']' Hmmm... I see what it is. We changed so that we ensure that you're not using like a directory, but that then doesn't work with using the mounted block device. The simple fix would be to change the -f there to a -e, but that's not the best fix. I'll try to kludge something in shell to work more completely Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
[Fedora-livecd-list] 2 commits - imgcreate/creator.py tools/livecd-iso-to-disk.sh
imgcreate/creator.py| 37 -
tools/livecd-iso-to-disk.sh |6 +-
2 files changed, 25 insertions(+), 18 deletions(-)
New commits:
commit fd5652933c0a49f8961d17bee5f0526bf1676a14
Author: Jeremy Katz [EMAIL PROTECTED]
Date: Thu May 29 17:04:41 2008 -0400
Allow isos to be blockdevs or regular files
diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
index 9676633..69e97e3 100644
--- a/tools/livecd-iso-to-disk.sh
+++ b/tools/livecd-iso-to-disk.sh
@@ -188,7 +188,11 @@ done
ISO=$(readlink -f $1)
USBDEV=$2
-if [ -z $ISO -o ! -f $ISO ]; then
+if [ -z $ISO ]; then
+usage
+fi
+
+if [ ! -b $ISO -a ! -f $ISO ]; then
usage
fi
commit 6e221ba27ed5a6c5a79ac1fbb7cfc5e11566e080
Author: Jeremy Katz [EMAIL PROTECTED]
Date: Thu May 29 08:53:25 2008 -0400
Move minimal /dev creation into a method
diff --git a/imgcreate/creator.py b/imgcreate/creator.py
index fc4298b..5d010a1 100644
--- a/imgcreate/creator.py
+++ b/imgcreate/creator.py
@@ -403,6 +403,24 @@ class ImageCreator(object):
fstab.write(self._get_fstab())
fstab.close()
+def __create_minimal_dev(self):
+Create a minimal /dev so that we don't corrupt the host /dev
+origumask = os.umask()
+devices = (('null', 1, 3, 0666),
+ ('urandom',1, 9, 0666),
+ ('random', 1, 8, 0666),
+ ('full', 1, 7, 0666),
+ ('ptmx', 5, 2, 0666),
+ ('tty',5, 0, 0666),
+ ('zero', 1, 5, 0666))
+for (node, major, minor, perm) in devices:
+os.mknod(self._instroot + /dev/ + node, perm | stat.S_IFCHR,
os.makedev(major,minor))
+os.symlink('/proc/self/fd', self._instroot + /dev/fd)
+os.symlink('/proc/self/fd/0', self._instroot + /dev/stdin)
+os.symlink('/proc/self/fd/1', self._instroot + /dev/stdout)
+os.symlink('/proc/self/fd/2', self._instroot + /dev/stderr)
+os.umask(origumask)
+
def mount(self, base_on = None, cachedir = None):
Setup the target filesystem in preparation for an install.
@@ -444,25 +462,10 @@ class ImageCreator(object):
if kickstart.selinux_enabled(self.ks):
self.__bindmounts.append(BindChrootMount(/selinux,
self._instroot, None))
-# Create minimum /dev
-origumask = os.umask()
-devices = [('null', 1, 3, 0666),
- ('urandom',1, 9, 0666),
- ('random', 1, 8, 0666),
- ('full', 1, 7, 0666),
- ('ptmx', 5, 2, 0666),
- ('tty',5, 0, 0666),
- ('zero', 1, 5, 0666)]
-for (node, major, minor, perm) in devices:
-os.mknod(self._instroot + /dev/ + node, perm | stat.S_IFCHR,
os.makedev(major,minor))
-os.symlink('/proc/self/fd', self._instroot + /dev/fd)
-os.symlink('/proc/self/fd/0', self._instroot + /dev/stdin)
-os.symlink('/proc/self/fd/1', self._instroot + /dev/stdout)
-os.symlink('/proc/self/fd/2', self._instroot + /dev/stderr)
-os.umask(origumask)
-
self._do_bindmounts()
+self.__create_minimal_dev()
+
os.symlink(../proc/mounts, self._instroot + /etc/mtab)
self.__write_fstab()
--
Fedora-livecd-list mailing list
Fedora-livecd-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: Introducing Fedora Nightlife
On Thu, May 29, 2008 at 7:55 AM, Rahul Sundaram [EMAIL PROTECTED] wrote: Hi, http://bryanche.blogspot.com/2008/05/introducing-fedora-nightlife.html Fedora Nightlife is a new project for creating a Fedora community grid. People will be able to donate idle capacity from their own computers to an open, general-purpose Fedora-run grid for processing socially beneficial work and scientific research that requires access to large amounts of computing power. http://digg.com/linux_unix/Introducing_Fedora_Nightlife Rahul irc channel #fedora-nightlife is open on irc.freenode.net for those interested. kind regards, Rudolf Kastl -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Fedora marketing meeting in about an hour
In freenode, #fedora-mktg. Agenda (on the new wiki, yay!) https://fedoraproject.org/wiki/Marketing/Tasks See you all at 3pm Eastern US time. --g -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Cluster Analysis Software
Hi, I've been asked whether or not if there's Cluster Analysis software that is open source? If so, please give me some recommendations. Thanks, Grady -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Re: Cluster Analysis Software
try here:- http://rana.lbl.gov/EisenSoftwareSource.htm released source code of ScanAlyze, Cluster and TreeView to the academic/non-profit community. Thanks you Have a Nice Day Best Regards, Jason Benedict Low *Allow us to treat you with the individuality you deserve! Grady Laksmono wrote: Hi, I've been asked whether or not if there's Cluster Analysis software that is open source? If so, please give me some recommendations. Thanks, Grady -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Re: Cluster Analysis Software
Thanks :) On Thu, May 29, 2008 at 5:20 PM, Jason Benedict Low [EMAIL PROTECTED] wrote: try here:- http://rana.lbl.gov/EisenSoftwareSource.htm released source code of ScanAlyze, Cluster and TreeView to the academic/non-profit community. Thanks you Have a Nice Day Best Regards, Jason Benedict Low *Allow us to treat you with the individuality you deserve! Grady Laksmono wrote: Hi, I've been asked whether or not if there's Cluster Analysis software that is open source? If so, please give me some recommendations. Thanks, Grady -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Fedora 9 Media Supplies
Hi all, Many of my class mates would like to get the Fedora 9 media, where can I request the supplies for this? I'm happy that many of us are moving to open source! :) Thanks, Grady -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Re: Introducing Fedora Nightlife
Excellent project and very illustrative description!!!, I posted a spanish translation in my blog http://alexacosta.wordpress.com (domain name to be changed soon ) Please spanish speaking fellows let me know if you find words or ideas that may be misspelled. Alejandro Acosta On Thu, 2008-05-29 at 11:25 +0530, Rahul Sundaram wrote: Hi, http://bryanche.blogspot.com/2008/05/introducing-fedora-nightlife.html Fedora Nightlife is a new project for creating a Fedora community grid. People will be able to donate idle capacity from their own computers to an open, general-purpose Fedora-run grid for processing socially beneficial work and scientific research that requires access to large amounts of computing power. http://digg.com/linux_unix/Introducing_Fedora_Nightlife Rahul -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Early Days with KDE 4: openSUSE 10.3, Kubuntu 8.04 and Fedora 9 compared
Hi More like short notes but someone from KDE SIG might want to take a look and respond http://softvision.wordpress.com/2008/05/18/early-days-with-kde-4-opensuse-103-kubuntu-804-and-fedora-9-compared/ Rahul -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Re: Early Days with KDE 4: openSUSE 10.3, Kubuntu 8.04 and Fedora 9 compared
may be should try Fedora kde edition -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Re: Fedora 9 Media Supplies
Hi all, Many of my class mates would like to get the Fedora 9 media, where can I request the supplies for this? I'm happy that many of us are moving to open source! :) Thanks, Grady Erm do you mean in with cd/dvd's? If so you will have to request it from the wiki. Do a search for freemedia. If you mean downloading the cd/dvd's from http://fedoraproject.org/en/get-fedora Cheers, Marc -- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
rpms/perl-aliased/devel .cvsignore, 1.3, 1.4 perl-aliased.spec, 1.4, 1.5 sources, 1.3, 1.4
Author: cweyl
Update of /cvs/extras/rpms/perl-aliased/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13709
Modified Files:
.cvsignore perl-aliased.spec sources
Log Message:
* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 0.22-1
- update to 0.22
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-aliased/devel/.cvsignore,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- .cvsignore 30 Mar 2007 15:58:44 - 1.3
+++ .cvsignore 29 May 2008 06:15:07 - 1.4
@@ -1 +1 @@
-aliased-0.21.tar.gz
+aliased-0.22.tar.gz
Index: perl-aliased.spec
===
RCS file: /cvs/extras/rpms/perl-aliased/devel/perl-aliased.spec,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- perl-aliased.spec 5 Mar 2008 14:55:50 - 1.4
+++ perl-aliased.spec 29 May 2008 06:15:07 - 1.5
@@ -1,6 +1,6 @@
Name: perl-aliased
-Version:0.21
-Release:2%{?dist}
+Version:0.22
+Release:1%{?dist}
Summary:Use shorter versions of class names
License:GPL+ or Artistic
Group: Development/Libraries
@@ -47,6 +47,9 @@
%{_mandir}/man3/*
%changelog
+* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 0.22-1
+- update to 0.22
+
* Wed Mar 5 2008 Tom spot Callaway [EMAIL PROTECTED] 0.21-2
- rebuild for new perl
Index: sources
===
RCS file: /cvs/extras/rpms/perl-aliased/devel/sources,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sources 30 Mar 2007 15:58:44 - 1.3
+++ sources 29 May 2008 06:15:07 - 1.4
@@ -1 +1 @@
-41e8947ff9b885cfcf210c6bcc715b4f aliased-0.21.tar.gz
+06cace025aa108fe4a9af3ae26bb297e aliased-0.22.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 448870] C::V::TT 0.27 is out!
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: C::V::TT 0.27 is out! https://bugzilla.redhat.com/show_bug.cgi?id=448870 [EMAIL PROTECTED] changed: What|Removed |Added BugsThisDependsOn||448871 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 448870] New: C::V::TT 0.27 is out!
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=448870 Summary: C::V::TT 0.27 is out! Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: perl-Catalyst-View-TT AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: fedora-perl-devel-list@redhat.com C::V::TT 0.27 is out; please update. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-aliased/F-9 perl-aliased.spec,1.4,1.5 sources,1.3,1.4
Author: cweyl
Update of /cvs/extras/rpms/perl-aliased/F-9
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13874
Modified Files:
perl-aliased.spec sources
Log Message:
* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 0.22-1
- update to 0.22
Index: perl-aliased.spec
===
RCS file: /cvs/extras/rpms/perl-aliased/F-9/perl-aliased.spec,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- perl-aliased.spec 5 Mar 2008 14:55:50 - 1.4
+++ perl-aliased.spec 29 May 2008 06:19:05 - 1.5
@@ -1,6 +1,6 @@
Name: perl-aliased
-Version:0.21
-Release:2%{?dist}
+Version:0.22
+Release:1%{?dist}
Summary:Use shorter versions of class names
License:GPL+ or Artistic
Group: Development/Libraries
@@ -47,6 +47,9 @@
%{_mandir}/man3/*
%changelog
+* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 0.22-1
+- update to 0.22
+
* Wed Mar 5 2008 Tom spot Callaway [EMAIL PROTECTED] 0.21-2
- rebuild for new perl
Index: sources
===
RCS file: /cvs/extras/rpms/perl-aliased/F-9/sources,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sources 30 Mar 2007 15:58:44 - 1.3
+++ sources 29 May 2008 06:19:05 - 1.4
@@ -1 +1 @@
-41e8947ff9b885cfcf210c6bcc715b4f aliased-0.21.tar.gz
+06cace025aa108fe4a9af3ae26bb297e aliased-0.22.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-WWW-Mechanize/devel .cvsignore, 1.10, 1.11 perl-WWW-Mechanize.spec, 1.15, 1.16 sources, 1.10, 1.11
Author: cweyl
Update of /cvs/extras/rpms/perl-WWW-Mechanize/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15823
Modified Files:
.cvsignore perl-WWW-Mechanize.spec sources
Log Message:
* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 1.34-1
- update to 1.34
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-WWW-Mechanize/devel/.cvsignore,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- .cvsignore 8 Dec 2007 07:42:02 - 1.10
+++ .cvsignore 29 May 2008 06:58:07 - 1.11
@@ -1 +1 @@
-WWW-Mechanize-1.32.tar.gz
+WWW-Mechanize-1.34.tar.gz
Index: perl-WWW-Mechanize.spec
===
RCS file: /cvs/extras/rpms/perl-WWW-Mechanize/devel/perl-WWW-Mechanize.spec,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- perl-WWW-Mechanize.spec 6 Feb 2008 02:11:11 - 1.15
+++ perl-WWW-Mechanize.spec 29 May 2008 06:58:07 - 1.16
@@ -10,8 +10,8 @@
%{?_with_livetests:%define livetests 1}
Name: perl-WWW-Mechanize
-Version:1.32
-Release:2%{?dist}
+Version:1.34
+Release:1%{?dist}
Summary:Automates web page form link interaction
Group: Development/Libraries
@@ -87,6 +87,9 @@
%changelog
+* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 1.34-1
+- update to 1.34
+
* Tue Feb 05 2008 Tom spot Callaway [EMAIL PROTECTED] - 1.32-2
- rebuild for new perl
Index: sources
===
RCS file: /cvs/extras/rpms/perl-WWW-Mechanize/devel/sources,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- sources 8 Dec 2007 07:42:02 - 1.10
+++ sources 29 May 2008 06:58:07 - 1.11
@@ -1 +1 @@
-1cc07496c920cce3a2b681831cbf5b8d WWW-Mechanize-1.32.tar.gz
+77a5c025b9a722b62884b7740b8133f9 WWW-Mechanize-1.34.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-WWW-Mechanize/F-9 perl-WWW-Mechanize.spec, 1.15, 1.16 sources, 1.10, 1.11
Author: cweyl
Update of /cvs/extras/rpms/perl-WWW-Mechanize/F-9
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22465
Modified Files:
perl-WWW-Mechanize.spec sources
Log Message:
* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 1.34-1
- update to 1.34
Index: perl-WWW-Mechanize.spec
===
RCS file: /cvs/extras/rpms/perl-WWW-Mechanize/F-9/perl-WWW-Mechanize.spec,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- perl-WWW-Mechanize.spec 6 Feb 2008 02:11:11 - 1.15
+++ perl-WWW-Mechanize.spec 29 May 2008 07:05:05 - 1.16
@@ -10,8 +10,8 @@
%{?_with_livetests:%define livetests 1}
Name: perl-WWW-Mechanize
-Version:1.32
-Release:2%{?dist}
+Version:1.34
+Release:1%{?dist}
Summary:Automates web page form link interaction
Group: Development/Libraries
@@ -87,6 +87,9 @@
%changelog
+* Wed May 28 2008 Chris Weyl [EMAIL PROTECTED] 1.34-1
+- update to 1.34
+
* Tue Feb 05 2008 Tom spot Callaway [EMAIL PROTECTED] - 1.32-2
- rebuild for new perl
Index: sources
===
RCS file: /cvs/extras/rpms/perl-WWW-Mechanize/F-9/sources,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- sources 8 Dec 2007 07:42:02 - 1.10
+++ sources 29 May 2008 07:05:05 - 1.11
@@ -1 +1 @@
-1cc07496c920cce3a2b681831cbf5b8d WWW-Mechanize-1.32.tar.gz
+77a5c025b9a722b62884b7740b8133f9 WWW-Mechanize-1.34.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 448735] Inconsistent @INC
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Inconsistent @INC https://bugzilla.redhat.com/show_bug.cgi?id=448735 --- Additional Comments From [EMAIL PROTECTED] 2008-05-29 05:11 EST --- perl-5.10.0-22.fc9 has the same issues. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-PHP-Serialization - New directory
Author: tibbs Update of /cvs/extras/rpms/perl-PHP-Serialization In directory cvs-int.fedora.redhat.com:/home/fedora/tibbs/tmpcvsZ17083/rpms/perl-PHP-Serialization Log Message: Directory /cvs/extras/rpms/perl-PHP-Serialization added to the repository -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-PHP-Serialization/devel - New directory
Author: tibbs Update of /cvs/extras/rpms/perl-PHP-Serialization/devel In directory cvs-int.fedora.redhat.com:/home/fedora/tibbs/tmpcvsZ17083/rpms/perl-PHP-Serialization/devel Log Message: Directory /cvs/extras/rpms/perl-PHP-Serialization/devel added to the repository -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-PHP-Serialization/devel .cvsignore, NONE, 1.1 Makefile, NONE, 1.1 sources, NONE, 1.1
Author: tibbs
Update of /cvs/extras/rpms/perl-PHP-Serialization/devel
In directory
cvs-int.fedora.redhat.com:/home/fedora/tibbs/tmpcvsZ17083/rpms/perl-PHP-Serialization/devel
Added Files:
.cvsignore Makefile sources
Log Message:
Setup of module perl-PHP-Serialization
--- NEW FILE .cvsignore ---
--- NEW FILE Makefile ---
# Makefile for source rpm: perl-PHP-Serialization
# $Id: Makefile,v 1.1 2008/05/28 19:36:57 tibbs Exp $
NAME := perl-PHP-Serialization
SPECFILE = $(firstword $(wildcard *.spec))
define find-makefile-common
for d in common ../common ../../common ; do if [ -f $$d/Makefile.common ] ;
then if [ -f $$d/CVS/Root -a -w $$/Makefile.common ] ; then cd $$d ; cvs -Q
update ; fi ; echo $$d/Makefile.common ; break ; fi ; done
endef
MAKEFILE_COMMON := $(shell $(find-makefile-common))
ifeq ($(MAKEFILE_COMMON),)
# attept a checkout
define checkout-makefile-common
test -f CVS/Root { cvs -Q -d $$(cat CVS/Root) checkout common echo
common/Makefile.common ; } || { echo ERROR: I can't figure out how to
checkout the 'common' module. ; exit -1 ; } 2
endef
MAKEFILE_COMMON := $(shell $(checkout-makefile-common))
endif
include $(MAKEFILE_COMMON)
--- NEW FILE sources ---
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-PHP-Serialization/devel perl-PHP-Serialization.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: tibbs
Update of /cvs/extras/rpms/perl-PHP-Serialization/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24990/devel
Modified Files:
.cvsignore sources
Added Files:
perl-PHP-Serialization.spec
Log Message:
Initial import.
--- NEW FILE perl-PHP-Serialization.spec ---
Name: perl-PHP-Serialization
Version:0.27
Release:1%{?dist}
Summary:Converts between PHP's serialize() output and the equivalent
Perl structure
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/PHP-Serialization/
Source0:
http://www.cpan.org/authors/id/J/JB/JBROWN/php-serialization/PHP-Serialization-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker) perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%description
Provides a simple, quick means of serializing perl memory structures
(including object data!) into a format that PHP can deserialize() and
access, and vice versa.
%prep
%setup -q -n PHP-Serialization-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
* Tue Feb 05 2008 Jason Tibbitts [EMAIL PROTECTED] 0.27-1
- Specfile autogenerated by cpanspec 1.74.
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-PHP-Serialization/devel/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- .cvsignore 28 May 2008 19:36:57 - 1.1
+++ .cvsignore 28 May 2008 20:11:32 - 1.2
@@ -0,0 +1 @@
+PHP-Serialization-0.27.tar.gz
Index: sources
===
RCS file: /cvs/extras/rpms/perl-PHP-Serialization/devel/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sources 28 May 2008 19:36:57 - 1.1
+++ sources 28 May 2008 20:11:32 - 1.2
@@ -0,0 +1 @@
+2fb3f63071c5c2119b4eebe39b329684 PHP-Serialization-0.27.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-PHP-Serialization Makefile,NONE,1.1 import.log,NONE,1.1
Author: tibbs
Update of /cvs/extras/rpms/perl-PHP-Serialization
In directory
cvs-int.fedora.redhat.com:/home/fedora/tibbs/tmpcvsZ17083/rpms/perl-PHP-Serialization
Added Files:
Makefile import.log
Log Message:
Setup of module perl-PHP-Serialization
--- NEW FILE Makefile ---
# Top level Makefile for module perl-PHP-Serialization
all : CVS/Root common-update
@cvs update
common-update : common
@cd common cvs update
common : CVS/Root
@cvs checkout common
CVS/Root :
@echo ERROR: This does not look like a CVS checkout exit 1
clean :
@find . -type f -name *~ -exec rm -fv {} \;
--- NEW FILE import.log ---
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 448735] Inconsistent @INC
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Inconsistent @INC https://bugzilla.redhat.com/show_bug.cgi?id=448735 --- Additional Comments From [EMAIL PROTECTED] 2008-05-29 08:16 EST --- (In reply to comment #2) Well, if I remove the empty directory /usr/lib/perl5/vendor_perl/5.8.7, then it disappears from @INC. That's one half of the issue. The real issue is # rpm -q --provides perl | grep COMPAT perl(:MODULE_COMPAT_5.10.0) Note: No COMPAT_5.8.* = You can't install packages, which rpm-wise Require perl(:MODULE_COMPAT_5.8...) = Though these package might be functional at run-time, these package are broken rpm-wise. The report also shows another inconsistency: on i386, site_perl is under /usr/lib*, while on x86_64 it is under /usr/local/lib*. Which is right? Since our rpm's should install to vendor_perl, not site_perl, it would seem that /usr/local/lib* is the right place for site_perl. How do other distros handle site_perl? But we have to do something about backward compatibility... Would a symlink suffice? No way - never. /usr/local/lib* is not Fedora's business. Fedora may set up perl's site_perl configuration to point to something below /usr/local, but adding a symlink is no-no. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 448735] Inconsistent @INC
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Inconsistent @INC https://bugzilla.redhat.com/show_bug.cgi?id=448735 --- Additional Comments From [EMAIL PROTECTED] 2008-05-29 07:57 EST --- Well, if I remove the empty directory /usr/lib/perl5/vendor_perl/5.8.7, then it disappears from @INC. I guess we should not deliberately break old third party modules, so we might keep that as a candidate for the @INC, but should not pack the empty dirs to the rpm. The report also shows another inconsistency: on i386, site_perl is under /usr/lib*, while on x86_64 it is under /usr/local/lib*. Which is right? Since our rpm's should install to vendor_perl, not site_perl, it would seem that /usr/local/lib* is the right place for site_perl. But we have to do something about backward compatibility... Would a symlink suffice? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[packaging] noarch package that creates arch dependant paths
Hello.
During this review:
https://bugzilla.redhat.com/show_bug.cgi?id=444755
This noarch package seems to create an empty arch dependant directory.
%{perl_vendorarch}/auto/*
If %{perl_vendorlib}/* is used (as the skeleton perl spec file suggest).
Then it leads for this empty directory to be listed in the package.
(at least if the package is built on %{_lib} == lib systems.)
At this time, I haven't seen any other case where this problem appears.
But I wonder why this directory is created ?
The workaround would be to have
%{perl_vendorlib}/Lingua/
But this remains weird...
Nicolas (kwizart)
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-Regexp-Common/devel .cvsignore, 1.2, 1.3 perl-Regexp-Common.spec, 1.7, 1.8 sources, 1.2, 1.3
Author: spot
Update of /cvs/pkgs/rpms/perl-Regexp-Common/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10872
Modified Files:
.cvsignore perl-Regexp-Common.spec sources
Log Message:
update to 2.122, new license
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Regexp-Common/devel/.cvsignore,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- .cvsignore 20 Aug 2005 00:10:13 - 1.2
+++ .cvsignore 29 May 2008 13:49:45 - 1.3
@@ -1 +1 @@
-Regexp-Common-2.120.tar.gz
+Regexp-Common-2.122.tar.gz
Index: perl-Regexp-Common.spec
===
RCS file: /cvs/pkgs/rpms/perl-Regexp-Common/devel/perl-Regexp-Common.spec,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- perl-Regexp-Common.spec 5 Mar 2008 22:14:40 - 1.7
+++ perl-Regexp-Common.spec 29 May 2008 13:49:45 - 1.8
@@ -1,8 +1,10 @@
Name: perl-Regexp-Common
-Version: 2.120
-Release: 7%{?dist}
+Version: 2.122
+Release: 1%{?dist}
Summary: Regexp::Common Perl module
-License: Artistic
+# Old Artistic 1.0 is also valid, but we won't list it here since it is
non-free.
+# Also, it would throw off the automated license check and flag this package.
+License: Artistic 2.0 or MIT or BSD
Group: Development/Libraries
URL: http://search.cpan.org/dist/Regexp-Common/
Source0:
http://www.cpan.org/authors/id/A/AB/ABIGAIL/Regexp-Common-%{version}.tar.gz
@@ -42,6 +44,10 @@
%{_mandir}/man3/*
%changelog
+* Thu May 29 2008 Tom spot Callaway [EMAIL PROTECTED] - 2.122-1
+- update to 2.122
+- license change
+
* Wed Mar 5 2008 Tom spot Callaway [EMAIL PROTECTED] - 2.120-7
- rebuild for new perl
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Regexp-Common/devel/sources,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sources 20 Aug 2005 00:10:13 - 1.2
+++ sources 29 May 2008 13:49:45 - 1.3
@@ -1 +1 @@
-a14f2a3c3f2718a567ec26f57a2bae13 Regexp-Common-2.120.tar.gz
+fdd82fb77f2ef7f85aefd7cfb5107729 Regexp-Common-2.122.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
Re: [packaging] noarch package that creates arch dependant paths
On Thu, 2008-05-29 at 14:59 +0200, Nicolas Chauvet wrote:
Hello.
During this review:
https://bugzilla.redhat.com/show_bug.cgi?id=444755
This noarch package seems to create an empty arch dependant directory.
%{perl_vendorarch}/auto/*
Are you sure it's the package which creates it?
I tripped a similar bug yesterday
(https://bugzilla.redhat.com/show_bug.cgi?id=448744)
which I assume to be caused by a bug in perl or rpm.
If %{perl_vendorlib}/* is used (as the skeleton perl spec file suggest).
Then it leads for this empty directory to be listed in the package.
(at least if the package is built on %{_lib} == lib systems.)
At this time, I haven't seen any other case where this problem appears.
But I wonder why this directory is created ?
The workaround would be to have
%{perl_vendorlib}/Lingua/
But this remains weird...
My bug from yesterday only happened in koji (using ppc), but did not
happen in local mock-chroots.
Ralf
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
