Changed license for clojure-1.0.0 (CPL - EPL)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I want to notifiy you, that the license of clojure-1.0.0 was changed from the Common Public License to Eclipse Public License 1.0. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAksf3z4ACgkQZLAIBz9lVu9FjAQAm0uRZ+7wVodnGkmLKiAummkt z/ZyLib/40TNDy3+HujMDZfFezyXXS+VmGWR4S4JZMjONOCA20g87AGWP+oSGwMD L6B5IfeLhsYi+lzr+0h1B++gDxarpRN1uyQV6QteHiSuGoJQAkXIPVHJL5TRmCyu En+3SyiWLEZjiCcrhxU= =05MF -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [RFA] Your [PACKAGE_NAME] did not pass QA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 24.11.2009 16:00, schrieb Chris Adams: What is the real maintenance cost? You have said that core fonts are not going away, so the maintenance cost will not go away. How is badgering other maintainers a good thing? If you don't want to maintain something, then the normal way is to orphan it and let someone else take the job, not badger everybody else using the thing you don't want to maintain anymore. Unfortunately, I have not following the discussion about X core fonts and I'm not a font specialist. If you mean the original bitmap oriented fonts of X11, so they are several reasons to avoid the usage of this kinds of fonts. The may issue with this fonts is, that they are not scaleable to any size you want. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAksL/8oACgkQZLAIBz9lVu/XVwQAqiDLEJfCAxFSTVRaXc2iCod8 buWz0rHqZ1EF2HrULNZP8/5f5XI6pOwmke1R52Zv/q29qWmIHTqTBSUByRfCsnbg 1D4SWmV3tLyiDnX8VyTjia5Qmd3gFVu+swWrZoErvOC0byW6HCFympdnM8pXfd/g ArpyT/VQiG5BpAWESAU= =K0tx -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.11.2009 20:56, schrieb James Laska: preupgrade to F12 is basically not going to work for anyone without significant manual workarounds, due to insufficient disk space on /boot. I think we may need to talk to hughsie and/or the desktop team about removing the preupgrade integration in PackageKit for F10/F11 and how to do preupgrade right for F13 and higher. My last experience with preupgrade was, that I have go an error message because there was not enaugh space on the /boot partition to download a special image. But after rebooting I was able to download this image from a mirror server before my system starts the upgrade process. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkr8aZEACgkQZLAIBz9lVu9edwQAlmTNnElmOCJDHBNxWu8uXuoi 7vuvyJxF+mGGHivNIiKJicpUn0P+aIIp+KglECHZEXW45HUG8Y6QC4L8Il7e1F8+ 4vYpG7FUSH7fCDqA56lXrb8fjv35lZ9ZB4nOo0zyurVR6F/LoZEEqKwTmdcYqOyc SL1KiYEZ1gAwAYMpECo= =Hszt -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: 2009-11-09 Fedora 12 Go/No Go Meeting Minutes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11.11.2009 16:30, schrieb Ikem Krueger: Folks, this question maybe sound stupid but, how do I participate on a meeting? As first you need a IRC client as IRSSI or konversation. With this client you have to make a connection the a irc.freenode.org server. After you are connected you can joe the channel on which the meeting is happen. Of course you should consider the announcement of the meeting to find out on which channel and when the meeting will happens. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkr62dUACgkQZLAIBz9lVu/WlwQA5QwZUebsEMQ/PcnddZAX8fm+ gpXkyhFcglWcWx1zemSp5H8BISqIEha5VYrIJbBWVIH0sfrpPldL5VKd4Q4zNXo9 TXu5No3k86F6FmzeAPemsJzkmdUy3PVPNizf2iTv8sgWp+6JhO51DAxmahD/3VaG jpWWgEshOKrVVtnRjZA= =4ICK -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 test machine for package maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 10.11.2009 21:42, schrieb Kevin Fenzi: Greetings. I have updated my test machine resources for Fedora package maintainers with a new Fedora 12 instance: abraxas.scrye.com or f12-test.scrye.com. As always you can see the full list and get more info at: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers Please feel free to use the new instance to test bugs, build packages or otherwise anything Fedora related that will assist you. At first thank you for your offering of the test machines. Unfortunately, I'm searching a ppc64 system where I can make a su for testing an odd issue with gnu-smalltalk. Unfortunately, this issue only happes on ppc64 systems. On ppc32 it's works fine. this is the reason why I'm search such system. The bombadil.infradead.org system is unusable for me, because I can't do a su or sudo on this system. It may be nice, if we can have a ppc64 test machine in the future. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkr7ETMACgkQZLAIBz9lVu/33QP/UTgQ3qfIabE+V/4cgQlDHPmP eZtZ2Ji7tKqE9iF7MZo7TJPljlL5rDm14YMr0Z+pxLALncE4wbUU8ybntqpJv30b Mfr4dGC7+51UKOdRaKp7G48PEMHJQ3u36wym408vAzJu4OmLYa/QtgibbnABEtfI c4o9jiPWjoTF7DJTgu0= =IwiI -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: GRUB2 In Fedora
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.11.2009 16:29, schrieb Bruno Wolff III: It is a prerelease version. The release string starting with '0' is a tip off that this is the case. The release of grub on Fedora is 9.97 nowaday. As link grub2, this is a prerelease. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkr4PBIACgkQZLAIBz9lVu/JvQQAg1YG1BtZWp5kCyAcwwPgv+iX JNylTC8ZnyO/mgGm7UP4yp/irArmGYD5bjIJogu7RsXmUUHqhlprKT40ZYz5414V beKX7GWsrZ2O4GovVVoJ5KjsgT2YuyL57NoeM3NpV/5Qq95m82EOqyMb/zCwEXJX NHCZ4tVMqJNfmOCJ/Zg= =wXAN -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora with Universal Binaries?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 22.10.2009 19:38, schrieb Jon Masters: Except, they're not really ELF binaries. ELF doesn't allow you to do both at the same time in the headers, so this adds a new header and is essentially an encapsulation for other ELF files. Thus, a kernel patch is required and it would be some time before all kernels supported it. I'm not against the notion of this...but I think some of the usual suspects need to get involved in standardizing such an ELF hack. (You might be able to do something with binfmt_misc as a hack) Jon. Creating FatELF binaries doesn't solve any x86_64 related issues. For example: Old releases of blender was not able to creates proper .blend files when the binary was compiled for x86_64. In this case the created files was not usable on the x86_32 release. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkrgmcEACgkQZLAIBz9lVu++FgP/br8KeMY5vp8V88xv4hoH9pyV 2vuJJyhszaWl/qFN9Iax7Q5p1A3muC/BFHhUu6VWphB2xIj9EXkMhubgVtX7OBBc J+v/wv0bWU2kBVFsYDUcfoiTkxluI4uuttTRoqZm7TUuc9/EMBVwzWGeqsBYoFej xV9jjWk4dGJ/sFlFC3I= =uZBp -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Updates-testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 15.10.2009 17:51, schrieb chasd: Postgres isn't even updatable. You need to do dumps before doing the upgrade. Yes, but you should make the dump with the dump utility of the new release to which you want to update. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkrXWQUACgkQZLAIBz9lVu/5HQP+INo/h8BFMrJ9IuQOqhXQEIUn nTcuB/W4qg7E+rlTt0Ljk5bWOBo4qpEJuxojdP0LXicPawADRlJSuZlEa13rDIPl oAxdZlPpbehSJBKvrCsS6PugFHIJ4uW+hIX6jexH15+2Gzw+QaO2khxbZoZw0B9Y lB8hfNl5731p00m4z08= =VKM0 -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: status of forked zlibs in rsync and zsync
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.09.2009 17:47, schrieb Toshio Kuratomi: That still leaves open the question of why no one has asked rsync upstream to make their fork publicly available instead of hoarding it as a private, internal copy. I would ask, why the modification will not integrated in the 'official' Fedora zlib package? After this integration the fedora maintainer can forward the pach to the upsream author. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkqxC0kACgkQZLAIBz9lVu+zmQQAgHZTiLsAVbps6bCzXD+oHFhV n1/vhtKc80KcxDTyHcw/yiiD43wewyz3EZtCJm1FV+x/TiqdKfroJa+9uExY/tVb RImt9ZrclIS7p+t5AgKDFZ/oXigEfXew6ydkj5G6dP1wfrAFb1jb4qtdLO8cSdGD vV5ldUkbOpDCtYH3+DE= =Uw7o -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: 238Can libvdpau go in Fedora? As far I understand this package itself is open source but has a dependency to the properitary nVidia video driver which is provides by rpmfusion.org. For this reason I vote agains the inclusion of this package into Fedora because I introduce a requirement reference to a third-party repository. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 21.08.2009 15:57, schrieb Adam Jackson: On Fri, 2009-08-21 at 15:39 +0200, Jochen Schmitt wrote: On Thu, 20 Aug 2009 22:10:59 -0400, you wrote: 238Can libvdpau go in Fedora? As far I understand this package itself is open source but has a dependency to the properitary nVidia video driver which is provides by rpmfusion.org. For this reason I vote agains the inclusion of this package into Fedora because I introduce a requirement reference to a third-party repository. I think there's precedents for accepting it for Fedora: - libXNVCtrl, another X extension library that happens to only do anything when the user is running the nvidia binary driver, but which is itself MIT-licensed. - gstreamer-plugins-flumpegdemux, which allows you to separate the audio and video streams from MPEG files, even though the decoding itself is off-limits for Fedora - From my point of view. This cases demostrate, that we need a clarification about the requirements which a package has to fullfill for inclusssion into Fedora. Package which are only useable if you have installed a package which is not part of Fedora may not allow for Fedora. This is the argument why we not contributes eumulators. In common emulators requires special ROM images which contains copyright content. It happens that only nvidia implements VDPAU at the moment, but so what? Any other vendor could too. - A made dicision may not be valid forever. If we will have got a opensource package which allow the usage of vdpau with the close source driver from nvidia we can change this dicision. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkqOrqYACgkQZLAIBz9lVu8IPQP/URKbZwLWz86b6y+8mRJtNv61 sUhgpY8pXQ1ztvf1HKVL2gdj6QnVuzFS6wb4x3UN3UTpErDZaF5x6galuS1zJOOo 5+iSjtkVdxDr12CQTEUT7+weKYTGxw3Vg2cFNzH4j3GkQzo8vxm2DJCDEwXvyZ3Q K8WjxvoHRS/LUXQn5pM= =8/2F -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Plan for tomorrow's (20090821) FESCo meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 21.08.2009 17:10, schrieb Adam Jackson: On Fri, 2009-08-21 at 16:26 +0200, Jochen Schmitt wrote: - From my point of view. This cases demostrate, that we need a clarification about the requirements which a package has to fullfill for inclusssion into Fedora. I don't disagree, but... Package which are only useable if you have installed a package which is not part of Fedora may not allow for Fedora. This is the argument why we not contributes eumulators. In common emulators requires special ROM images which contains copyright content. I think this is a faulty generalization. X is a network protocol. vdpau and xnvctrl applications can be perfectly functional running on a Fedora machine with no nvidia driver installed, if they happen to be talking to some _other_ machine somewhere in the world that does support those extensions. One might argue that this is a trivial distinction, and that it still requires some non-free blob to be made to work, but to make that assertion you're basically saying that interoperability is only acceptable if there's some free implementation of what you're interoperating with. If you follow that idea through, you end up removing pilot-link, libgpod... The emulator rule-of-thumb makes sense to the extent that the emulator itself is the end goal. If the only reason you could want it installed is to play some arcade game ROM then there's pretty clearly no interoperability argument to be made. But libvdpau isn't the end goal; the VDPAU app is the end goal. libvdpau is just how you get there. The emulator RoT also assumes that the copyright holder of the magic bits doesn't _want_ you to use them. NVIDIA clearly wants people to use VDPAU. - ajax Thank you for your explaination. I think we should make a distinct betwenn a regquirement which must install on the same machine and another requirement which is provides by a remote system. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkqOumsACgkQZLAIBz9lVu9MoQP/ZNjwRUZSEUFxRj19pmjKocky 4OfA8yE8k15ZSEGr46wy7aMTshSnN0Ccw3hxwM1Qj+Z/g21XVJlXOK4EyFIz28Mt voBhqg2nYOBbArbBfLs+Jp3BnVZ1WIUdhTtWyDfdo6l5si61QYc5QGL2ZATBaHRT 7BYhDbiZFWxevACyRPE= =QIRs -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Confusion with openal-soft
On Sun, 16 Aug 2009 15:32:51 +0530, you wrote: Apparently openal-soft shouldn't have been pushed to Fedora 11 and Fedora 10. Unfortunately I already did the cvs commits for these branches and only noticed after the Fedora 11 build failed. Heads up for others. What would be the right way to revert these commits? Pushing openal-soft info F-11/F-10 is a violation of the Fedora updating policy. So I'M wondering why someone have filled a rebuild request for blender for this reason. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Confusion with openal-soft
On Sun, 16 Aug 2009 20:34:23 +0200, you wrote: Hello Jochen i have closed the Ticket for rebuild. But you must rebuild it in F12. Yes, I have rebuilt blender agains freealut-1.1.0-10, which was rebult agains openal-soft. Best Regards: Jochen Schmitt References: http://koji.fedoraproject.org/koji/buildinfo?buildID=126989 http://koji.fedoraproject.org/koji/buildinfo?buildID=126871 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Isue on building blender agains system ftgl library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I'm trying to build blender agains the system version of the ftgl libary instead of the bFTGL library which is bundled with blender. Unfortunately, I have got the following error message: /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc build/linux2/lib/libbf_ftfont.a(FTF_TTFont.o): In function `FTF_TTFont::GetBoundingBox(char*, float*, float*, float*, float*, float*, float*, unsigned int)': /home/s4504kr/cvs/fedora/blender/devel/blender-2.49a/source/blender/ftfont/intern/FTF_TTFont.cpp:381: undefined reference to `FTFont::BBox(wchar_t const*, float, float, float, float, float, float)' Unfortunately, I can't find any way to fix this error message. I have tried a const cast without any success. In the include file /usr/include/FTGL/FTFont.h I have find a matching function prototype in the FTFont class, so I not understand why this error message was occured. Perhaps someone have a hint for me to fix this issue. The whole build log and a SRPM you may find at: http://www.herr-schmitt.de/pub/blender/build.log http://www.herr-schmitt.de/pub/blender/blender-2.49a-5.fc12.src.rpm Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkp/dEwACgkQT2AHK6txfgynogCg1UiHXG9KoMNrZQWEL8aQ89jt TqgAnjkjESJprnQSMSVsr9E6krVRomDY =UPwi -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Trouble with koji
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I'm trying to make a scratch build for kaya on rawhide to fix a FTBFS. Unfortunately, I have got the lollowing error message: DEBUG util.py:256: No Package Found for ghc-editline But from my view of point this package should exist. It may be nice, if anyone can help me. You may find the build at: http://koji.fedoraproject.org/koji/taskinfo?taskID=1563211 Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpwyIQACgkQT2AHK6txfgxGBgCfQuiZYYlOYB9btu4oqsBe9Eqj PQ8An1k9qzfl1FqLc7fCry8s3iaFehWt =zRAL -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Need help about XEmacs packaging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I have a package with a xemacs lisp file which refer to lpr-command. If I try to compile this file, I will get an error message that the symbol's value may be void. So I want to ask for the best practice to fix this issue. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpl39gACgkQT2AHK6txfgxrdACgt+0w2wnwq5UbB0cK1m+RsYHS fv0An2O7Wzbgmxq/maREC6uC3v2HoJkS =aFaU -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: fedora-cvs flag could not be set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 15.07.2009 16:31, schrieb Miroslav Suchý: I just wanted to set fedora-cvs flag to ? in my bug https://bugzilla.redhat.com/show_bug.cgi?id=491331 But it is grey (i.e disabled) and I could not change it. I can edit: fedora‑review fedora_requires_release_note needinfo but not fedora-cvs Q: Did I miss some process change? It is bug in BZ? Did somebody set some wrong settings? Did I forgot to set someting in BZ? Question: Why do you want to set this flag. Your package is not approved until yet, so it make no sense to create a CVSAdmin request. As a secons question: Are you a member of the packager group, or do you need a sponsor. If so, please set the FE-NEEDSPONSOR blocker bug on your review request. Best regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpd6dQACgkQT2AHK6txfgwhYgCeIq5Ip/LfSfVn1c+70zXftCuc L8QAniCSjt/8hi1dNAk8iZmKV7m2dZeN =oVqj -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Conditionally applying a patch based on a program's EVR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 09.07.2009 21:59, schrieb Alan Dunn:
I want to conditionally apply a patch in a spec file based upon the
version of a package. (There's an emacs package that needs a patch to
work with the latest version of xemacs, but this patch shouldn't be
applied for previous versions of xemacs.) I know that for checking
something like Fedora version numbers I can use
%if 0%{?fedora} 9
...
%endif
but is there an easy way to do this for a version number in say, EVR
form? That is, something like
I assume, that your match may fixed a issue caused by xemacs.
So, I would to prefer, that the user should make a update to the specific
release of xemacs on which the issue doesn't occurs.
You may write someting link
# You need xemacs = required release to
# fix the following issue ...
Requires:xemacs = required release
Of corse, if the required release may not available on older
distribution, you may embrace the Requires statement into
a condition.
Best Regards:
Jochen Schmitt
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkpWTd8ACgkQT2AHK6txfgyL+ACfYmujoW+Grc46ngj7gFSH1GER
MGgAoMI7fLQnLjin2dJ8HNFFGCDQKy0Z
=WR+q
-END PGP SIGNATURE-
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: readline update?
On Fri, 3 Jul 2009 12:27:47 +0200, you wrote: gnu-smalltalk-3.1-5.fc12 I have revisited this package for a license check and changed the license tag to GPLv2+ with exceptions Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KSplice in Fedora?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 01.07.2009 17:16, schrieb Kevin Kofler: Those people must be trusting their hardware and software (drivers in particular) a lot more than I do. ;-) This behaviour is not right in the time of climatic change. Running a system 7x24 hours make only sense for a server and for this system you have the need to avoid reboots. Avoiding reboots have the advantage of minimizing the time of outage during maintaining your system. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEUEARECAAYFAkpLgnkACgkQT2AHK6txfgwbuACY9udWHZSz5opYT3DQpGckDMck ZACfYAgB+YdUY3we/KWulrypiooOKyE= =6rrv -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KSplice in Fedora?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 01.07.2009 17:48, schrieb Kevin Kofler: Whose behavior? Turning the computer off completely definitely saves more power than suspend to RAM and on some machines also suspend to disk (hibernate). Yes, and this is the reason why a desktop user should turns his coputer completely of to save the maximum of power. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpLhsMACgkQT2AHK6txfgzw0ACfSRYdJFzpAlVwM9lY9SURmx+F eeUAoMx9JmTHe4Vob2KvUDbiE885eJwP =aLyW -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KSplice in Fedora?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 01.07.2009 18:44, schrieb Bill McGonigle: Because Fedora has several kernel update in the lifetime, you have to create a ksplice kernelpatch for each kernel release which is available on Fedora. Since you quoted my post with criteria to avoid this, I have to assume I'm missing your point here. Could you clarify? Ok, lets assume, that we have a security kernel patch for Fedora-10. On Fedora we have kernels from the 2.6.27 and from the 2.6.28 series. This means, that you have to create seperates kernel patch modules for each kernel release which was submitted for Fedora-10. The reseason to do it, is that ksplice is not able to handled patches, which may change global data structures. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpLoVkACgkQT2AHK6txfgzmFACgrhko8Pnppq48txUYl3HS6/QE J+8AoNhj2aSfI5jW4UGTuQQb6x+TD9Tm =0KZA -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KSplice in Fedora?
On Mon, 29 Jun 2009 19:38:58 -0500, you wrote: technology that could possibly be integrated in. fedora-ksplice is only build scripts for the kernel it looks like. ksplice The fedora-ksplice script are doing the following: 1.) Getting the sources of the current running fedora kernel 2.) Prepare the kernel source tree for running ksplice. 3.) Create the kernel patch module on based of a patch and the prepared kernel sources. The main aim is a more convinience way to use ksplice on fedora. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KSplice in Fedora?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 30.06.2009 19:04, schrieb Bill McGonigle: ksplice updates are only available for: 1. kernels that have been the lastest kernel in the past two weeks 2. kernel updates that are remotely exploitable 3. kernel updates that rate 'high' on CVSS I'd have to do more research to be sure, but just guessing this feels like 0-4 candidates per Fedora release cycle. Please keep in mind, that you can't handle a kernel update, if globlal structure was changed. Because Fedora has several kernel update in the lifetime, you have to create a ksplice kernelpatch for each kernel release which is available on Fedora. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpKSUYACgkQT2AHK6txfgxPDgCeLcU53/wFqhdSmydCzn5ToxB6 n0IAoI03A7nF40CXhjqgpYUvE5KfPDfj =d1i6 -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
License changed for hightlight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hallo, beginning with the release 2.10 of highlight, the license of this package is changed from GPLv2 to GPLv3. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkpI7z0ACgkQT2AHK6txfgwrxACg1ppjORljvjxvzQwkkUOCE1vP 6L4An3A00HF0C5Co0jQpgOSVutRvCh/f =HPXM -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Suggestion for improvement https://admin.fedoraproject.org/community
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, in the Fedora Weekly News there was an announcement about the new community portal for Fedora. After I have taken a first look, I want to make the following suggestion. It may be helpful if you can see on the user profile, if the user are a sponsor of the packager group. Nowaday, you have none indicator about this state on the user profile. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAko/2AEACgkQT2AHK6txfgysTQCdGGQmDPSt9nkslI4442Bf92Mt UiUAn2txpD2/0yZTGZcykAs/Wudx3mnd =3/JV -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Heads up: NoArch Sub Packages Feature continues
Am 15.06.2009 16:19, schrieb Florian Festi: Please check your packages[2] whether they can make use of this feature and add your changed packages to the list[3]. I have reread the list of the candidates for noarch sub packages on your list. I wan't to notifiy, that the creation of the noarch package is only possible, if there are no packages required on the package which contains a ExcludeArch or ExclusiveArch statement in the SPEC file. For example the package fedora-ksplice could be a noarch package because it's contains only two shell scripts but unfortunately ksplice which is a dependency of this package is provided only for the intel architiecture. Creating such a package as a noarch package may cause dependencies issues, because the require package will no be available on all plattforms. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: F11 discontinued so fast? :-)
Krzysztof Halasa schrieb: I guess I understand why the following URL is no longer valid, but perhaps the ErrorDocument doesn't work by mistake? http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/iso/ Forbidden The reason is, that the release date of F-11 was sliped to Jun, 9. This slip was caused by a severe issue on anaconda. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: I must be doing something seriously wrong...
Christoph Wickert schrieb: When the flags proposal was announced to fedora-devel, so so a public decision-making could take place *before* making a policy? The proposal was not announced, it's ratification nether and the policy was active for months without anybody getting informed. This is what I'd call a secret. Even the title of thei policy was a bad chosen, because you may thought, the the usage of compiler flags may be the topic of this policy. Hopefully, but the original question is still unanswered then: How is a deluge user supposed the realize the lack of single a function? My opinion is to drop the flag policy entirely, so the flags should be integrated into the application as planed by the upstream. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: I must be doing something seriously wrong...
Christoph Wickert schrieb: Let's not start this discussion again. ;) I'm glad FESCo did the right thing by withdrawing the policy (at least for now). You know, that the flag policy was revert on the last FESCo meeting to take futher examination about it. Best Regards: Jochen Schmitt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
