[Bug 711261] Missing dependency ocaml-curl-devel - libcurl-devel
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=711261 Richard W.M. Jones rjo...@redhat.com changed: What|Removed |Added Flag|needinfo? | --- Comment #2 from Richard W.M. Jones rjo...@redhat.com 2011-06-12 14:27:02 EDT --- Seems good to me ... -- 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. ___ ocaml-devel mailing list ocaml-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ocaml-devel
Re: systemd: please stop trying to take over the world :)
On Sun, Jun 12, 2011 at 6:42 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Sat, Jun 11, 2011 at 12:03:33PM +0100, Peter Robinson wrote: for decades. Fedora 14's init system isn't that different to the first version of RHL (4.0) I started using back in 96. This is somewhat misleading. There have been many rewrites of the init system in the past decade. In fact, the Fedora 14 init system has the capability to be quite different than the SysVinit scripts that were adopted in the mid-90s. What is true is that Fedora 14 had not switched to using the incompatible-with-SysVinit features of its default (or any of its optional) init systems so the presentation and behaviour was almost the same as older SysVinit. That's true but due to the way we used it upstart was more or less a renamed sysVinit. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
OT: Fedora MulitiLiveCD, Current Status?
What is the status of the MultiLiveCD, that was being mooted last year. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
Ok, it looks like I have managed to fix it. I have blacklisted b43 and removed rpc and some other things. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On 06/12/2011 03:27 PM, Frank Murphy wrote: What is the status of the MultiLiveCD, that was being mooted last year. http://alt.fedoraproject.org/pub/alt/releases/15/Multi/ Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On Sun, Jun 12, 2011 at 5:57 AM, Frank Murphy frankl...@gmail.com wrote: What is the status of the MultiLiveCD, that was being mooted last year. We were able to work through all the technical issues with the proposal, and Release Engineering has created Multi-Desktop LiveDVD images for Fedora 15. They even auto-detect whether you're on an i386 or x86_64 platform, but of course you can override the automatic selection. A big thank you goes out to Tom Callaway for rewriting the script that generates the images, Dennis Gilmore for actually getting the images created, and of course Christoph Wickert for championing the idea. The North American ambassadors have had some media created from those images (and I was able to pick up a copy this weekend at South East Linux Fest and watch it work), and I know that the European ambassadors as in the process of ordering media as well. In short, the Multi-Desktop LiveDVD is alive and working well. In addition, we created a Multi-Install image that merged both the i386 and x86_64 installation DVDs into a single disk image. I don't remember whether or not the North American ambassadors had any of these DVDs pressed, but I know the European ambassadors have ordered some of these DVDs. -- Jared Smith Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20110612 changes
Compose started at Sun Jun 12 08:15:22 UTC 2011 Broken deps for x86_64 -- 389-admin-1.1.16-1.fc16.i686 requires libadmsslutil.so.1 389-admin-1.1.16-1.fc16.i686 requires libadminutil.so.1 389-admin-1.1.16-1.fc16.x86_64 requires libadmsslutil.so.1()(64bit) 389-admin-1.1.16-1.fc16.x86_64 requires libadminutil.so.1()(64bit) 389-dsgw-1.1.6-3.fc16.x86_64 requires libadmsslutil.so.1()(64bit) 389-dsgw-1.1.6-3.fc16.x86_64 requires libadminutil.so.1()(64bit) CGSI-gSOAP-1.3.4.0-2.fc15.i686 requires libvomsapi.so.0 CGSI-gSOAP-1.3.4.0-2.fc15.x86_64 requires libvomsapi.so.0()(64bit) OpenEXR_Viewers-1.0.2-3.fc15.x86_64 requires libfltk.so.1.1()(64bit) OpenEXR_Viewers-1.0.2-3.fc15.x86_64 requires libfltk_gl.so.1.1()(64bit) acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) camcardsync-0.1.1-4.fc15.x86_64 requires libhal.so.1()(64bit) db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0 deskbar-applet-2.32.0-4.fc15.x86_64 requires gnome-python2-applet deskbar-applet-2.32.0-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper ed2k_hash-gui-0.4.0-10.fc13.x86_64 requires libfltk.so.1.1()(64bit) emacs-common-mozc-1.1.717.102-2.fc16.x86_64 requires libprotobuf.so.6()(64bit) exaile-0.3.2.1-1.fc16.noarch requires hal fawkes-guis-0.4.2-4.fc16.i686 requires libgraph.so.4 fawkes-guis-0.4.2-4.fc16.i686 requires libcdt.so.4 fawkes-guis-0.4.2-4.fc16.i686 requires libgvc.so.5 fawkes-guis-0.4.2-4.fc16.x86_64 requires libgraph.so.4()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libcdt.so.4()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libgvc.so.5()(64bit) fawkes-plugin-player-0.4.2-4.fc16.x86_64 requires libgeos-3.2.1.so()(64bit) file-browser-applet-0.6.6-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfltk_images.so.1.1()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfltk.so.1.1()(64bit) flpsed-0.5.2-2.fc15.x86_64 requires libfltk.so.1.1()(64bit) gdb-heap-0.5-5.fc16.x86_64 requires glibc(x86-64) = 0:2.13.90 gedit-valencia-0.3.0-4.fc14.x86_64 requires libvala-0.10.so.0()(64bit) gipfel-0.3.2-8.fc15.x86_64 requires libfltk_images.so.1.1()(64bit) gipfel-0.3.2-8.fc15.x86_64 requires libfltk.so.1.1()(64bit) gmediaserver-0.13.0-7.fc15.x86_64 requires libupnp.so.3()(64bit) gmediaserver-0.13.0-7.fc15.x86_64 requires libthreadutil.so.2()(64bit) gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-cpufire-1.6-3.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2) gnome-applet-timer-2.1.4-2.fc15.x86_64 requires gnome-python2-applet = 0:2.16 gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-device-manager-0.2-6.fc15.x86_64 requires libhal.so.1()(64bit) gnome-device-manager-devel-0.2-6.fc15.i686 requires hal-devel = 0:0.5.10 gnome-device-manager-devel-0.2-6.fc15.i686 requires pkgconfig(hal) gnome-device-manager-devel-0.2-6.fc15.x86_64 requires hal-devel = 0:0.5.10 gnome-device-manager-devel-0.2-6.fc15.x86_64 requires pkgconfig(hal) gnome-device-manager-libs-0.2-6.fc15.i686 requires libhal.so.1 gnome-device-manager-libs-0.2-6.fc15.i686 requires hal = 0:0.5.10 gnome-device-manager-libs-0.2-6.fc15.x86_64 requires libhal.so.1()(64bit) gnome-device-manager-libs-0.2-6.fc15.x86_64 requires hal = 0:0.5.10 gnome-netstatus-2.28.2-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdconduit.so.3()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotd.so.5()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdcm.so.4()(64bit) gnome-pilot-eds-2.91.92-1.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) gnome-schedule-2.0.2-6.fc15.noarch requires gnome-python2-applet gnubiff-2.2.13-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gold-2.1.12.2-5.fc15.noarch requires perl(Data::Properties) gorm-1.2.13-0.20110331.fc16.i686 requires
Re: OT: Fedora MulitiLiveCD, Current Status?
On Sun, 12 Jun 2011 13:19:23 +0200, Jared K. Smith wrote: We were able to work through all the technical issues with the proposal, and Release Engineering has created Multi-Desktop LiveDVD images for Fedora 15. They even auto-detect whether you're on an i386 or x86_64 platform, but of course you can override the automatic selection. I was trying to push it since 2009: [Fedora-livecd-list] auto-biarch (x86_64 + i686) LiveDVD patch + ISO https://www.redhat.com/archives/fedora-livecd-list/2009-June/msg00018.html http://fedoraproject.org/wiki/Biarch_Spin so when there exists now a releng-approved biarch spin why isn't the default Download button on http://fedoraproject.org finally the biarch-autodetecting spin? A biarch single-desktop download would be enough with under 2GB size. Besides users benefits Fedora could get the x86_64 ebtter performance over other distros in various magazine reviews this way. Regards, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On 06/12/2011 04:55 AM, Jan Kratochvil wrote: so when there exists now a releng-approved biarch spin why isn't the default Download button on http://fedoraproject.org finally the biarch-autodetecting spin? A biarch single-desktop download would be enough with under 2GB size. 1GB USB flash storage often can be scavenged for no monetary cost. 2GB USB flash storage more often costs real money. The capacity of a CD-R is 700MB, and there are still-very-usable 5-year-old boxes (even x86_64) that cannot boot from a USB harddrive. -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On Sun, 12 Jun 2011 14:16:41 +0200, John Reiser wrote: 1GB USB flash storage often can be scavenged for no monetary cost. 2GB USB flash storage more often costs real money. I got my 2GB flash for free, I do not find this 1GB-2GB difference relevant, the availability also differs according to country how the sizes increase. The capacity of a CD-R is 700MB, and there are still-very-usable 5-year-old boxes (even x86_64) that cannot boot from a USB harddrive. Yes, there exist many old boxes. But the common machine today both downloads and runs 2GB DVD/flash without any problem. I agree there still should be CD-R 700MB 32bit ISO but it is enough to keep it under More options for those few old boxes. People running such old hardware are aware of it. Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On 12/06/11 12:19, Jared K. Smith wrote: On Sun, Jun 12, 2011 at 5:57 AM, Frank Murphyfrankl...@gmail.com wrote: What is the status of the MultiLiveCD, that was being mooted last year. We were able to work through all the technical issues with the proposal, and Release Engineering has created Multi-Desktop LiveDVD images for Fedora 15. snip So they are fully approved Fedora Images, It may be possible for us to include in Freemedia then? -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
Am Sonntag, den 12.06.2011, 10:57 +0100 schrieb Frank Murphy: What is the status of the MultiLiveCD, that was being mooted last year. It is available for download at http://alt.fedoraproject.org/pub/alt/releases/15/Multi/ AFAIK the NA ambassadors have received their media already while EMEA is waiting for the shipment from the company. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Are 3.0 kernels working for anyone?
On Sat, Jun 11, 2011 at 01:27:44PM -0700, Garrett Holmstrom wrote: On 2011-06-11 12:11, Lucas wrote: Actually it does relabel by it self after boot with option selinux=0 That sounds rather useful. How does it know whether or not it was previously booted with selinux=0? booting with selinux=0 creates /.autorelabel If you boot without it, and that file exists, relabeling occurs. Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
Am Sonntag, den 12.06.2011, 13:55 +0200 schrieb Jan Kratochvil: I was trying to push it since 2009: [Fedora-livecd-list] auto-biarch (x86_64 + i686) LiveDVD patch + ISO https://www.redhat.com/archives/fedora-livecd-list/2009-June/msg00018.html http://fedoraproject.org/wiki/Biarch_Spin And we are very grateful for your work. so when there exists now a releng-approved biarch spin why isn't the default Download button on http://fedoraproject.org finally the biarch-autodetecting spin? For various reasons: * It is still a new technology and only got a very limited amount of testing [1]. It was not tested during the release cycle at all but only last minute. Making it default would IMHO be to risky. * Your biarch spin is a spin of it's own and was never approved by the spins SIG. We said we would rather like to see a good tool coming out of this than a spin of it's own. If something should become default, it should be a biarch version of the desktop live CD. * Currently we don't have that, we only have a biarch installeation DVD and the multi desktop spin. A biarch desktop live media was not requested, produced or tested. If you want biarch as the default, please 1. make it a F16 feature 2. get in touch with the different SIGs to discuss the size limit and application selection. If we target a biarch desktop live, we need to at least have the desktop SIG involved. 3. make sure it is available for all milestones, this means alpha, beta and rc so it gets proper testing. 4. have a test day for it. I really like to see wider testing of the images with bare metal hardware and not only virtualization. A biarch single-desktop download would be enough with under 2GB size. There were various attempts to change the limit of the default download, but there never was agreement. If we target 2 GB, we should change the application selection to come close to the limit but not only double 2 700 MB media. If we target 2 GB, people want to see e.g. LibreOffice on the media. IHMO biarch is nice for physical media but not for downloads: As an ambassador I don't need to worry about the arch and only take the biarch spin to an event. If I am to make media for production, say for a media in a computer magazine, it is a clear benefit because I can server all users. But as a user I usually know what I want and only want to download what I need. Ja, I really think you have done an awesome job and I appreciate your work helped me with the multi desktop spin. However I am not sure if it is already mature enough to become the default download or if this is a good thing. But if you decide to make a feature of it for F16 I promise to support you. Regards, Christoph [1] https://fedoraproject.org/wiki/Test_Results:Fedora_15_Final_Multi_Boot_DVD -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: retiring hal-info
2011/4/28 Richard Hughes hughsi...@gmail.com: In a move that will surprise few, I'm retiring hal-info in devel and orphaned it in f15. If hal gets blocked for f16, then I'll do the same for hal-info. The only thing that requires hal-info is hal, and libmtp-hal. Fixed this the other day, sorry for taking so long :-/ Thanks for killing HAL! Linus Walleij -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On Sun, 12 Jun 2011 15:49:18 +0200, Christoph Wickert wrote: * It is still a new technology and only got a very limited amount of testing [1]. It was not tested during the release cycle at all but only last minute. Making it default would IMHO be to risky. It is true Fedora-15-Multi-* is (also) still not listed at: http://fedoraproject.org/en/get-fedora-options If you want biarch as the default, please 1. make it a F16 feature OK, I will try to. 4. have a test day for it. I really like to see wider testing of the images with bare metal hardware and not only virtualization. I was asking how to test EFI but according to still NEW Bug 477035 (EFI BIOS support in qemu) I see the only way is to test EFI on a bare metal hardware during a test day. But as a user I usually know what I want and only want to download what I need. http://smolts.org/static/stats/stats.html says 60% of installations are still i686. I do not believe there is 60% of old hardware and/or specific i686 compatibility needs (such as what I heard about the Adobe Flash plugin). My idea is the problem may be the default image arch being provided. Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Reminder: Fedora 13 end of life on 2011-06-24
Greetings. This is a reminder email about the end of life process for Fedora 13. Fedora 13 will reach end of life on 2011-06-24, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 15, no new packages will be added to the Fedora 13 collection. Please see http://fedoraproject.org/wiki/DistributionUpgrades for more information on upgrading from Fedora 13 to a newer release. kevin signature.asc Description: PGP signature ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
New package maintainer asking for sponsor
Hi. My name is Carlos Olmedo and I'm the upstream developer of libsysactivity [1] and i want to maintain the fedora package because it's old and orphaned. I filed a review request [2] but now i need a sponsor. Anybody interested? ~Carlos [1] http://sourceforge.net/projects/libsysactivity/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=712693 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
Hello list, Any tips how to debug why laptop CPU temperature is around 30 degrees celsius higher on Fedora 14 or Fedora 15 compared to Windows 7 ? Both Linux and Windows were idle when measuring.. I tried both Fedora 14 (Linux 2.6.35) and Fedora 15 (Linux 2.6.38). Laptop specs: - HP Elitebook 8530p. - CPU: Mobile Intel Core 2 Duo T9600 (Penryn). Results: - Windows: CPU is 57 - 65 celsius when idle. - Fedora/Linux: CPU is 85 - 95 celsius when idle. The laptop definitely feels much more hot when in Linux and sometimes shuts down with thermal overheating warning. That overheating problem never happens in Windows. Checking powertop in Linux shows the CPU is mostly running with the lowest MHz available. Not much idle time though.. I was using Core Temp in Windows and /sys ACPI interface in Linux: # cat /sys/bus/acpi/devices/LNXTHERM\:03/thermal_zone/temp 86000 # cat /sys/bus/acpi/devices/LNXTHERM\:03/path \_TZ_.CPUZ acpi -t also shows the same CPU temperature. Fedora 15 Linux 2.6.38 dmesg here: http://pasik.reaktio.net/fedora/f15/cputemp/dmesg-laptop-f15.txt Any ideas how to track what's causing that? All suggestions welcome! Thanks, -- Pasi -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 and Sandy Bridge graphics
is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds this is nothing i would expect with http://ark.intel.com/Product.aspx?id=52213 signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: please stop trying to take over the world :)
On Sun, Jun 12, 2011 at 08:19:03AM +0200, drago01 wrote: On Sun, Jun 12, 2011 at 6:42 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Sat, Jun 11, 2011 at 12:03:33PM +0100, Peter Robinson wrote: for decades. Fedora 14's init system isn't that different to the first version of RHL (4.0) I started using back in 96. This is somewhat misleading. There have been many rewrites of the init system in the past decade. In fact, the Fedora 14 init system has the capability to be quite different than the SysVinit scripts that were adopted in the mid-90s. What is true is that Fedora 14 had not switched to using the incompatible-with-SysVinit features of its default (or any of its optional) init systems so the presentation and behaviour was almost the same as older SysVinit. That's true but due to the way we used it upstart was more or less a renamed sysVinit. Which is what I said in my last sentence, yes? ;-) I wanted to clarify that there have been a lot of new, rewritten init systems in the Linux ecosystem in the past decade, including upstart. It's just the Fedora default init system that's been an old fuddy-duddy about adopting any of the rewritten-requiring features until now. -Toshio pgprGP1DjmOBj.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
intel 82579LM/82574L network not working on the same machine?
if have the following two network cards
the 02:00.0 is an additional pci-express-card and recognized as eth0
the 00:19.0 is on-board and ignored from the system
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
why is the on-board not activated while it is receiving broadcast-packets
DMESG:
pci :00:19.0: reg 10: [mem 0xfe60-0xfe61]
pci :00:19.0: reg 14: [mem 0xfe628000-0xfe628fff]
pci :00:19.0: reg 18: [io 0xf080-0xf09f]
pci :00:19.0: PME# supported from D0 D3hot D3cold
pci :00:19.0: PME# disabled
only the PCI-Express card is recognized by udev
[root@rh:~]$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10d3 (e1000e) (custom name provided by external tool)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1b:21:b6:5f:28, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
DMESGG of the working card is much more verbose
pci :02:00.0: reg 10: [mem 0xfe4c-0xfe4d]
pci :02:00.0: reg 14: [mem 0xfe40-0xfe47]
pci :02:00.0: reg 18: [io 0xe000-0xe01f]
pci :02:00.0: reg 1c: [mem 0xfe4e-0xfe4e3fff]
pci :02:00.0: reg 30: [mem 0xfe48-0xfe4b pref]
pci :02:00.0: PME# supported from D0 D3hot D3cold
pci :02:00.0: PME# disabled
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
microcode: CPU6 updated to revision 0x17, date = 2011-04-07
microcode: CPU7 updated to revision 0x17, date = 2011-04-07
e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
e1000e :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
e1000e :02:00.0: setting latency timer to 64
alloc irq_desc for 46 on node -1
alloc kstat_irqs on node -1
e1000e :02:00.0: irq 46 for MSI/MSI-X
alloc irq_desc for 47 on node -1
alloc kstat_irqs on node -1
e1000e :02:00.0: irq 47 for MSI/MSI-X
alloc irq_desc for 48 on node -1
alloc kstat_irqs on node -1
e1000e :02:00.0: irq 48 for MSI/MSI-X
e1000e :02:00.0: Disabling ASPM L0s
e1000e :02:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1b:21:b6:5f:28
e1000e :02:00.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e :02:00.0: eth0: MAC: 3, PHY: 8, PBA No: fafa02-0c2
signature.asc
Description: OpenPGP digital signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: please stop trying to take over the world :)
On Sun, Jun 12, 2011 at 6:01 PM, Toshio Kuratomi a.bad...@gmail.com wrote: On Sun, Jun 12, 2011 at 08:19:03AM +0200, drago01 wrote: On Sun, Jun 12, 2011 at 6:42 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Sat, Jun 11, 2011 at 12:03:33PM +0100, Peter Robinson wrote: for decades. Fedora 14's init system isn't that different to the first version of RHL (4.0) I started using back in 96. This is somewhat misleading. There have been many rewrites of the init system in the past decade. In fact, the Fedora 14 init system has the capability to be quite different than the SysVinit scripts that were adopted in the mid-90s. What is true is that Fedora 14 had not switched to using the incompatible-with-SysVinit features of its default (or any of its optional) init systems so the presentation and behaviour was almost the same as older SysVinit. That's true but due to the way we used it upstart was more or less a renamed sysVinit. Which is what I said in my last sentence, yes? ;-) Oh indeed ... probably a case of -E_NOCOFFEE ;) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On Sun, Jun 12, 2011 at 6:00 PM, Reindl Harald h.rei...@thelounge.net wrote: is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds 1) Wrong list 2) Update to F15 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 18:37, schrieb drago01: On Sun, Jun 12, 2011 at 6:00 PM, Reindl Harald h.rei...@thelounge.net wrote: is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds 1) Wrong list because why? F14 is in the middle of the support-cycle 2) Update to F15 give me a way to replace systemd by upstart as in F13, F14 signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On Sun, Jun 12, 2011 at 6:45 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 18:37, schrieb drago01: On Sun, Jun 12, 2011 at 6:00 PM, Reindl Harald h.rei...@thelounge.net wrote: is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds 1) Wrong list because why? F14 is in the middle of the support-cycle Because this is the *development* mailing list, there is a separate list for user support. 2) Update to F15 give me a way to replace systemd by upstart as in F13, F14 upstart is still maintained and shipped, you should be able to install and use it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 18:53, schrieb drago01: On Sun, Jun 12, 2011 at 6:45 PM, Reindl Harald h.rei...@thelounge.net wrote: upstart is still maintained and shipped, you should be able to install and use it. and why in the world is systemd forced after a upgrade via yum where upstart was in use before - upgrades should left core configurations in peace! signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On Sun, Jun 12, 2011 at 6:55 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 18:53, schrieb drago01: On Sun, Jun 12, 2011 at 6:45 PM, Reindl Harald h.rei...@thelounge.net wrote: upstart is still maintained and shipped, you should be able to install and use it. and why in the world is systemd forced after a upgrade via yum where upstart was in use before - upgrades should left core configurations in peace! Upgrade usually means progress not stagnation, if you want to stay in the past don't upgrade. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 18:56, schrieb drago01: On Sun, Jun 12, 2011 at 6:55 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 18:53, schrieb drago01: On Sun, Jun 12, 2011 at 6:45 PM, Reindl Harald h.rei...@thelounge.net wrote: upstart is still maintained and shipped, you should be able to install and use it. and why in the world is systemd forced after a upgrade via yum where upstart was in use before - upgrades should left core configurations in peace! Upgrade usually means progress not stagnation, if you want to stay in the past don't upgrade. you said upstart is still maintained and shipped, you should be able to install and use it - so how and why damned must be a init-replace in a early state forced on a existing system? normally this should be systemd is also available for upgraded systems and you should be able to install and use it signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On Sun, Jun 12, 2011 at 6:59 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 18:56, schrieb drago01: On Sun, Jun 12, 2011 at 6:55 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 18:53, schrieb drago01: On Sun, Jun 12, 2011 at 6:45 PM, Reindl Harald h.rei...@thelounge.net wrote: upstart is still maintained and shipped, you should be able to install and use it. and why in the world is systemd forced after a upgrade via yum where upstart was in use before - upgrades should left core configurations in peace! Upgrade usually means progress not stagnation, if you want to stay in the past don't upgrade. you said upstart is still maintained and shipped, you should be able to install and use it - so how and why damned must be a init-replace in a early state forced on a existing system? That was the case in F14, now we are making the switch. For people that for whatever reasons want upstart it is still here. But for the rest we move on ... But please don't start yet another systemd flamewar we had enough of them. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 19:03, schrieb drago01: On Sun, Jun 12, 2011 at 6:59 PM, Reindl Harald h.rei...@thelounge.net wrote: you said upstart is still maintained and shipped, you should be able to install and use it - so how and why damned must be a init-replace in a early state forced on a existing system? That was the case in F14, now we are making the switch. For people that for whatever reasons want upstart it is still here. But for the rest we move on ... But please don't start yet another systemd flamewar we had enough of them if will not start a flamewar i still have not the time yet to verify a couple of services/service-orders and it is useless for me making a 30 second reboot 2 seconds faster, so i like to use the old init-system and have NO IDEA how to do this and that is why a UPGRADE should not forcing switch essential core-systems if not really needed signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 09:12 PM, Reindl Harald wrote: Am 12.06.2011 19:03, schrieb drago01: On Sun, Jun 12, 2011 at 6:59 PM, Reindl Haraldh.rei...@thelounge.net wrote: you said upstart is still maintained and shipped, you should be able to install and use it - so how and why damned must be a init-replace in a early state forced on a existing system? That was the case in F14, now we are making the switch. For people that for whatever reasons want upstart it is still here. But for the rest we move on ... But please don't start yet another systemd flamewar we had enough of them if will not start a flamewar i still have not the time yet to verify a couple of services/service-orders and it is useless for me making a 30 second reboot 2 seconds faster, so i like to use the old init-system and have NO IDEA how to do this and that is why a UPGRADE should not forcing switch essential core-systems if not really needed Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 19:14, schrieb Lucas: On 06/12/2011 09:12 PM, Reindl Harald wrote: Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. i tried this before my first post this is simply not true because this forces glibc as requirement -- Führe Transaktionsprüfung aus --- Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um aktualisiert zu werden --- Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden --- Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert zu werden --- Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 --- Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 --- Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Abhängigkeitsauflösung beendet Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. You could try running: rpm -Va --nofiles --nodigest [root@rh:/downloads]$ ls insgesamt 40M drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 kernel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 kernel-devel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 kernel-headers-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 root root69K 2011-04-15 05:54 libdrm-2.4.25-1.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 linux-firmware-20110601-1.fc15.noarch.rpm -rw-r--r-- 1 root root 202K 2011-04-28 19:13 xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm -rw-r--r-- 1 root root77K 2011-05-05 22:55 xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 12:55 PM, Reindl Harald wrote: Am 12.06.2011 18:53, schrieb drago01: On Sun, Jun 12, 2011 at 6:45 PM, Reindl Haraldh.rei...@thelounge.net wrote: upstart is still maintained and shipped, you should be able to install and use it. and why in the world is systemd forced after a upgrade via yum where upstart was in use before - upgrades should left core configurations in peace! +1 -- Stephen Clark *NetWolves* Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
On Sunday 12 June 2011 16:56:33 Pasi Kärkkäinen wrote: Hello list, Any tips how to debug why laptop CPU temperature is around 30 degrees celsius higher on Fedora 14 or Fedora 15 compared to Windows 7 ? Both Linux and Windows were idle when measuring.. I tried both Fedora 14 (Linux 2.6.35) and Fedora 15 (Linux 2.6.38). Laptop specs: - HP Elitebook 8530p. - CPU: Mobile Intel Core 2 Duo T9600 (Penryn). Results: - Windows: CPU is 57 - 65 celsius when idle. - Fedora/Linux: CPU is 85 - 95 celsius when idle. The laptop definitely feels much more hot when in Linux and sometimes shuts down with thermal overheating warning. That overheating problem never happens in Windows. Checking powertop in Linux shows the CPU is mostly running with the lowest MHz available. Not much idle time though.. I was using Core Temp in Windows and /sys ACPI interface in Linux: # cat /sys/bus/acpi/devices/LNXTHERM\:03/thermal_zone/temp 86000 # cat /sys/bus/acpi/devices/LNXTHERM\:03/path \_TZ_.CPUZ acpi -t also shows the same CPU temperature. Fedora 15 Linux 2.6.38 dmesg here: http://pasik.reaktio.net/fedora/f15/cputemp/dmesg-laptop-f15.txt Any ideas how to track what's causing that? All suggestions welcome! Thanks, -- Pasi What is the graphics card? I am running this from a laptop of the same model and I see: $ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+30.0°C (crit = +115.0°C) temp2:+50.0°C (crit = +105.0°C) temp3:+26.6°C (crit = +112.0°C) temp4:+58.0°C (crit = +112.0°C) temp5:+46.0°C (crit = +90.0°C) temp6:+16.0°C (crit = +112.0°C) radeon-pci-0100 Adapter: PCI adapter temp1:+58.0°C coretemp-isa- Adapter: ISA adapter Core 0: +51.0°C (high = +105.0°C, crit = +105.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +50.0°C (high = +105.0°C, crit = +105.0°C) The only thing I have done in order to cool down graphics card was to run: # echo mid /sys/class/drm/card0/device/power_profile instead of the default value auto (that alternates between mid (middle) and high) for the graphics card. Definitivily I saw an improvement between F14 and F15. Running the graphics card power profile as low brings the temperature even lower (at the expense of some slower window updates). FWIW I never had a problem with overheating. Regarding the comparison with windows (win.. what?) ;-) this computer came with freedos installed so no such luck here. :-D -- José Abílio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
On Sun, Jun 12, 2011 at 06:20:55PM +0100, José Matos wrote: On Sunday 12 June 2011 16:56:33 Pasi Kärkkäinen wrote: Hello list, Any tips how to debug why laptop CPU temperature is around 30 degrees celsius higher on Fedora 14 or Fedora 15 compared to Windows 7 ? Both Linux and Windows were idle when measuring.. I tried both Fedora 14 (Linux 2.6.35) and Fedora 15 (Linux 2.6.38). Laptop specs: - HP Elitebook 8530p. - CPU: Mobile Intel Core 2 Duo T9600 (Penryn). Results: - Windows: CPU is 57 - 65 celsius when idle. - Fedora/Linux: CPU is 85 - 95 celsius when idle. The laptop definitely feels much more hot when in Linux and sometimes shuts down with thermal overheating warning. That overheating problem never happens in Windows. Checking powertop in Linux shows the CPU is mostly running with the lowest MHz available. Not much idle time though.. I was using Core Temp in Windows and /sys ACPI interface in Linux: # cat /sys/bus/acpi/devices/LNXTHERM\:03/thermal_zone/temp 86000 # cat /sys/bus/acpi/devices/LNXTHERM\:03/path \_TZ_.CPUZ acpi -t also shows the same CPU temperature. Fedora 15 Linux 2.6.38 dmesg here: http://pasik.reaktio.net/fedora/f15/cputemp/dmesg-laptop-f15.txt Any ideas how to track what's causing that? All suggestions welcome! Thanks, -- Pasi What is the graphics card? It's ATI radeon RV635. Do you have the same graphics card? I am running this from a laptop of the same model and I see: $ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+30.0°C (crit = +115.0°C) temp2:+50.0°C (crit = +105.0°C) temp3:+26.6°C (crit = +112.0°C) temp4:+58.0°C (crit = +112.0°C) temp5:+46.0°C (crit = +90.0°C) temp6:+16.0°C (crit = +112.0°C) So your CPU temp is what it should be.. radeon-pci-0100 Adapter: PCI adapter temp1:+58.0°C coretemp-isa- Adapter: ISA adapter Core 0: +51.0°C (high = +105.0°C, crit = +105.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +50.0°C (high = +105.0°C, crit = +105.0°C) The only thing I have done in order to cool down graphics card was to run: # echo mid /sys/class/drm/card0/device/power_profile Oh, I wasn't aware of this. I'll try and see if that makes a difference. instead of the default value auto (that alternates between mid (middle) and high) for the graphics card. Definitivily I saw an improvement between F14 and F15. Running the graphics card power profile as low brings the temperature even lower (at the expense of some slower window updates). FWIW I never had a problem with overheating. Ok, good to know. Regarding the comparison with windows (win.. what?) ;-) this computer came with freedos installed so no such luck here. :-D :) Thanks for the reply! -- Pasi -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 09:18 PM, Reindl Harald wrote: Am 12.06.2011 19:14, schrieb Lucas: On 06/12/2011 09:12 PM, Reindl Harald wrote: Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. i tried this before my first post this is simply not true because this forces glibc as requirement -- Führe Transaktionsprüfung aus --- Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um aktualisiert zu werden --- Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden --- Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert zu werden --- Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 --- Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 --- Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Abhängigkeitsauflösung beendet Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. You could try running: rpm -Va --nofiles --nodigest [root@rh:/downloads]$ ls insgesamt 40M drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 kernel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 kernel-devel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 kernel-headers-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 root root69K 2011-04-15 05:54 libdrm-2.4.25-1.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 linux-firmware-20110601-1.fc15.noarch.rpm -rw-r--r-- 1 root root 202K 2011-04-28 19:13 xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm -rw-r--r-- 1 root root77K 2011-05-05 22:55 xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm Strange, I did exactly the same thing with Fedora 14, I add new kernel, changed xorg and intel driver. But I have i686. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 09:18 PM, Reindl Harald wrote: Am 12.06.2011 19:14, schrieb Lucas: On 06/12/2011 09:12 PM, Reindl Harald wrote: Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. i tried this before my first post this is simply not true because this forces glibc as requirement -- Führe Transaktionsprüfung aus --- Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um aktualisiert zu werden --- Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden --- Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert zu werden --- Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 --- Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 --- Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Abhängigkeitsauflösung beendet Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. You could try running: rpm -Va --nofiles --nodigest [root@rh:/downloads]$ ls insgesamt 40M drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 kernel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 kernel-devel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 kernel-headers-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 root root69K 2011-04-15 05:54 libdrm-2.4.25-1.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 linux-firmware-20110601-1.fc15.noarch.rpm -rw-r--r-- 1 root root 202K 2011-04-28 19:13 xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm -rw-r--r-- 1 root root77K 2011-05-05 22:55 xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm I probably already had libc.so.6 in Fedora 14. Because I did not have any problem with update process. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Hi Reindl, You could also build it from sources. You should already have the latest kernel and the X server updates, compiling the intel driver will then produce a couple of user-space shared libraries that you can place in /usr/lib64/xorg/modules/drivers. That's it. -Ilyes 2011/6/12 Reindl Harald h.rei...@thelounge.net: Am 12.06.2011 19:14, schrieb Lucas: On 06/12/2011 09:12 PM, Reindl Harald wrote: Look, to be able to use Sandy Bridge you need - i915 driver, kernel, and Xorg. You can add Fedora 15 repository and update only kernel, Xorg and intel driver. All of this you can download from koji and install manually. i tried this before my first post this is simply not true because this forces glibc as requirement -- Führe Transaktionsprüfung aus --- Paket kernel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-devel.x86_64 0:2.6.38.8-31.fc15 markiert, um installiert zu werden --- Paket kernel-headers.x86_64 0:2.6.38.8-31.fc15 markiert, um aktualisiert zu werden --- Paket libdrm.x86_64 0:2.4.25-1.fc15 markiert, um aktualisiert zu werden --- Paket linux-firmware.noarch 0:20110601-1.fc15 markiert, um aktualisiert zu werden --- Paket xorg-x11-drv-intel.x86_64 0:2.14.0-6.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 --- Paket xorg-x11-server-Xorg.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Verarbeite Abhängigkeiten: libc.so.6(GLIBC_2.14)(64bit) für Paket: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 --- Paket xorg-x11-server-common.x86_64 0:1.10.1-14.fc15 markiert, um aktualisiert zu werden -- Abhängigkeitsauflösung beendet Fehler: Package: xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64 (/xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Fehler: Package: xorg-x11-drv-intel-2.14.0-6.fc15.x86_64 (/xorg-x11-drv-intel-2.14.0-6.fc15.x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. You could try running: rpm -Va --nofiles --nodigest [root@rh:/downloads]$ ls insgesamt 40M drwxr-xr-x 16 harry verwaltung 4,0K 2011-06-09 10:58 teletest -rw-r--r-- 1 harry verwaltung 23M 2011-06-12 19:17 kernel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 6,8M 2011-06-12 19:17 kernel-devel-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 739K 2011-06-12 19:16 kernel-headers-2.6.38.8-31.fc15.x86_64.rpm -rw-r--r-- 1 root root 69K 2011-04-15 05:54 libdrm-2.4.25-1.fc15.x86_64.rpm -rw-r--r-- 1 harry verwaltung 8,3M 2011-06-12 19:17 linux-firmware-20110601-1.fc15.noarch.rpm -rw-r--r-- 1 root root 202K 2011-04-28 19:13 xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm -rw-r--r-- 1 root root 77K 2011-05-05 22:55 xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm -rw-r--r-- 1 root root 1,4M 2011-05-05 22:52 xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
2011/6/12 Pasi Kärkkäinen pa...@iki.fi: Hello list, Any tips how to debug why laptop CPU temperature is around 30 degrees celsius higher on Fedora 14 or Fedora 15 compared to Windows 7 ? Both Linux and Windows were idle when measuring.. I tried both Fedora 14 (Linux 2.6.35) and Fedora 15 (Linux 2.6.38). Laptop specs: - HP Elitebook 8530p. - CPU: Mobile Intel Core 2 Duo T9600 (Penryn). Same model, no tweaks at all: [helena@moderato ~]$ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+30.0°C (crit = +115.0°C) temp2:+69.0°C (crit = +105.0°C) temp3:+34.3°C (crit = +112.0°C) temp4:+65.0°C (crit = +112.0°C) temp5:+49.0°C (crit = +90.0°C) temp6:+16.0°C (crit = +112.0°C) nouveau-pci-0100 Adapter: PCI adapter temp1:+71.0°C (high = +100.0°C, crit = +110.0°C) coretemp-isa- Adapter: ISA adapter Core 0: +57.0°C (high = +105.0°C, crit = +105.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +58.0°C (high = +105.0°C, crit = +105.0°C) [helena@moderato ~]$ -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What is the status of Features/YumLangpackPlugin?
On Thursday 02 June 2011 16:28:56 Bill Nottingham wrote: 1) This feature will also allow firefox and thunderbird to earn langpacks as they deserve. It certainly allows for it - it requires that the packagers take advantage of it. ISTR discussions in the past that the mechanics of creating the langpacks in the spec file wasn't something they wanted to deal with at the time. yum-langpacks can't help with that part. That is fair, thanks for the note. 2) In the Optional/longer term ideas: 3. recommendation for Packaging Guideline for standard naming of langpacks (eg basename-langpack-lang) This seems an easy step, both to standardize the form of lang as well as to suggest a virtual provides to packages that already provide this, I am thinking in this case of packages like kde-i18n* or kde-i10n*. These virtual provides should be there for any langpack that exists. I suppose I should write an official packaging guideline for this. That would be great, I think that this is a case where we can see the work that is intrinsic to the coordination effort of a linux distribution. Thank you for your work on this feature. Bill -- José Abílio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 19:28, schrieb Lucas: Strange, I did exactly the same thing with Fedora 14, I add new kernel, changed xorg and intel driver. But I have i686. mhh - strange - an trying to update glibc results in chaos Datei oder Verzeichnis nicht gefunden means file not found in english yes as advanced user i was able to repair this with some luck updating only the kernel/kernel-headers/kernel-devel results in no longer able to build kernel-modules (vmware-workstation) and this all for a graphics-driver? i remember times where feodra updated the kernel in the lifetime of a supported release and now you can do nothing if you do not want replace of upstart by systemd, if systemd would not be hardly activated in F15 a dist-upgrade would be no problem BULLSHIT BULLSHIT BULLSHIT scripts/basic/fixdep: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by scripts/basic/fixdep) make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driverLog.o] Fehler 1 make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Fehler 2 make[1]: Leaving directory `/usr/src/kernels/2.6.38.8-31.fc15.x86_64' make: *** [vmmon.ko] Fehler 2 make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' [master 1f5151f] saving uncommitted changes in /etc prior to yum run 1 files changed, 29 insertions(+), 0 deletions(-) create mode 100644 yum.repos.d/fedora-15.repo Aktualisieren : glibc-common-2.14-1.x86_64 1/24 Aktualisieren : glibc-2.14-1.x86_64 2/24 Error: Cannot open file kernel-headers-2.6.38.8-31.fc15.x86_64.rpm: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'kernel-headers-2.6.38.8-31.fc15.x86_64.rpm' TypeError: an integer is required Fehler: Python-Callback bound method RPMTransaction.callback of yum.rpmtrans.RPMTransaction instance at 0x43bcab8 fehlgeschlagen, abbrechen! [root@rh:/downloads]$ rpm -Uvh --force *.rpm Warnung: libdrm-2.4.25-1.fc15.x86_64.rpm: Header V3 RSA/SHA256 Signature, Schlüssel-ID 069c8460: NOKEY Vorbereiten... ### [100%] 1:glibc-common ### [ 8%] 2:glibc ### [ 15%] Fehler: Öffnen von xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von linux-firmware-20110601-1.fc15.noarch.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-headers-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-headers-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-devel-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-devel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von libdrm-2.4.25-1.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 10:02 PM, Reindl Harald wrote: Am 12.06.2011 19:28, schrieb Lucas: Strange, I did exactly the same thing with Fedora 14, I add new kernel, changed xorg and intel driver. But I have i686. mhh - strange - an trying to update glibc results in chaos Datei oder Verzeichnis nicht gefunden means file not found in english yes as advanced user i was able to repair this with some luck updating only the kernel/kernel-headers/kernel-devel results in no longer able to build kernel-modules (vmware-workstation) and this all for a graphics-driver? i remember times where feodra updated the kernel in the lifetime of a supported release and now you can do nothing if you do not want replace of upstart by systemd, if systemd would not be hardly activated in F15 a dist-upgrade would be no problem BULLSHIT BULLSHIT BULLSHIT scripts/basic/fixdep: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by scripts/basic/fixdep) make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driverLog.o] Fehler 1 make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Fehler 2 make[1]: Leaving directory `/usr/src/kernels/2.6.38.8-31.fc15.x86_64' make: *** [vmmon.ko] Fehler 2 make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' [master 1f5151f] saving uncommitted changes in /etc prior to yum run 1 files changed, 29 insertions(+), 0 deletions(-) create mode 100644 yum.repos.d/fedora-15.repo Aktualisieren : glibc-common-2.14-1.x86_64 1/24 Aktualisieren : glibc-2.14-1.x86_64 2/24 Error: Cannot open file kernel-headers-2.6.38.8-31.fc15.x86_64.rpm: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'kernel-headers-2.6.38.8-31.fc15.x86_64.rpm' TypeError: an integer is required Fehler: Python-Callbackbound method RPMTransaction.callback ofyum.rpmtrans.RPMTransaction instance at 0x43bcab8 fehlgeschlagen, abbrechen! [root@rh:/downloads]$ rpm -Uvh --force *.rpm Warnung: libdrm-2.4.25-1.fc15.x86_64.rpm: Header V3 RSA/SHA256 Signature, Schlüssel-ID 069c8460: NOKEY Vorbereiten... ### [100%] 1:glibc-common ### [ 8%] 2:glibc ### [ 15%] Fehler: Öffnen von xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von linux-firmware-20110601-1.fc15.noarch.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-headers-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-headers-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-devel-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-devel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von libdrm-2.4.25-1.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Wait a second, have you enable Fedora 15 repository? If you did, yum should find all dependences in there without your help. You need just type yum update xorg-x11-drv-intel. Everything should be there. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 12.06.2011 20:07, schrieb Lucas: On 06/12/2011 10:02 PM, Reindl Harald wrote: Am 12.06.2011 19:28, schrieb Lucas: Strange, I did exactly the same thing with Fedora 14, I add new kernel, changed xorg and intel driver. But I have i686. mhh - strange - an trying to update glibc results in chaos Datei oder Verzeichnis nicht gefunden means file not found in english yes as advanced user i was able to repair this with some luck updating only the kernel/kernel-headers/kernel-devel results in no longer able to build kernel-modules (vmware-workstation) and this all for a graphics-driver? i remember times where feodra updated the kernel in the lifetime of a supported release and now you can do nothing if you do not want replace of upstart by systemd, if systemd would not be hardly activated in F15 a dist-upgrade would be no problem BULLSHIT BULLSHIT BULLSHIT scripts/basic/fixdep: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by scripts/basic/fixdep) make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driverLog.o] Fehler 1 make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Fehler 2 make[1]: Leaving directory `/usr/src/kernels/2.6.38.8-31.fc15.x86_64' make: *** [vmmon.ko] Fehler 2 make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' [master 1f5151f] saving uncommitted changes in /etc prior to yum run 1 files changed, 29 insertions(+), 0 deletions(-) create mode 100644 yum.repos.d/fedora-15.repo Aktualisieren : glibc-common-2.14-1.x86_64 1/24 Aktualisieren : glibc-2.14-1.x86_64 2/24 Error: Cannot open file kernel-headers-2.6.38.8-31.fc15.x86_64.rpm: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'kernel-headers-2.6.38.8-31.fc15.x86_64.rpm' TypeError: an integer is required Fehler: Python-Callbackbound method RPMTransaction.callback ofyum.rpmtrans.RPMTransaction instance at 0x43bcab8 fehlgeschlagen, abbrechen! [root@rh:/downloads]$ rpm -Uvh --force *.rpm Warnung: libdrm-2.4.25-1.fc15.x86_64.rpm: Header V3 RSA/SHA256 Signature, Schlüssel-ID 069c8460: NOKEY Vorbereiten... ### [100%] 1:glibc-common ### [ 8%] 2:glibc ### [ 15%] Fehler: Öffnen von xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von linux-firmware-20110601-1.fc15.noarch.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-headers-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-headers-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von glibc-devel-2.14-1.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-devel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von kernel-2.6.38.8-31.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von libdrm-2.4.25-1.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Fehler: Öffnen von xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64.rpm fehlgeschlagen: Datei oder Verzeichnis nicht gefunden Wait a second, have you enable Fedora 15 repository? If you did, yum should find all dependences in there without your help. You need just type yum update xorg-x11-drv-intel. Everything should be there. i am not an idiot this does nothing change in the dependency of F15-GLIBC which seems to be a really bad idea on a F14 system and after running only the F15-Kernel you will not upgrade the other packages Gesamte Downloadgrösse: 1.7 M Ist dies in Ordnung? [j/N] :j Lade Pakete herunter: Setting up and reading Presto delta metadata fedora-15/prestodelta | 2.5 MB 00:01 Processing delta metadata Package(s) data still to download: 1.7 M (1/4): libdrm-2.4.25-1.fc15.x86_64.rpm | 69 kB 00:00 (2/4): xorg-x11-drv-intel-2.14.0-6.fc15.x86_64.rpm | 201 kB 00:00 (3/4): xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64.rpm | 1.4 MB 00:01 (4/4): xorg-x11-server-common-1.10.1-14.fc15.x86_64.rpm | 76 kB 00:00 --
Re: F15 / VirtualBox
On Sat, Jun 11, 2011 at 07:09:19PM +0100, Jeroen van Meeuwen (Kolab Systems) wrote: while you're thinking about what to do in the area of virt-clone / cloning VMs, I recon it would be nice not only to be able to clone VMs that have image files, but also those that have a Logical Volume as their disk device. What I'd really like to see would be fast/lazy cloning of LVs: https://bugzilla.redhat.com/show_bug.cgi?id=638188 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
On Sunday 12 June 2011 18:26:25 Pasi Kärkkäinen wrote: What is the graphics card? It's ATI radeon RV635. Do you have the same graphics card? I think so (but I think that are mixing the references :-) ): # lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 01:00.1 Audio device: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series] so I think that the 365 here refers to the digital sound part. Thanks for the reply! Glad to help. :-) -- Pasi -- José Abílio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Laptop CPU overheating in Fedora, temperature +30 celsius higher than in Windows
2011/6/12 José Matos jama...@fc.up.pt: On Sunday 12 June 2011 18:26:25 Pasi Kärkkäinen wrote: What is the graphics card? It's ATI radeon RV635. Do you have the same graphics card? I think so (but I think that are mixing the references :-) ): # lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 01:00.1 Audio device: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series] so I think that the 365 here refers to the digital sound part. Thanks for the reply! Glad to help. :-) -- Pasi -- José Abílio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel You are probably hitting https://bugzilla.redhat.com/show_bug.cgi?id=702953 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
SYSTEMD: Give us a option for upstart
PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS attachment: screen.png signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Sun, Jun 12, 2011 at 5:23 PM, Reindl Harald h.rei...@thelounge.net wrote: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS BULL***, I CAN'T HEAR YOU! SOUND OFF LIKE YOU GOT A PAIR! josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 12.06.2011 23:35, schrieb Josh Boyer: On Sun, Jun 12, 2011 at 5:23 PM, Reindl Harald h.rei...@thelounge.net wrote: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS BULL***, I CAN'T HEAR YOU! SOUND OFF LIKE YOU GOT A PAIR! there is nothing bullshit why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fed-Devel] Re: SYSTEMD: Give us a option for upstart
On Sun, Jun 12, 2011 at 11:39:17PM +0200, Reindl Harald wrote: WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it I don't agree with the design or the implementation of systemd at all but to call the developers idiots is a little harsh, don't you think? And you shouting in a public mailing list doesn't do much to help your cause. You've a strong tendency to go off at the least little thing, and not only here. Might you consider toning it down? Just a little? John -- To do just the opposite is also a form of imitation. -- Georg Christoph Lichtenberg (1742-1799), German scientist, satirist and philosopher, Notebook D (1773-1775) pgpp0iBDgmlwM.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Sun, Jun 12, 2011 at 5:39 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 12.06.2011 23:35, schrieb Josh Boyer: On Sun, Jun 12, 2011 at 5:23 PM, Reindl Harald h.rei...@thelounge.net wrote: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS BULL***, I CAN'T HEAR YOU! SOUND OFF LIKE YOU GOT A PAIR! there is nothing bullshit Oh, you were trying to have a conversation about something? Sorry, with all the shouting I thought we were doing impromptu Gunnery Sergeant Hartman quotes from Full Metal Jacket. why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored I actually don't know the answer to this question other than Fedora switched to systemd. WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it Amazing what one motivated maintainer and their package can accomplish while everyone else is shouting. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fed-Devel] Re: SYSTEMD: Give us a option for upstart
Am 12.06.2011 23:43, schrieb John R. Dennison: On Sun, Jun 12, 2011 at 11:39:17PM +0200, Reindl Harald wrote: WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it I don't agree with the design or the implementation of systemd at all i agree with the design and idea but not with forcing every user with since years perfectly running systems to use it without any reason - the are hughe differences between a new setup and a upgrade and even on a new setup this should be a decision of the user at the very beginning what init-system he wants to use but to call the developers idiots is a little harsh, don't you think? And you shouting in a public mailing list doesn't do much to help your cause. sorry but it makes me crazy that intel-graphics on newer hardware is slow and buggy like hell and thean cames somebody and says upgrade to Fedora 15 with his little desktop without any developer-tools and services perfectly configured over years signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 12.06.2011 23:45, schrieb Josh Boyer: why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored I actually don't know the answer to this question other than Fedora switched to systemd cool - on linux the apple-way starts also? great - the desicion force systemd for updated installations is the best way to crap down the reputation of linux as a system where the user can decide what he want to run signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On 12/06/11 22:54, Reindl Harald wrote: Am 12.06.2011 23:45, schrieb Josh Boyer: why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored snip Try yum install upstart, kernel arg init=/sbin/upstart YMMV. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Sun, 2011-06-12 at 23:23 +0200, Reindl Harald wrote: I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS Why run Fedora itself on 20 servers? Those are mission capable and in a production environment? Might be free, but not sure I would run all those on this type environment. A slower and more stable platform that is free might be better. That's beside the point, why are you not testing upgrades and working out the issues yourself before even trying, in a test environment? Actually, if they need no magic and are fast enough, why upgrade at all right now and wait until everything is worked out? Not telling you what to do, just bringing up different points/suggestions. -- Mike Chambers Madisonville, KY The best town on Earth! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
RE: SYSTEMD: Give us a option for upstart
PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before No one is stopping you from packaging upstart (assuming someone hasn't done so) for F15. * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES No one is forcing you to use F15 I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS If you're running that many servers, then why are you running Fedora? Considering that Fedora has a stated mission to be the first to introduce new software and that releases are only supported for thirteen months, would it not be wise to go with a distribution that has a) more mature code and b) longer support? John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 12.06.2011 23:58, schrieb Frank Murphy: On 12/06/11 22:54, Reindl Harald wrote: Am 12.06.2011 23:45, schrieb Josh Boyer: why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored snip Try yum install upstart, kernel arg init=/sbin/upstart and that this does not happen automatic on an UPGRADE is a major fault! it seems also not very well working and telling / is already mounted Dateisysteme prüfen /dev/md1: sauber, 48557/1905008 Dateien, 477525/7607040 Blöcke /dev/md0: sauber, 38/128016 Dateien, 47146/511988 Blöcke [ OK ] Root-Dateisystem mit Schreib- und Lesezugriff neu einhängen[ OK ] mount: Laut mtab ist /dev/md1 schon auf / eingehängt Lokale Dateisysteme einhängen: [FEHLGESCHLAGEN] signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On 06/12/2011 05:39 PM, Reindl Harald wrote: Am 12.06.2011 23:35, schrieb Josh Boyer: On Sun, Jun 12, 2011 at 5:23 PM, Reindl Haraldh.rei...@thelounge.net wrote: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS BULL***, I CAN'T HEAR YOU! SOUND OFF LIKE YOU GOT A PAIR! there is nothing bullshit why are users of running systems are forced to change their init-system to systemd? upstart is in the repos but ignored WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it sarcasmdon't you know you will save 15-30 seconds each time you boot up/sarcasm -- Stephen Clark *NetWolves* Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:00, schrieb Mike Chambers: On Sun, 2011-06-12 at 23:23 +0200, Reindl Harald wrote: I DO NOT NEED SYSTEMD ON 20 SERVERS HERE BECAUSE THEY ARE STARTING FAST ENOUGH AND I NEED NO MAGIC WHICH THINKS KNOWS WHAT TO START IN WHICH ORDER SINCE I KNOW WHAT IS RUNNING ON MY SYSTEMS Why run Fedora itself on 20 servers? Because it works perfectly with one version behind Those are mission capable and in a production environment? yes and this time on F14 but the clock goes fast around and since F14 is not supporting the hardware of my new work station (Intel graphics / Sandy Brdige) i have to play around with F15 A slower and more stable platform that is free might be better. Running Fedora since F7 in production environments without any downtime bcause the OS or any upgrade-problems showing that i know what i do That's beside the point, why are you not testing upgrades and working out the issues yourself before even trying, in a test environment? what do you believe what i am doing here? the test says i do not want this crap in this early devel-state on my servers end of the year nobody knows what systemd mislikes on /mnt/storage because if i uncomment it the system starts without any issue and manually mounting works on the other hand this crap tells me the follwoing without bringing httpd up [root@testserver:~]$ service httpd start Starting httpd (via systemctl): [ OK ] [Sun Jun 12 23:30:40 2011] [error] (2)No such file or directory: could not create /var/run/httpd/httpd.pid [Sun Jun 12 23:30:40 2011] [error] httpd: could not log pid to file /var/run/httpd/httpd.pid well this is the F14 build of Apache but shows me that i will go to hell if the output of service start is no longer trustable as years before Actually, if they need no magic and are fast enough, why upgrade at all right now and wait until everything is worked out? because i do not update the servers, i try to bring up my test/build-environemt to get my workstation supported which relys on the same packages as production-servers (ffmpeg, newer httpd-versions, newer php-versions) Not telling you what to do, just bringing up different points/suggestions i knowing my job very well and because this is so i have to upgrade to F15 a longer time before the servers and i see NO SINGLE REASON for systemd on a server at all! signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:13, schrieb Steve Clark: WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it sarcasmdon't you know you will save 15-30 seconds each time you boot up/sarcasm someone come out there and show me how will a 20 second-reboot on the vmware-guest production servers will get 20 seconds faster everybody out there is crying about boot / start times have the peopole nothing to do as reboot their machines? normally i start a computer and then it runs for a day, some weeks or even some months, the same with open programs signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:04, schrieb John Dulaney: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before No one is stopping you from packaging upstart (assuming someone hasn't done so) for F15. it is in the repos and it is replaced by systemd via yum dist-upgrade this is bullshit and should never happen by an upgrade * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES No one is forcing you to use F15 not today but in some months signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On 06/12/2011 06:18 PM, Reindl Harald wrote: Am 13.06.2011 00:13, schrieb Steve Clark: WTF every three years a new pig is forced to run through the city and if any subsystem is runnign well and debugged some idiot comes out of his hole and try replace and force everybody to use it sarcasmdon't you know you will save 15-30 seconds each time you boot up/sarcasm someone come out there and show me how will a 20 second-reboot on the vmware-guest production servers will get 20 seconds faster everybody out there is crying about boot / start times have the peopole nothing to do as reboot their machines? normally i start a computer and then it runs for a day, some weeks or even some months, the same with open programs I agree - saying a main feature of systemd is improved boot times is idiotic. I you boot your system in the morning and shut it down at night what does 30 seconds mean out of 8*60*60 seconds? Nothing. If your are concerned with boot times suspend to disk! -- Stephen Clark *NetWolves* Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:23, schrieb Steve Clark: On 06/12/2011 06:18 PM, Reindl Harald wrote: sarcasmdon't you know you will save 15-30 seconds each time you boot up/sarcasm someone come out there and show me how will a 20 second-reboot on the vmware-guest production servers will get 20 seconds faster everybody out there is crying about boot / start times have the peopole nothing to do as reboot their machines? normally i start a computer and then it runs for a day, some weeks or even some months, the same with open programs I agree - saying a main feature of systemd is improved boot times is idiotic. I you boot your system in the morning and shut it down at night what does 30 seconds mean out of 8*60*60 seconds? Nothing. If your are concerned with boot times suspend to disk! suspend to disk with 16 GB RAM - have fun :-) i have really no problem with systemd but it would be wise to use it only for new installations to get a wider userbase without spit current users in their face instead give them time to play and decide while have the benefit of nerwer kernels and better hardware-support this time systemd is not trustable since if there is a problem with httpd the anser of a service start is OK and the service was not started [root@testserver:~]$ service httpd start Starting httpd (via systemctl): [ OK ] signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am Sonntag, den 12.06.2011, 23:23 +0200 schrieb Reindl Harald: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before systems upgraded with yum still have upstart installed (I did it myself) and you can select the init as a kernel parameter, so obviously nobody is forced. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F15 / VirtualBox
Richard W.M. Jones wrote: On Sat, Jun 11, 2011 at 07:09:19PM +0100, Jeroen van Meeuwen (Kolab Systems) wrote: while you're thinking about what to do in the area of virt-clone / cloning VMs, I recon it would be nice not only to be able to clone VMs that have image files, but also those that have a Logical Volume as their disk device. What I'd really like to see would be fast/lazy cloning of LVs: https://bugzilla.redhat.com/show_bug.cgi?id=638188 That would certainly be a good basis for efficiency and performance enhancement of a VM clone for which the storage is in LVM, but with or without LVM lvlazyclone, to virt-clone or to virt-clone --lazy isn't a showstopper is it? Kind regards, -- kanarip -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Reminder: Fedora 13 end of life on 2011-06-24
On Sun, 12 Jun 2011 08:01:24 -0600 Kevin Fenzi ke...@scrye.com wrote: Greetings. This is a reminder email about the end of life process for Fedora 13. Fedora 13 will reach end of life on 2011-06-24, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 15, no new packages will be added to the Fedora 13 collection. I might wait for F16 to do a clean install. It's the first time I reach an EOL. Can you tell me if the packages in the F13 repository remains available (even though the packages are not updated) past June, or not? Thanks -- nomnex nom...@gmail.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Mon, Jun 13, 2011 at 12:27 AM, Reindl Harald h.rei...@thelounge.net wrote: Am 13.06.2011 00:23, schrieb Steve Clark: On 06/12/2011 06:18 PM, Reindl Harald wrote: sarcasmdon't you know you will save 15-30 seconds each time you boot up/sarcasm someone come out there and show me how will a 20 second-reboot on the vmware-guest production servers will get 20 seconds faster everybody out there is crying about boot / start times have the peopole nothing to do as reboot their machines? normally i start a computer and then it runs for a day, some weeks or even some months, the same with open programs I agree - saying a main feature of systemd is improved boot times is idiotic. I you boot your system in the morning and shut it down at night what does 30 seconds mean out of 8*60*60 seconds? Nothing. If your are concerned with boot times suspend to disk! suspend to disk with 16 GB RAM - have fun :-) i have really no problem with systemd but it would be wise to use it only for new installations to get a wider userbase without spit current users in their face instead give them time to play and decide while have the benefit of nerwer kernels and better hardware-support 1) You said you aren't going to start a flamewar but still opened a new thread shouting some random I hate change, how dare you FORCE something new on me BS 2) No users upgrading should not have a degraded user experience because some users are afraid of changes (those shouldn't be running a distro like fedora in the first place) and to use your words they shouldn't be FORCED to take manual steps to get current software (i.e that is what the upgrade was all about after all). 3) We have a site called bugzilla where problems are supposed to be reported, flamewars do not really solve problems -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:54, schrieb Christoph Wickert: Am Sonntag, den 12.06.2011, 23:23 +0200 schrieb Reindl Harald: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before systems upgraded with yum still have upstart installed (I did it myself) and you can select the init as a kernel parameter, so obviously nobody is forced. my first test-setup had no upstart after upgrade this was only a minimal-installation with RAID10 to look if the RAID is alive after update to F15 the test-machine with the troubles was even not able to reboot after yum-upgrade, after hard restart systemd meant it can not relabel (the system was started with selinux=0 param) and not mount a volume after found out how to ignore this a manual mount /mnt/storage mounted the volume systemd meant it could not without any issue forcing upstart gives error-messages while botting about /sys and / Dateisysteme prüfen /dev/md1: sauber, 48557/1905008 Dateien, 477525/7607040 Blöcke /dev/md0: sauber, 38/128016 Dateien, 47146/511988 Blöcke [ OK ] Root-Dateisystem mit Schreib- und Lesezugriff neu einhängen[ OK ] mount: Laut mtab ist /dev/md1 schon auf / eingehängt Lokale Dateisysteme einhängen: [FEHLGESCHLAGEN] this is a bad user experience and shows my that systemd had been better delayed again for Fedora 16 to not repeat the bad things happended with the way too early incldunfig of pulseaudio and KDE4.0 AND we are speaking here about the absolutely core-system and not a sound-daemon or a desktop environment signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 12:00 PM, Reindl Harald wrote: is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds this is nothing i would expect with http://ark.intel.com/Product.aspx?id=52213 I have done this and its working - I've used rawhide with 2.6.39 kernel and also F15. See my comments below. I'll describe what you need to do using subset of F15. You need newer kernel, xorg* and mesa*. If you pull these from f15 you'll find that the compiler has changed - and you will need a newer compiler - which is fine. You'll also need - as you discovered newer glibc - which is also fine. Back up your system - and then do this: yum --releasever=15 install kernel* xorg* mesa* perf* You'll need to so something like: yum --releasever=15 update kernel* xorg* mesa* perf* yum update to do your updates so you keep picking up just the F15 pieces you need. For me I could not boot the F14 install DVD at all - so I made my own DVD using F14 plus all the pieces frmo F15 which yum tells you you need to satisfy the above. The F15 kernel still seems to have a problem with the rhgb for me using i915 (hardware has nvidia optiumus with nvidia turned off) - a bug which has popped up now and again since 2007 - it seems not to be a problem with 2.6.39 and later kernels - but you wont find a 2.6.39 in koji or rawhide at the moment. (Bug is in rhgb best I can tell) So remove the rhgb out of the kernel line in /boot/grub/grub.conf for the new f15 kernel you installed. The sympton if you dont is machine hangs when it flips rhgb after plymouth has done its thing ... if you look in you /var/log/Xorg.0.log you'll see something like: Xf860OpenConsole: VT_WAITINACTIVE_FAILED: Interrupted system call THe work around is avoidning rhgb for now ... Once kernel-3.0 has settled - that is likely your best bet. I have this working using F15 but am planning to move to 3.0 kernel as soon as its settled down a bit - you'll find the fedora team working hard to get a decent 3.0 kernel in koji. regards gene/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 13.06.2011 01:54, schrieb Genes MailLists: On 06/12/2011 12:00 PM, Reindl Harald wrote: is there any clean way to get newer intel-graphics drivers on fedora 14? performance is horrible and under kde the desktop often hangs for some seconds this is nothing i would expect with http://ark.intel.com/Product.aspx?id=52213 I have done this and its working - I've used rawhide with 2.6.39 kernel and also F15. See my comments below. I'll describe what you need to do using subset of F15. this forces a GLIBC-Upgrade, see my others posts You need newer kernel, xorg* and mesa*. and GLIBC from F15 on F14 this does not work If you pull these from f15 you'll find that the compiler has changed - and you will need a newer compiler - which is fine. You'll also need - as you discovered newer glibc - which is also fine. Back up your system - and then do this: yum --releasever=15 install kernel* xorg* mesa* perf* You'll need to so something like: yum --releasever=15 update kernel* xorg* mesa* perf* yum update to do your updates so you keep picking up just the F15 pieces you need this means change the whole core-system to an undefined state in the worst case this will damage your whole setup or future-security-updates are not possible if dependencies are changing again signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Reminder: Fedora 13 end of life on 2011-06-24
On 06/12/2011 04:11 PM, nomnex wrote: I might wait for F16 to do a clean install. It's the first time I reach an EOL. Can you tell me if the packages in the F13 repository remains available (even though the packages are not updated) past June, or not? Thanks The archives are here: http://archive.fedoraproject.org/pub/archive/fedora/linux/releases/13/ http://archive.fedoraproject.org/pub/archive/fedora/linux/updates/13/ I'm pretty sure the mirror manager will do the right redirect for this. Josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 00:04, schrieb John Dulaney: PLEASE give us a option for systems upgraded with yum NOT USING systemd and force upstart as before No one is stopping you from packaging upstart (assuming someone hasn't done so) for F15. it is in the repos and it is replaced by systemd via yum dist-upgrade this is bullshit and should never happen by an upgrade No, it does happen with upgrade. systemd is supposed to replace upstart whenever an upgrade from F15 is installed. It is explicitly stated that systemd is the default feature, and, as such, it will be installed by default. Therefore, it should happen, and the fact that it does mean that it is working. Essentially, if you do not want systemd, don't use Fedora 15. It is that simple. * the system is running since years * every dist-upgrade via yum was no problem * now see screenshot * WTF is there to relabel if started with selinux=0-kernel-param WHY IN THE WORLD ARE USERS FORCED TO USE SYSTEMD ONLY BECAUSE THEY UPGRAD TO F15? DO THIS FOR NEW INSTALLATIONS BUT NEVER ON UPDATES No one is forcing you to use F15 not today but in some months How so? How is it that in 'some months' you will be forced to use systemd? Are the Chinese going to torture you until you make the switch? Why not go with another distro that does not use systemd, rather than complaining on here and mommicking the rest of us? It really seems that Fedora is not the distribution that fits your application. John Dulaney -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 07:59 PM, Reindl Harald wrote: I have done this and its working - I've used rawhide with 2.6.39 kernel and also F15. See my comments below. I'll describe what you need to do using subset of F15. this forces a GLIBC-Upgrade, see my others posts Yes - I said the same thing below and its needed for good reason - and the newer glibc provides everything needed by the older other f14 binaries - and its fine. You need newer kernel, xorg* and mesa*. and GLIBC from F15 on F14 this does not work It is working for me .. sorry it isn't for you. this means change the whole core-system to an undefined state in the worst case this will damage your whole setup or future-security-updates are not possible if dependencies are changing again It is a perfectly defined state - don't be confused - it is F14 plus some updates. I also showed exactly how to do all updates on an ongoing basis to keep it updated and get all security updates - and keep things in a perfectly defined state ... it is working for me .. Perhaps this is not the way for you if you find it confusing ... my suggestion then is deal with systemd and its bugs/quirks or perhaps install F15 and replace systemd with upstart - that should work the same as f14 + a few f15 packages. Do whatever works for you ... you could try even the new ubuntu if its mesa and xorg are enough up to date. good luck! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 02:28, schrieb John Dulaney: not today but in some months How so? How is it that in 'some months' you will be forced to use systemd? Are the Chinese going to torture you until you make the switch? F14 EOL? No Kernel 2.6.38 while Kernel-Update in the support-cycle not so long ago were absolutly normal - results in F14 bot supporting the Network-Card of my new Workstation, the intel graphcics drivers in F14 are a joke so F14 does not support my hardware because some release changes in the shorter past F15 is a breakage in core-system Why not go with another distro that does not use systemd, rather than complaining on here and mommicking the rest of us? It really seems that Fedora is not the distribution that fits your application. I am using Fedora * since Fedora Core 3 in production * since Fedora Core 5 on Desktops * since Fedora 7 on VOIP Server * since Fedora 9 on all Web/Mail-Servers and NOW it should be the wrong distribution? other things you are dreaming about? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Sun, 12 Jun 2011 23:23:30 +0200 Reindl Harald wrote: * now see screenshot That's probably https://bugzilla.redhat.com/show_bug.cgi?id=709681 * WTF is there to relabel if started with selinux=0-kernel-param Although fedora-autorelabel.service is there, it does not imply that anything is being relabeled. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
Am 13.06.2011 02:29, schrieb Genes MailLists: Perhaps this is not the way for you if you find it confusing ... my suggestion then is deal with systemd and its bugs/quirks or perhaps install F15 and replace systemd with upstart - that should work the same as f14 + a few f15 packages. you should read the thread! i am not able to upgrade to F15 GLIBC without destroy the whole system because yYUM and RPM are stopping after two of 5 GLIBC-packages and only because i am using fedora/yum/rpm since many years the whole setup has not died this way! Do whatever works for you ... you could try even the new ubuntu if its mesa and xorg are enough up to date. *loool* show me how to switch a total amount of 24 steups to another distribution and after the year of work this means some idiot there is breaking some core-component and you will jump to the next? i am using Feodra since NINE releases and now i have the first time really troubles and finally someone tell me the fault is not what Fedora did with F15? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Mon, 13 Jun 2011 00:16:00 +0200 Reindl Harald wrote: [Sun Jun 12 23:30:40 2011] [error] (2)No such file or directory: could not create /var/run/httpd/httpd.pid [Sun Jun 12 23:30:40 2011] [error] httpd: could not log pid to file /var/run/httpd/httpd.pid well this is the F14 build of Apache but shows me that i will go to hell if the output of service start is no longer trustable as years before The F14 build does not have the necessary /etc/tmpfiles.d/httpd.conf file to ensure /var/run/httpd is created on boot. Running F14 packages on F15 is not expected to work. Don't do that. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 02:38, schrieb Michal Schmidt: On Sun, 12 Jun 2011 23:23:30 +0200 Reindl Harald wrote: * now see screenshot That's probably https://bugzilla.redhat.com/show_bug.cgi?id=709681 * WTF is there to relabel if started with selinux=0-kernel-param Although fedora-autorelabel.service is there, it does not imply that anything is being relabeled. and why does it STOP the boot-process at a point no network is available? i thought systemd is magic and does everytime know what is needed why does it start the relabel service i never see with selinux=0 and break the system? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 02:42, schrieb Michal Schmidt: On Mon, 13 Jun 2011 00:16:00 +0200 Reindl Harald wrote: [Sun Jun 12 23:30:40 2011] [error] (2)No such file or directory: could not create /var/run/httpd/httpd.pid [Sun Jun 12 23:30:40 2011] [error] httpd: could not log pid to file /var/run/httpd/httpd.pid well this is the F14 build of Apache but shows me that i will go to hell if the output of service start is no longer trustable as years before The F14 build does not have the necessary /etc/tmpfiles.d/httpd.conf file to ensure /var/run/httpd is created on boot. i am not merlin to build packages before upgrade Running F14 packages on F15 is not expected to work. Don't do that. i will not do that, my F15 package is built after that but it shows that the widely use of systemd is too soon because this crap has to say FAILED and not OK in this case! signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Mon, 13 Jun 2011 02:42:15 +0200 Reindl Harald wrote: and why does it STOP the boot-process at a point no network is available? Mounts from /etc/fstab are considered required unless they are marked with the nofail option. why does it start the relabel service i never see with selinux=0 and break the system? The relabel service was NOT started according to the screenshot. It was aborted. When you manage to fix the mnt-storate.mount problem, it will not start the relabel either. A condition for it to start will not be met. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 and Sandy Bridge graphics
On 06/12/2011 08:40 PM, Reindl Harald wrote: Am 13.06.2011 02:29, schrieb Genes MailLists: Perhaps this is not the way for you if you find it confusing ... my suggestion then is deal with systemd and its bugs/quirks or perhaps install F15 and replace systemd with upstart - that should work the same as f14 + a few f15 packages. you should read the thread! I read the thread - you did not do what I suggested - you did something different ... be that as it may ... I have done this both as an update as an install from a DVD built using mock/pungi which contains F14 fully updated + all the f15 rpm's needed to satisfy the packages I put in my first email. I hear your pain - there is a reason many I know have moved away from F15 - anyway - I have sandy bridge running, as I said,using fully updated F14 + selected packages from F15. YYour hardware may be different - so you may need different things. Good luck. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 02:56, schrieb Michal Schmidt: On Mon, 13 Jun 2011 02:42:15 +0200 Reindl Harald wrote: and why does it STOP the boot-process at a point no network is available? Mounts from /etc/fstab are considered required unless they are marked with the nofail option. why does it start the relabel service i never see with selinux=0 and break the system? The relabel service was NOT started according to the screenshot. It was aborted. When you manage to fix the mnt-storate.mount problem, it will not start the relabel either. A condition for it to start will not be met and because this systemd stopped booting in emergency mode after root-pwd and systemctl default it finsihed starting interesting: mount /mnt/storage manually works after that exclude the mountpint in /etc/fstab results in normal boot and you have everytime mount the LVM manually you call this ready for endusers? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Mon, 13 Jun 2011 02:44:36 +0200 Reindl Harald wrote: but it shows that the widely use of systemd is too soon because this crap has to say FAILED and not OK in this case! Apparently the httpd initscript returned with exit code 0. A service can fail after starting successfully. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: please stop trying to take over the world :)
On Fri, 10 Jun 2011 18:42:11 +0200 Denys Vlasenko wrote: On Fri, 2011-06-10 at 15:36 +0200, Michal Schmidt wrote: Why does systemd link against libpam? systemd does logins now, not /bin/login or gdm or ...? to implement PAMName= (man systemd.exec) I don't see any users of this feature on my F15. I searched with Google and come up empty too. But anyway, assuming it's a useful feature, why it has to be done by systemd? A nice property of systemd is that it takes care of setting up the environment for each service. PAMName can be considered one of the pieces of the environment. It is expected that services will eventually start taking advantage of it and cease to implement these things themselves. It makes them simpler. See http://0pointer.de/public/systemd-man/daemon.html for how new-style daemons are made simpler. libwrap? systemd is a network application now too? to implement TCPWrapName= (man systemd.exec) Again, why it has to be done *by systemd*? As systemd takes away the responsibility of creating sockets from the services when it offers socket activation, it makes sense to offer the option to filter the activation requests using libwrap. Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Mon, 13 Jun 2011 03:01:19 +0200 Reindl Harald wrote: Am 13.06.2011 02:56, schrieb Michal Schmidt: On Mon, 13 Jun 2011 02:42:15 +0200 Reindl Harald wrote: and why does it STOP the boot-process at a point no network is available? Mounts from /etc/fstab are considered required unless they are marked with the nofail option. why does it start the relabel service i never see with selinux=0 and break the system? The relabel service was NOT started according to the screenshot. It was aborted. When you manage to fix the mnt-storate.mount problem, it will not start the relabel either. A condition for it to start will not be met and because this systemd stopped booting in emergency mode after root-pwd and systemctl default it finsihed starting Sorry, I am having trouble parsing this. Are you saying that the relabel service was started then? interesting: mount /mnt/storage manually works after that exclude the mountpint in /etc/fstab results in normal boot and you have everytime mount the LVM manually Have you looked at the bug I linked to? https://bugzilla.redhat.com/show_bug.cgi?id=709681 Is it relevant for your situation? Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
Am 13.06.2011 03:26, schrieb Michal Schmidt: On Mon, 13 Jun 2011 03:01:19 +0200 Reindl Harald wrote: Am 13.06.2011 02:56, schrieb Michal Schmidt: interesting: mount /mnt/storage manually works after that exclude the mountpint in /etc/fstab results in normal boot and you have everytime mount the LVM manually Have you looked at the bug I linked to? https://bugzilla.redhat.com/show_bug.cgi?id=709681 Is it relevant for your situation? Jesus christ - yes this can be the reason can not try now because the machine is building F15-RPMs for some hours now THAN YKOU i will review all /etc/fstab-configurations in a hurry one reason more to switch not to sytsemd while upgarding and get the needed test-user-base with new installations, so they deal easier with systemd while existing users are not forced to troubles really - i love the idea of sytemd but not the way it is introduced for existing users with perfectly working systems and since i am developer as my amin-job a know really that it is impossible to replace complex things without mistakes and that is why i would never force a update this way signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
how to push to stable?
https://admin.fedoraproject.org/updates/ocp-0.1.20-8.fc15 bodhi says of my update: bodhi - 2011-06-10 05:03:46 This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes But clicking the mark as stable button says: This update has not yet met the minimum testing requirements defined in the Package Update Acceptance Criteria Reading the linked to document Package Update Acceptance Criteria is completely unhelpful. How do I push this update to stable? Thanks. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: SYSTEMD: Give us a option for upstart
On Sun, Jun 12, 2011 at 9:26 PM, Michal Schmidt wrote: Have you looked at the bug I linked to? https://bugzilla.redhat.com/show_bug.cgi?id=709681 Is it relevant for your situation? Having a quick look at the link and at the steps to reproduce the bug gave me shivers. Are we really sure that systemd is ready? I mean, I don't even call my code alpha if it can't parse a slash correctly. Did we hurry too much to serve this plate to end users? Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT: Fedora MulitiLiveCD, Current Status?
On Sunday, June 12, 2011 09:30:30 AM Jan Kratochvil wrote: On Sun, 12 Jun 2011 15:49:18 +0200, Christoph Wickert wrote: * It is still a new technology and only got a very limited amount of testing [1]. It was not tested during the release cycle at all but only last minute. Making it default would IMHO be to risky. It is true Fedora-15-Multi-* is (also) still not listed at: http://fedoraproject.org/en/get-fedora-options It is not something on the mirrors or intended for download by users, in a large part because it requires a dual layer DVD burner to use. It would be putting a 3rd copy of most of the content on the mirrors which is too much to ask from them. It is something thats intended for a small section of the fedora universe. the use case of the images was for ambassadors to produce and distribute at events. Dennis signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Reminder: Fedora 13 end of life on 2011-06-24
On 06/12/2011 07:27 PM, Josh Stone wrote: On 06/12/2011 04:11 PM, nomnex wrote: I might wait for F16 to do a clean install. It's the first time I reach an EOL. Can you tell me if the packages in the F13 repository remains available (even though the packages are not updated) past June, or not? Thanks The archives are here: http://archive.fedoraproject.org/pub/archive/fedora/linux/releases/13/ http://archive.fedoraproject.org/pub/archive/fedora/linux/updates/13/ I'm pretty sure the mirror manager will do the right redirect for this. It's certainly doing that just fine for me with my (mostly) Fedora 12 systems. The mirror manager comes back with archive.fedoraproject.org plus a handful of mirrors that still carry F12. -- Bob Nichols NOSPAM is really part of my email address. Do NOT delete it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
On 06/09/2011 08:24 PM, Clément David wrote: Hi, My name is Clément DAVID (aka davidcl) and I'm a french software developer. I'm currently working on Scilab [1]. I'm interested to become a packager for Scientific application or just software toys :). My first package has been approved (thanks to Alexander Kurtakov) [2] and build by koji [3]. My FAS name is davidcl. Welcome to Fedora. Hope to see you around more Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
On 06/07/2011 07:11 AM, Ryan Lewis wrote: Hola Fedora developers, My name is Ryan! Currently i'm a PhD student in computer science theory at dartmouth college. I'm a campus ambassador at dartmouth college. My research interests are in computational applied topology for a brief introduction to field: http://en.wikipedia.org/wiki/Topological_data_analysis. I try to contribute to the community as a campus ambassador. I regularly give away install/live media buttons and stickers to just about everyone, and I use them as prizes when I TA computer science classes (which works really well for getting us dartmouth undergrads to contribute). I've just joined this list, and I'm learning now about how to write RPM spec files, with my ultimate goal of maintaining a few packages. I recently got my koji browser certs, and I've been reading the guidelines. I move pretty slowly on my own, if anyone nearby me is interested in helping me advance my packaging 'foo' as they say, i'd be open to the assistance! Welcome to Fedora Ryan. Are you working on any specific package? have you submitted any for review? I would be happy to help Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
Hey Rahul, I few things are in the works: I am packing this program sketch, as a first taste of learning RPM's https://bugzilla.redhat.com/show_bug.cgi?id=711547 I'm not sure why I haven't heard back from the reviewers after these few days have gone by, maybe I will hear this week? -rhl On Sun, Jun 12, 2011 at 11:06 PM, Rahul Sundaram methe...@gmail.com wrote: On 06/07/2011 07:11 AM, Ryan Lewis wrote: Hola Fedora developers, My name is Ryan! Currently i'm a PhD student in computer science theory at dartmouth college. I'm a campus ambassador at dartmouth college. My research interests are in computational applied topology for a brief introduction to field: http://en.wikipedia.org/wiki/Topological_data_analysis. I try to contribute to the community as a campus ambassador. I regularly give away install/live media buttons and stickers to just about everyone, and I use them as prizes when I TA computer science classes (which works really well for getting us dartmouth undergrads to contribute). I've just joined this list, and I'm learning now about how to write RPM spec files, with my ultimate goal of maintaining a few packages. I recently got my koji browser certs, and I've been reading the guidelines. I move pretty slowly on my own, if anyone nearby me is interested in helping me advance my packaging 'foo' as they say, i'd be open to the assistance! Welcome to Fedora Ryan. Are you working on any specific package? have you submitted any for review? I would be happy to help Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self Introduction
On 06/13/2011 09:27 AM, Ryan Lewis wrote: Hey Rahul, I few things are in the works: I am packing this program sketch, as a first taste of learning RPM's https://bugzilla.redhat.com/show_bug.cgi?id=711547 I'm not sure why I haven't heard back from the reviewers after these few days have gone by, maybe I will hear this week? Not a full review but a cursory look shows you need to do atleast the following: You haven't fixed the issues noted in comment 3. You need not specify the build dependencies if they are part of the default build root. http://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions_2 You don't need to define a buildroot http://fedoraproject.org/wiki/Packaging:Guidelines#BuildRoot_tag No need to specify a clean section. Yours is incorrect and empty http://fedoraproject.org/wiki/Packaging:Guidelines#.25clean You haven't written a changelog. Make sure you run rpmlint on the spec file, srpm and binary rpm Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perlbrew] BR perl(Test::Spec)
commit b0870e36991178c5ed1f9b46508a54da49862546
Author: Iain Arnell iarn...@gmail.com
Date: Sun Jun 12 08:47:38 2011 +0200
BR perl(Test::Spec)
perlbrew.spec |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
---
diff --git a/perlbrew.spec b/perlbrew.spec
index 9bd2d61..c5d3bb6 100644
--- a/perlbrew.spec
+++ b/perlbrew.spec
@@ -1,6 +1,6 @@
Name: perlbrew
Version:0.24
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Manage perl installations in your $HOME
License:MIT
Group: Development/Libraries
@@ -15,6 +15,7 @@ BuildRequires: perl(Path::Class)
BuildRequires: perl(Test::Exception)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Output)
+BuildRequires: perl(Test::Spec)
BuildRequires: perl(Try::Tiny)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
Requires: perl(Devel::PatchPerl) = 0.26
@@ -49,8 +50,6 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
-# no Test::Spec (yet)
-rm t/installation2.t
make test
%files
@@ -61,6 +60,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun Jun 12 2011 Iain Arnell iarn...@gmail.com 0.24-2
+- BR perl(Test::Spec) and reinstate t/installation2.t
+
* Wed Jun 08 2011 Iain Arnell iarn...@gmail.com 0.24-1
- update to latest upstream version
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 712671] New: perl-Shipwright-2.4.26 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Shipwright-2.4.26 is available https://bugzilla.redhat.com/show_bug.cgi?id=712671 Summary: perl-Shipwright-2.4.26 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-Shipwright AssignedTo: robinlee.s...@gmail.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, robinlee.s...@gmail.com Classification: Fedora Story Points: --- Latest upstream release: 2.4.26 Current version in Fedora Rawhide: 2.4.24 URL: http://search.cpan.org/dist/Shipwright/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 712694] perl-Data-FormValidator: Reports invalid field as valid when untaint_all_constraints used
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=712694 --- Comment #1 from Jan Lieskovsky jlies...@redhat.com 2011-06-12 10:36:48 EDT --- This issue affect the versions of the perl-Data-FormValidator package, as shipped with Fedora release of 13, 14, and 15. Please schedule an update (once final upstream patch known / ready). -- 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. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 712694] perl-Data-FormValidator: Reports invalid field as valid when untaint_all_constraints used
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=712694 Jan Lieskovsky jlies...@redhat.com changed: What|Removed |Added CC||fedora-perl-devel-list@redh ||at.com, iarn...@gmail.com -- 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. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 712694] perl-Data-FormValidator: Reports invalid field as valid when untaint_all_constraints used
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=712694 --- Comment #2 from Jan Lieskovsky jlies...@redhat.com 2011-06-12 10:51:13 EDT --- CVE Request: [3] http://www.openwall.com/lists/oss-security/2011/06/12/3 -- 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. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
