Crypto++ license changed
Crypto++ 5.6.2 license changed from Public Domain to Boost Software License 1.0. http://www.cryptopp.com/License.txt -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
MySQL-libs conflicts with mariadb-libs-5.5.29-7.fc19.x86_64
Hi, Last KDE nightly composes failed because of error DEBUG util.py:264: Error creating Live CD : Failed to build transaction : MySQL-libs conflicts with mariadb-libs-5.5.29-7.fc19.x86_64 http://koji.fedoraproject.org/koji/taskinfo?taskID=5100301 http://koji.fedoraproject.org/koji/taskinfo?taskID=5100302 Previous composes before importing new MySQL package was fine, so last composes problem related with new MySQL. There is also other problem with missing MySQL component in bugzilla, looks like for bugzilla MySQL=mysql, it finds mysql bugs for MySQL package. https://admin.fedoraproject.org/pkgdb/acls/bugs/MySQL -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: DisplayManagerRework: how to handle upgrades?
Lennart Poettering wrote: On Sat, 11.08.12 21:54, alekc...@googlemail.com (alekc...@googlemail.com) wrote: Rex Dieter wrote: OK, so we have https://fedoraproject.org/wiki/Features/DisplayManagerRework#How_To_Test that tells one how to enable the display manager of your choice, via systemctl enable --force xyzdm.service But, how to handle upgrades? (or is this case already handled somehow?) Off the top of my head, perhaps create some sort of scriptlet (probably to live in initscripts, since that's what owned prefdm) to parse /etc/sysconfig/desktop to make some educated guess about which dm service to enable. thoughts? -- rex This is marked as DONE: 8. (Optionally) Patch systemd to parse /etc/sysconfig/desktop at upgrade time and generate a symlink from it that is stored in /etc/systemd/system/display-manager.service and ensures that the original display manager choice is kept. I have DISPLAYMANAGER=KDE in /etc/sysconfig/desktop but symlink was not generated after Rawhide update. Hmm, that would suggest that this bit is borked: http://pkgs.fedoraproject.org/cgit/systemd.git/tree/systemd.spec#n300 If you execute that by hand in a shell, does it work for you then? Lennart This part of code creates symlink (after installing all updates including systemd and kde-settings-kdm). But as I commented in bug 847472, symlink also created after updating systemd if kde-settings-kdm was previously updated to version which adds kdm.servise. If systemd and kde-settings both updated at once then symlink not created. https://bugzilla.redhat.com/show_bug.cgi?id=847472#c5 -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
libzrtpcpp build faild: missing openssl/ec.h
Hi, I tried to build libzrtpcpp-2.0.0 (see http://ftp.gnu.org/gnu/ccrtp/ ). But it is impossible to build it in Fedora because openssl/ec.h is disabled in openssl which is build with no-ec option. libzrtpcpp/crypto/openssl/ZrtpDH.cpp:46:24: fatal error: openssl/ec.h: No such file or directory Is it possible to build openssl with enabled openssl/ec.h? If this is impossible is there any workaround for building libzrtpcpp-2.0.0? -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Making release of KDE LiveDVD spin for Fedora 17
To be more clear, I mean that both 700M and 2G KDE images can be released. 700M still will be main live image released in releases/*/Live/ http://dl.fedoraproject.org/pub/fedora/linux/releases/15/Live/ But 2G image can be released along with other Fedora spins in releases/*/Spins/ http://dl.fedoraproject.org/pub/alt/spins/linux/releases/15/Spins/ Hi, Fedora-Live-KDE CD's released officially are limited by size 700M so there not much space for various KDE applications. Such space becomes even smaller at every Fedora release because of other non-KDE packages. There was digikam and kipi-plugins on Fedora 15 LiveCD but no space for them Fedora 16 CD's. So is it makes sense to release not only 700M-sized Live-KDE images but also 2G-sized (actual size is 1.5G) along with other Fedora spins? Such 2G images additionally may contain basic KDE applications such as digikam, kipi-plugins, kdeedu, kdegames and other. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Making release of KDE LiveDVD spin for Fedora 17
Hi, Fedora-Live-KDE CD's released officially are limited by size 700M so there not much space for various KDE applications. Such space becomes even smaller at every Fedora release because of other non-KDE packages. There was digikam and kipi-plugins on Fedora 15 LiveCD but no space for them Fedora 16 CD's. So is it makes sense to release not only 700M-sized Live-KDE images but also 2G-sized (actual size is 1.5G) along with other Fedora spins? Such 2G images additionally may contain basic KDE applications such as digikam, kipi-plugins, kdeedu, kdegames and other. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Reindl Harald wrote: with VMware-Workstation and VMware-ESXi with ntp configured in the guests there is no time difference at all and i am working day and night with vrtualization and full power managment active I assume that you didn't have my problem with wrong CPU frequency in /proc/cpuinfo when cpufreq modules loaded. Frequency reported here in /proc/cpuinfo is not equal actual CPU frequency. That's why time difference between VM's and host increases very fast. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Vratislav Podzimek wrote: On Mon, 2011-10-17 at 22:40 +0300, alekc...@googlemail.com wrote: Frequency scaling have negative effects for me so I need to have it disabled in BIOS. What negative effects does frequency scaling have for you when using governor performance? -- Vratislav Podzimek I have wrong frequency in /proc/cpuinfo (not equal actual CPU frequency) when loaded cpufreq modules. This leads to a large difference of time between VM's and host. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Marcos Mello wrote: alekcejk at googlemail.com writes: Kernel don't have parameter which can disable using cpufreq built-in modules. This is the main problem because it makes using frequency scaling unconditional. Here's what I use. I hope it can help you. - Install kernel-tools package - Start/enable cpupower.service - If you want a different governor than performance edit /etc/sysconfig/cpupower and replace it in the CPUPOWER_START_OPTS line Marcos Changing governor can't help me, I need frequency scaling completely disabled. cpupower.service starts cpupower which can't set frequency which I set in BIOS (slightly overclocked). This is cpufreq modules problem because frequency which I set is not in range which can be detected by cpufreq modules and cpupower. I have no such problems only when cpufreq modules not loaded. Loading module immediately sets wrong frequency in /proc/cpuinfo while real frequency shown by 'cpupower monitor' is equal to what I set in BIOS. That's why forcing cpufreq module loading by building them into kernel is unacceptable for me. Loading modules by starting service was more flexible. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Marcos Felipe Rasia de Mello wrote: Let's hope the CPU modaliases stuff get done some day. Marcos As workaround now I can use in F16 kernel from F15. But when F15 will be EOL no more kernel updates will be available and using old kernels forever is not good idea. Is there any chance that auto-loading of cpufreq modules (not built into kernel) will be available in F16 before F15 EOL? -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Adam Williamson wrote: On Tue, 2011-10-18 at 18:57 +0300, alekc...@googlemail.com wrote: Changing governor can't help me, I need frequency scaling completely disabled. Have you filed a bug for the problem which frequency scaling causes for you (system time going out of whack)? https://bugzilla.redhat.com/show_bug.cgi?id=746372 I need to add there comments from bug https://bugzilla.redhat.com/show_bug.cgi?id=713572 Have you tried alternative workarounds for that problem, like changing the clock source or using NTP? Both ntpd and chrony can't synchronize time in VM's because of large offset. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Josh Boyer wrote: Chrony is in Fedora, so I'm not entirely sure what you mean there. I mean other systems (even not Linux-based) that may run in virtual machines. The real solution can be adding kernel parameter like cpufreq=disable that can disable using built-in cpufreq modules. Something like that should be submitted to upstream for discussion. Possibly even in patch form. Glad to know about that. Thanks. -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Building cpufreq modules into F16 kernel is it right or wrong?
Hi, The purpose of this bug was to provide native systemd script for cpuspeed in Fedora 16 https://bugzilla.redhat.com/show_bug.cgi?id=713572 But instead of adding systemd script which should load cpufreq modules other solution was provided - cpufreq modules was compiled as built-in in Fedora 16 kernel. This decision was based on assumption that kernel itself can really decide which cpufreq driver to use. But this assumption was wrong for my system which have BIOS option for disabling CPU frequency scaling (SpeedStep). If SpeedStep is enabled in BIOS then kernel uses acpi-cpufreq built-in module but if I will disable frequency scaling in BIOS kernel still loads cpufreq module but p4-clockmod instead of acpi-cpufreq. Such kernel behavior is not what expected because there is no way to really disable frequency scaling for me. So decision to compile cpufreq modules into kernel looks wrong for me and should be revised. Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building cpufreq modules into F16 kernel is it right or wrong?
Frequency scaling have negative effects for me so I need to have it disabled in BIOS. I think that this is not BIOS option broken but broken kernel with built-in cpufreq modules. If hardware supports disabling frequency scaling then should be possibility to do this. BIOS have such possibility, Fedora kernels before F16 also makes it possible to use or not to use scaling. But with F16+ kernels this becomes impossible. Adam Jackson wrote: On Mon, 2011-10-17 at 21:54 +0300, alekc...@googlemail.com wrote: But this assumption was wrong for my system which have BIOS option for disabling CPU frequency scaling (SpeedStep). If SpeedStep is enabled in BIOS then kernel uses acpi-cpufreq built-in module but if I will disable frequency scaling in BIOS kernel still loads cpufreq module but p4-clockmod instead of acpi-cpufreq. Why would you choose broken BIOS options? - ajax -- Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Should I bump cryptopp soname?
Hi, Need help with soname for new libcryptopp build. One of previous cryptopp versions built with disabled SSE2 for x86 because it doesn't built with SSE2. See http://groups.google.com/group/cryptopp-users/browse_thread/thread/d639907b0b1816b9 This was done by adding in config.h line (only for x86) #define CRYPTOPP_DISABLE_SSE2 But negative side of this was conflict when installing both cryptopp-devel i686 x86_64 packages. See bug https://bugzilla.redhat.com/show_bug.cgi?id=645169 config.h is in cryptopp-devel and was used for building other apps (amule and other). Last cryptopp 5.6.1 not needs disabling SSE2 for building on x86 but I can't just build it without patched config.h because amule will crash when using this cryptopp build. If I rebuild amule against new cryptopp build it will not crash. So should I bump libcryptopp soname to .so.7 when building it with enabled SSE2 because of binary incompatibility with .so.6? Soname not set by Crypto++ upstream and was manually added with autotools patch Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Detecting systems booting with GRUB2 in anaconda
Hi, I was asked about problem with installing Fedora 13 on a machine that is dual booting Windows 7 and another distro using GRUB2. There is nothing about GRUB2 in Installation Guide http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/s1-x86-bootloader.html To add, remove, or change the detected operating system settings, use the options provided. It is not clear is anaconda capable to detect properly such distro that uses GRUB2 and add it as additional system to Fedora GRUB menu list? Here is e-mail that I received about this problem: And Fedora has made my ubuntu installation unreachable (remember I'm a novice). I expected GRUB2 like behavior - list the available OSes. Instead I have Fedora and Other, with other pointing to Windows 7. You can try to add Ubuntu to this grub.conf Unfortunately, it looks like I was nailed pretty good on this one. Though a novice, I know that fdisk -l and blockid give me a lot of info. So I know the Ubuntu device (/dev/sda5), but Fedora complains when trying to mount it (Error mounting: wrong fs type, bad option, bad superblock on /dev/sda5). Booting from a Ubuntu LiveCD is the same. fschk -f /dev/sda5 - no joy. And trying to repair the superblock by hand with e2fsck, dumpe2fs and friends has not helped. I think I'm too ignorant of the file system to correct the problems that the installer created. Perhaps you could ask the Fedora team to add a test case: Install Fedora on a machine that is dual booting Windows 7 and another distro using GRUB2. The results might be alarming considering I did not receive one warning for the operation. Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Detecting systems booting with GRUB2 in anaconda
What can expect user that have system booting with GRUB2 and installing Fedora? It is natural to expect that after Fedora installation will be bootable both systems Fedora and other distro. But if GRUB2 can not be detected there should be some kind of warning about that. This is the reason why it may be described in Installation Guide. Fedora 14 Installation Guide have some mention about GRUB2 but it is still not clear is anaconda capable to detect it. http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/s1-x86-bootloader.html Jeff Spaleta wrote: On Mon, Nov 1, 2010 at 10:00 PM, alekc...@googlemail.com wrote: There is nothing about GRUB2 in Installation Guide I'm not sure why there would be an expectation that their would be. Fedora doesn't use Grub2. There are many possible bootloaders that could be on a system. Do we mention any of them by name anywhere? We do have this just above the snippet you quote: You may have a boot loader installed on your system already. An operating system may install its own preferred boot loader, or you may have installed a third-party boot loader.If your boot loader does not recognize Linux partitions, you may not be able to boot Fedora How do we make it any clearer than that? -jef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Adding optional packages to comps.xml
As there are no objections I have added to Sound and Video v4l2ucp in comps.xml for F12-F14, ucview for F11-F14, EL5 (Robert Scheck replied that I can do it) and gtk-v4l for F13-F14. Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Adding optional packages to comps.xml
Hi, I want to add to Sound and Video in comps.xml some optional packages which I not own. v4l2ucp in comps.xml for F11-F14, ucview for F11-F14, EL5 and gtk-v4l for F13-F14. Is there any objections to do this? Alexey Kurov nuc...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
