Re: [Test-Announce] Fedora 17 Final Release Candidate 3 (RC3) Available Now!
I thought I should report that I was shutting down for the night and got a kernel-panic; is there a file to look at so that I can report it? I may not reply for the next 10 hours. On Mon, May 21, 2012 at 10:28 PM, Adam Williamson awill...@redhat.comwrote: On Mon, 2012-05-21 at 22:22 -0700, Richard Vickery wrote: I'm slightly uneasy to install this boot.iso as it looks really small. It's a network installation image. It retrieves the packages to be installed from the online repositories. We have always provided such images for Fedora. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- 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: Stop the git abuse
On Mon, 2012-05-21 at 21:58 +0200, Kevin Kofler wrote: Tom Lane wrote: [ shrug... ] The fact that *you* don't care is not evidence that nobody else cares, and it is certainly not evidence that nobody else should care. The fact that many maintainers have been doing this for years and nobody complained about it is, though. It just doesn't make sense to maintain per-branch changelogs if the specfile is otherwise identical across branches. +1, I personally use both methods depending on the package differences among branches. If the differences are small to none I use merges otherwise cherry-picking. And nobody complained. This definitely should not be mandated one way or other - it should be left on maintainer's discretion. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 17 Final Release Candidate 3 (RC3) Available Now!
On Tue, 2012-05-22 at 15:32 +1000, Amit Saha wrote: On Tue, May 22, 2012 at 3:28 PM, Adam Williamson awill...@redhat.com wrote: On Mon, 2012-05-21 at 22:22 -0700, Richard Vickery wrote: I'm slightly uneasy to install this boot.iso as it looks really small. It's a network installation image. It retrieves the packages to be installed from the online repositories. We have always provided such images for Fedora. I used the nentinst.iso for a VirtualBox installation and it ran smoothly without any hiccups. Currently using it, and its good to get a updated system from the beginning. BTW, just curious - is boot.iso and netinst.iso the one and same? Yes. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On Tue, 22 May 2012 06:23:56 +0200, Jesse Keating wrote: So that the NVR- hash mapping needs to be done by 'fedpkg verrel' which (a) requires network connectivity contradicting GIT local repo, (b) is slow. Hrm, in what way does it require network connectivity? gitbuildhash does require the network to hit the buildsystem, but I thought verrel was all offline. True, I agree now. It is just so slow (0m2.693s now, 0m4.222s with drop_caches=3) I expected it waits for network. Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
Dne 21.5.2012 18:47, Stanislav Ochotnicky napsal(a): Quoting Ralf Corsepius (2012-05-21 17:13:56) On 05/21/2012 12:09 PM, Matej Cepl wrote: On 21.5.2012 10:23, Ralf Corsepius wrote: -1 changelogs are manually written documents and source files. And your commit messages are written by aliens? My change logs are inside of the rpm.spec. You are lucky! I have to write them myself (and I really hate that I have to write the same information thrice I usually write them once: editor *.spec fedpkg clog fedpkg commit -F clog -p [Due to fedpkg clog weaknesses, the commits being generated look awful.] Yes, I didn't like them either. That's why instead of whining I sent Jesse a patch and it's been fixed for a few months. I suggest you retry. Ah, that was you who is proposing patches against guidelines [1] and expectations, so now fedpkg is providing broken clog? Vit [1] https://fedoraproject.org/wiki/Packaging:Guidelines#Changelogs -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On Mon, May 21, 2012 at 10:13:41AM -0400, David Cantrell wrote: We automatically generate the spec file changelog block each time we make a new release of anaconda. Check out scripts/makebumpver in the anaconda git repo on git.fedorahosted.org. For us, the work is done in git.fedorahosted.org and we make .tar.bz2 releases of anaconda. The resulting archive and spec file are then checked in to pkgs.fedoraproject.org and built using fedpkg. Same basic workflow from when it was cvs as well. On this subject, it'd also be good to have an easier method to maintain packages as unpacked source + patches on top, which get turned as automatically as possible into spec files. I'm maintaining a few (RHEL, not Fedora) packages this way, and it sure makes handling patches easier. Also: https://rwmj.wordpress.com/2011/08/09/nice-rpm-git-patch-management-trick/#content Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Self Introduction
Hello everyone, my name is Tomas Mlcoch. I've just submitted my first package review request for createrepo_c (https://bugzilla.redhat.com/show_bug.cgi?id=823811). The package is a C implementation of the original createrepo tool. I'm a student at Brno University of Technology and an intern at Red Hat. The Createrepo_c is my project. Kind Regards Tomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Autoreconf race condition?
Hello all!
I've run into a problem when I was trying to build tftp (master branch) package
locally.
~/work/tftp$ fedpkg local
...
config.status: creating MCONFIG
config.status: creating aconfig.h
configure: WARNING: unrecognized options: --disable-dependency-tracking
+ make -j4
rm -f aconfig.h.in aconfig.h
echo \#define VERSION \tftp-hpa `cat version`\ version.h
autoheader
make -C lib
make -C common
make[1]: Entering directory `/home/jsynacek/work/tftp/tftp-hpa-5.2/common'
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -W -Wall -Wpointer-arith
-Wbad-function-cast -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -Wwrite-strings -Wundef
-Wshadow -Wsign-compare -pipe -fno-strict-aliasing
-I/home/jsynacek/work/tftp/tftp-hpa-5.2 -c tftpsubs.c
make[1]: Entering directory `/home/jsynacek/work/tftp/tftp-hpa-5.2/lib'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/jsynacek/work/tftp/tftp-hpa-5.2/lib'
In file included from tftpsubs.h:41:0,
from tftpsubs.c:34:
/home/jsynacek/work/tftp/tftp-hpa-5.2/config.h:21:73: fatal error:
aconfig.h: No
such file or directory
compilation terminated.
Notice the execution of rm -f aconfig.h *after* make. The spec doesn't seem to
be wrong:
...
autoreconf
%configure
make %{?_smp_mflags}
...
And here is the corresponding part from the build log:
...
autoreconf
CFLAGS=${CFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=gen
CXXFLAGS=${CXXFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune
FFLAGS=${FFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=gen
LDFLAGS=${LDFLAGS:--Wl,-z,relro }; export LDFLAGS;
./configure --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu \
--program-prefix= \
--disable-dependency-tracking \
--prefix=/usr \
--exec-prefix=/usr \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--sysconfdir=/etc \
--datadir=/usr/share \
--includedir=/usr/include \
--libdir=/usr/lib64 \
--libexecdir=/usr/libexec \
--localstatedir=/var \
--sharedstatedir=/var/lib \
--mandir=/usr/share/man \
--infodir=/usr/share/info
make -j4
...
I also noticed a rather weird comment in the Makefile:
# Adding configure to the dependencies serializes this with running
# autoconf, because there are apparently race conditions between
# autoconf and autoheader.
aconfig.h.in: configure.in configure aclocal.m4
rm -f aconfig.h.in aconfig.h
autoheader
This part also seems to be causing my problem. Adding configure to the
dependencies apparently does not help.
I don't really know what the root cause of my problem is. I looks like a race
condition between some of the autotools, but I'm not really sure.
The problem goes away when I add sleep 1 between autoreconf and %configure in
the spec file.
Any ideas?
Thanks,
--
Jan Synacek
Software Engineer, BaseOS team Brno, Red Hat
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
F-17 Branched report: 20120522 changes
Compose started at Tue May 22 08:15:07 UTC 2012 Broken deps for x86_64 -- [LuxRender] LuxRender-blender-0.8.0-13.fc17.x86_64 requires blender(ABI) = 0:2.61 [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires rubygem(fastercsv) aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri [calf] lv2-calf-plugins-0.0.18.6-6.fc17.x86_64 requires lv2core [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [gnome-do-plugins] gnome-do-plugins-banshee-0.8.4-8.fc17.x86_64 requires mono(Banshee.CollectionIndexer) = 0:2.2.0.0 [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [lilv] lilv-devel-0.5.0-3.fc17.i686 requires pkgconfig(lv2core) lilv-devel-0.5.0-3.fc17.x86_64 requires pkgconfig(lv2core) [lv2-EQ10Q-plugins] lv2-EQ10Q-plugins-1.0-10.fc17.x86_64 requires lv2core [lv2-abGate] lv2-abGate-1.1.3-4.fc17.x86_64 requires lv2core [lv2-avw-plugins] lv2-avw-plugins-0.0.6-3.fc17.x86_64 requires lv2core [lv2-fil-plugins] lv2-fil-plugins-2.0-5.fc17.x86_64 requires lv2core [lv2-invada-plugins] lv2-invada-plugins-1.2.0-6.fc17.x86_64 requires lv2core [lv2-kn0ck0ut] lv2-kn0ck0ut-1.1-0.4.git60421a3.fc17.x86_64 requires lv2core [lv2-ll-plugins] lv2-ll-plugins-0.2.8-9.fc17.x86_64 requires lv2core [lv2-mdaEPiano] lv2-mdaEPiano-0-0.2.git9db45842.fc17.x86_64 requires lv2core [lv2-swh-plugins] lv2-swh-plugins-1.0.15-7.20110510.9c9935egit.fc17.x86_64 requires lv2core [lv2-vocoder-plugins] lv2-vocoder-plugins-1-4.fc17.x86_64 requires lv2core [lv2-zynadd-plugins] lv2-zynadd-plugins-1-6.fc17.x86_64 requires lv2core [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-sqlite-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-sqlite-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) [mcollective] mcollective-common-1.3.1-7.fc17.noarch requires ruby(abi) = 0:1.8 [moksha] moksha-0.5.0-5.fc15.noarch requires pyevent [natus] libnatus-V8-0.1.5-2.fc15.x86_64 requires libv8-3.0.0.1.so()(64bit) [ocaml-augeas] ocaml-augeas-0.4-9.fc15.x86_64 requires ocaml(runtime) = 0:3.12.0 [openvrml] libopenvrml-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires java-1.6.0-openjdk(x86-64)
Re: Stop the git abuse
Quoting Vít Ondruch (2012-05-22 10:01:06) Dne 21.5.2012 18:47, Stanislav Ochotnicky napsal(a): Quoting Ralf Corsepius (2012-05-21 17:13:56) On 05/21/2012 12:09 PM, Matej Cepl wrote: On 21.5.2012 10:23, Ralf Corsepius wrote: -1 changelogs are manually written documents and source files. And your commit messages are written by aliens? My change logs are inside of the rpm.spec. You are lucky! I have to write them myself (and I really hate that I have to write the same information thrice I usually write them once: editor *.spec fedpkg clog fedpkg commit -F clog -p [Due to fedpkg clog weaknesses, the commits being generated look awful.] Yes, I didn't like them either. That's why instead of whining I sent Jesse a patch and it's been fixed for a few months. I suggest you retry. Ah, that was you who is proposing patches against guidelines [1] and expectations, so now fedpkg is providing broken clog? You are mixing up spec %changelog with SCM log. Only thing I've changed was removing - in first item and adding 1 empty line after it. I never use clog for creating changelog in spec so I don't know how it's supposed to work. I assume it stopped working right after cvs-fedpkg transition. Guidelines say nothing about SCM log, just about spec %changelog format I just do C-c C-r to raise release number, C-c C-e to write my message, then fedpkg commit -c to create commit out of it. Works like a charm -- Stanislav Ochotnicky sochotni...@redhat.com Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com signature.asc Description: signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Hello, everyone
Hello, everyone, my name is Nazar. I have just made my first package review request(https://bugzilla.redhat.com/show_bug.cgi?id=823873). The package is The Powder Toy game which is very fun. So I want to see it in repo. It is not my project, original code is from http://powdertoy.co.uk/ Nazar -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
Dne 22.5.2012 13:22, Stanislav Ochotnicky napsal(a): Quoting Vít Ondruch (2012-05-22 10:01:06) Dne 21.5.2012 18:47, Stanislav Ochotnicky napsal(a): Quoting Ralf Corsepius (2012-05-21 17:13:56) On 05/21/2012 12:09 PM, Matej Cepl wrote: On 21.5.2012 10:23, Ralf Corsepius wrote: -1 changelogs are manually written documents and source files. And your commit messages are written by aliens? My change logs are inside of the rpm.spec. You are lucky! I have to write them myself (and I really hate that I have to write the same information thrice I usually write them once: editor *.spec fedpkg clog fedpkg commit -F clog -p [Due to fedpkg clog weaknesses, the commits being generated look awful.] Yes, I didn't like them either. That's why instead of whining I sent Jesse a patch and it's been fixed for a few months. I suggest you retry. Ah, that was you who is proposing patches against guidelines [1] and expectations, so now fedpkg is providing broken clog? You are mixing up spec %changelog with SCM log. Only thing I've changed was removing - in first item and adding 1 empty line after it. Yes, that is the issue. Here is example of my real-life changelog: * Thu Feb 14 2012 Vít Ondruch vondr...@redhat.com - 2.21.2-1 - Rebuilt for Ruby 1.9.3. - Updated to heroku 2.21.2. Now if you run fedpkg clog, the the clog file will contain: Rebuilt for Ruby 1.9.3. - Updated to heroku 2.21.2. Which is complete nonsense. I never use clog for creating changelog in spec so I don't know how it's supposed to work. I assume it stopped working right after cvs-fedpkg transition. Neither did I and I don't think it is even possible ;) This seems to be misunderstanding. Guidelines say nothing about SCM log, just about spec %changelog format Yes, they says nothing about scm log, but fedpkg clog had some assumptions, e.g. several lines, each starting with dash. There is no relation between those lines. While in SCM log, you expect something like brief description on first line and more elaborated description on others. I just do C-c C-r to raise release number, C-c C-e to write my message, then fedpkg commit -c to create commit out of it. Works like a charm You can try rpmdev-bumpspec instead. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Replacing libusb1 with libusbx
Hi All, I plan to replace libusb1 with libusbx, libusx is a fork of and a drop in replacement for libusb1. The libusbx fork was started by various libusb-1.0 developers (almost all of them *), because the official maintainer of libusb-1.0 refused to do any stable / tarbal releases for over 18 months and in general was very slow with merging new developments and fixes. Don't be fooled by the recently done libusb-1.0.9 release, that was done by the libusb-1.0 maintainer *after* the libusbx fork was announced and had already done 2 releases. The fact that this release only happened after the fork went public, despite various people including me asking for a release for ages (**) shows that forking was necessary. Anyways, I just included this tidbit to explain why I'm replacing libusb1 with libusbx for Fedora-18 and later. Lets not look backwards, but forwards towards what looks to be a bright future with libusbx :) A rename review request can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=823886 Reviews appreciated! Regards, Hans *) Full disclosure: I'm one of the libusb developers behind the fork **) I was originally promised a 1.0.9 release in time for inclusion into Fedora 16 gold! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On 05/22/2012 01:42 PM, Vít Ondruch wrote: Dne 22.5.2012 13:22, Stanislav Ochotnicky napsal(a): I never use clog for creating changelog in spec so I don't know how it's supposed to work. I assume it stopped working right after cvs-fedpkg transition. Neither did I and I don't think it is even possible ;) Why? To me this only is a matter of how fedpkg formats extracted %changelog blocks. Nothing prevents it from applying a different formating. Guidelines say nothing about SCM log, just about spec %changelog format Yes, they says nothing about scm log, but fedpkg clog had some assumptions, e.g. several lines, each starting with dash. There is no relation between those lines. While in SCM log, you expect something like brief description on first line and more elaborated description on others. I don't see how an rpm's %changelog block would not fit into this. Git commits log basically are free form texts + git header. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
using Koji
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I'm setting up Koji for a private build environment. I have followed the instructions at http://fedoraproject.org/wiki/Koji/ServerHowTo At the very bottom, it refers to http://fedoraproject.org/wiki/Koji/ServerBootstrap For instructions on importing packages and preparing Koji to run builds So I then referred to the ServerBootstrap Koji/wiki. It discusses tags, packages, groups. I've also beet to http://fedoraproject.org/wiki/Koji and the various pages off that. What it does NOT discuss is how to kick off a build, and where the files end up. I'm looking for a wiki / white paper / howto, on how to USE Koji to do builds. Anyone have any familiarity on this ? All the best, - -Greg - -- +-+ Please also check the log file at /dev/null for additional information. (from /var/log/Xorg.setup.log) | Greg Hosler ghos...@redhat.com| +-+ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+7gFAACgkQ404fl/0CV/S7+gCgpPvNLDlEk6XtXlrhCy0hTaJK 61kAoOdkwslxS+fcHOFgKSWK9Icg3BAR =BNaO -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Autoreconf race condition?
On 2012-05-22, Jan Synacek jsyna...@redhat.com wrote: I've run into a problem when I was trying to build tftp (master branch) package locally. Notice the execution of rm -f aconfig.h *after* make. That's how the Makefile is written. Unfortunatelly, it does not define all targets produced by each command. Also the make compares modification times of targets and prerequisites. And that's the reason, why make does not re-run configure (needed to generate aconfig.h removed before explicitly). You can see it by running: $ make -j5 -n --no-builtin-rules -d [...] No implicit rule found for `all'. Considering target file `MCONFIG'. Considering target file `configure'. Considering target file `configure.in'. Looking for an implicit rule for `configure.in'. No implicit rule found for `configure.in'. Finished prerequisites of target file `configure.in'. No need to remake target `configure.in'. Considering target file `aclocal.m4'. Looking for an implicit rule for `aclocal.m4'. No implicit rule found for `aclocal.m4'. Finished prerequisites of target file `aclocal.m4'. No need to remake target `aclocal.m4'. Finished prerequisites of target file `configure'. Prerequisite `configure.in' is older than target `configure'. Prerequisite `aclocal.m4' is older than target `configure'. No need to remake target `configure'. Considering target file `MCONFIG.in'. Looking for an implicit rule for `MCONFIG.in'. No implicit rule found for `MCONFIG.in'. Finished prerequisites of target file `MCONFIG.in'. No need to remake target `MCONFIG.in'. Considering target file `aconfig.h.in'. Pruning file `configure.in'. Pruning file `configure'. Pruning file `aclocal.m4'. Finished prerequisites of target file `aconfig.h.in'. Prerequisite `configure.in' is older than target `aconfig.h.in'. →Prerequisite `configure' is newer than target `aconfig.h.in'. Prerequisite `aclocal.m4' is older than target `aconfig.h.in'. Must remake target `aconfig.h.in'. [...] Which is dragged in by upstream `fix': I also noticed a rather weird comment in the Makefile: # Adding configure to the dependencies serializes this with running # autoconf, because there are apparently race conditions between # autoconf and autoheader. aconfig.h.in: configure.in configure aclocal.m4 rm -f aconfig.h.in aconfig.h autoheader Thus you get rm file removal without re-runing configure. The last bullet is they remove a file which has been already considered by make as up-to-date target (and call it side-effect). The problem goes away when I add sleep 1 between autoreconf and %configure in the spec file. Sound like an issue with modification times granularity. I would remove the configure prequisite from aconfig.h.in target (that's really fake dependency) or touch the files to get better ordering. -- Petr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hello, everyone
On Tue, May 22, 2012 at 02:38:40PM +0300, Назар Міштурак wrote: Hello, everyone, my name is Nazar. I have just made my first package review request(https://bugzilla.redhat.com/show_bug.cgi?id=823873). The package is The Powder Toy game which is very fun. So I want to see it in repo. It is not my project, original code is from http://powdertoy.co.uk/ Hello Nazar and welcome. It's better to make those links into plain files, not Google Docs, as this is easier for the reviewer. When I did manage to download the spec file, it looked sensible and simple so it shouldn't be a problem to find a reviewer to take this on. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
Dne 22.5.2012 13:52, Ralf Corsepius napsal(a): On 05/22/2012 01:42 PM, Vít Ondruch wrote: Dne 22.5.2012 13:22, Stanislav Ochotnicky napsal(a): I never use clog for creating changelog in spec so I don't know how it's supposed to work. I assume it stopped working right after cvs-fedpkg transition. Neither did I and I don't think it is even possible ;) Why? To me this only is a matter of how fedpkg formats extracted %changelog blocks. Nothing prevents it from applying a different formating. I should better say even possible ATM. Guidelines say nothing about SCM log, just about spec %changelog format Yes, they says nothing about scm log, but fedpkg clog had some assumptions, e.g. several lines, each starting with dash. There is no relation between those lines. While in SCM log, you expect something like brief description on first line and more elaborated description on others. I don't see how an rpm's %changelog block would not fit into this. Git commits log basically are free form texts + git header. Ralf If guidelines says that changelog is transformed into git commit message in some particular way, e.g. in a way that first line has some special meaning, then I am fine with that. But in current state, implying anything more is wrong. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Replacing libusb1 with libusbx
On Tue, 2012-05-22 at 13:44 +0200, Hans de Goede wrote: Hi All, I plan to replace libusb1 with libusbx, libusx is a fork of and a drop in replacement for libusb1. The libusbx fork was started by various libusb-1.0 developers (almost all of them *), because the official maintainer of libusb-1.0 refused to do any stable / tarbal releases for over 18 months and in general was very slow with merging new developments and fixes. I'm guessing you're talking about Daniel Drake. Why didn't you ask him if you could get commit access instead? I took over libfprint and fprintd releases, and got them moved to freedesktop.org last year. Cheers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20120522 changes
Compose started at Tue May 22 08:15:04 UTC 2012 Broken deps for x86_64 -- [389-admin] 389-admin-1.1.28-1.fc18.i686 requires libicuuc.so.48 389-admin-1.1.28-1.fc18.i686 requires libicui18n.so.48 389-admin-1.1.28-1.fc18.i686 requires libicudata.so.48 389-admin-1.1.28-1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicudata.so.48()(64bit) [389-adminutil] 389-adminutil-1.1.15-2.fc17.i686 requires libicuuc.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicui18n.so.48 389-adminutil-1.1.15-2.fc17.i686 requires libicudata.so.48 389-adminutil-1.1.15-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-adminutil-1.1.15-2.fc17.x86_64 requires libicudata.so.48()(64bit) [389-dsgw] 389-dsgw-1.1.9-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicudata.so.48()(64bit) [aeolus-all] aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-doc = 0:0.4.0-2.fc17 aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-daemons = 0:0.4.0-2.fc17 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [boost141] boost141-graph-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-graph-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-graph-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-graph-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) boost141-regex-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-regex-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-regex-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-regex-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [evolution-couchdb] evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-cal-1.2.so.15()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-book-1.2.so.13()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libecal-1.2.so.11()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [evolution-rss] 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libedataserverui-3.0.so.1()(64bit) 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [fawkes] fawkes-plugin-xmlrpc-0.4.2-10.fc18.x86_64 requires libxmlrpc_server++.so.7()(64bit) fawkes-plugin-xmlrpc-0.4.2-10.fc18.x86_64 requires libxmlrpc++.so.7()(64bit) [gambas2] gambas2-gb-pdf-2.23.1-10.fc18.x86_64 requires libpoppler.so.19()(64bit) [gambas3] gambas3-gb-pdf-3.1.1-2.fc18.x86_64 requires libpoppler.so.19()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python2-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 [ghc-warp] ghc-warp-0.4.6.3-3.fc18.i686 requires libHSwai-0.4.3-ghc7.4.1.so ghc-warp-0.4.6.3-3.fc18.i686 requires ghc(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-0.4.6.3-3.fc18.x86_64 requires libHSwai-0.4.3-ghc7.4.1.so()(64bit) ghc-warp-0.4.6.3-3.fc18.x86_64 requires ghc(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) ghc-warp-devel-0.4.6.3-3.fc18.i686 requires ghc-devel(wai-0.4.3-876d0504e17291cc228eed88f0ba35c9) ghc-warp-devel-0.4.6.3-3.fc18.x86_64 requires ghc-devel(wai-0.4.3-80e159ce6c5c5bb23a495fb1953addc6) [gnome-pilot] gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserverui-3.0.so.1()(64bit) gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [gnome-python2-desktop] gnome-python2-evolution-2.32.0-9.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [grub2] 1:grub2-2.0-0.29.beta5.fc18.x86_64 requires grub2-tools = 0:2.0-0.29.beta5.fc18 [inkscape] inkscape-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) inkscape-view-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) [koji] koji-hub-1.6.0-3.fc17.noarch requires mod_python koji-web-1.6.0-3.fc17.noarch requires mod_python [mapnik] mapnik-2.0.0-4.fc17.i686 requires libicuuc.so.48 mapnik-2.0.0-4.fc17.x86_64 requires
Re: [announce] yum: parallel downloading
On Mon, May 21, 2012 at 05:33:51AM -0500, Zdenek Pavlas wrote: The number of concurrent users is now lower because, well, each of them now completes a yum update in one third of the time. I think Glen's concerns were that the consumed resources (flow caches, TCP hash entries, sockets) may scale faster than the aggregated downloading speed. I am aware of this, and in most cases the downloader in urlgrabber will make just 1 concurrent connection to a mirror, because: 1) The Nth concurrent connection to the same host is assumed to be N times slower than 1st one, so we'll very likely not select the same mirror again. 2) maxconnections=1 in every metalink I've seen so far. This is a hard limit, we block until a download finishes and reuse one connection when the limit is maxed out. That's MirrorManager's doing. I don't have a box for mirror admins to tell MM otherwise - that they'd be happy with 1 connection. I suppose that could be added, default to 1. The reason for NOT banning 1 connections to the same host altogether is that (as John Reiser wrote) 2nd connection does help quite a lot when downloading many small files and just one mirror is available. I agree that using strictly 1 connection and HTTP pipelining would be even better, but we can't do that with libcurl. I'd be happy if yum/urlgrabber/libcurl finally used http keepalives. Last time I looked (and it has been a while), it didn't, so you always paid the TCP slow startup penalty for each package. -- Matt Domsch Technology Strategist Dell | Office of the CTO -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On Mon, May 21, 2012 at 3:08 PM, Kevin Kofler kevin.kof...@chello.at wrote: Greg Swift wrote: i'm not against cleaning up ifs related to end of life/support releases, but how far are you suggesting that go? All support for Fedora n should be dropped at Fedora n's end of life. which fits within the definition I stated. okay.. np I know that I've pulled plenty of rawhide packages for build on a RHEL box when necessary, and even if they don't always support EPEL sometimes they've had if switches in them that helped save me lots of time. We do not support this usecase. It is just not feasible to maintain so many conditionals in our packages. And Fedora version conditionals won't help you anyway if you're building for RHEL, you'd need RHEL version conditionals, which packages not supporting EPEL are very unlikely to contain. So I recently helped bring python-augeas into EPEL. Before that (for the last 2+ years) the spec file supported RHEL conditionals and many of the python-augeas users did local builds of the fedora package in their RHEL environment. Just because a package has not gotten an EPEL maintainer yet, doesn't mean the package doesn't support RHEL. The zabbix package is in EPEL. On RHEL 5 that means it is in the 1.4 branch due to the update policies. The Fedora package had gone through 1.6 and 1.8 releases before RHEL6 came out, none of which are in epel-testing. Myself and many others built our updated packages off the fedora package. I know there are several other packages that fall into this category. So what would happen in those scenarios? I realize that at some threshold maintaining too many conditionals can make a spec very difficult to work with, but for very simple and limited conditionals the same could be said of having multiple spec files. I'd really think that is more of a decision to be left to the maintainer of the package since packages can vary so drastically. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On Tue, May 22, 2012 at 09:07:56AM +0100, Richard W.M. Jones wrote: On Mon, May 21, 2012 at 10:13:41AM -0400, David Cantrell wrote: We automatically generate the spec file changelog block each time we make a new release of anaconda. Check out scripts/makebumpver in the anaconda git repo on git.fedorahosted.org. For us, the work is done in git.fedorahosted.org and we make .tar.bz2 releases of anaconda. The resulting archive and spec file are then checked in to pkgs.fedoraproject.org and built using fedpkg. Same basic workflow from when it was cvs as well. On this subject, it'd also be good to have an easier method to maintain packages as unpacked source + patches on top, which get turned as automatically as possible into spec files. I'm maintaining a few (RHEL, not Fedora) packages this way, and it sure makes handling patches easier. Also: https://rwmj.wordpress.com/2011/08/09/nice-rpm-git-patch-management-trick/#content Yeah, that is a nice workflow for package management in pkgs.fedoraproject.org for things that we [the Fedora project] are not also the upstream for. For the anaconda case, we're sort of unique in that we don't make releases and post them anywhere. The .tar.bz2 files end up in SRPMs only. So for us, we go to great lengths to avoid patches in pkgs.fedoraproject.org. If we have to make changes, that's a new release. The anaconda SRPM should only ever contain a spec file and tarball from us. Downstream consumers will probably put patches in there though. -- David Cantrell dcantr...@redhat.com Supervisor, Installer Engineering Team Red Hat, Inc. | Westford, MA | EST5EDT -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [announce] yum: parallel downloading
I'd be happy if yum/urlgrabber/libcurl finally used http keepalives. It does, indeed. Parallel downloader tries to use keepalives, too. (we cache and reuse the last idle process instead of closing it) Last time I looked (and it has been a while), it didn't, so you always paid the TCP slow startup penalty for each package. /me just checked with tcpflow that we really do. Please, contact me off-list if you can reproduce it. Thanks! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [announce] yum: parallel downloading
On Tue, 2012-05-22 at 11:24 +0930, Glen Turner wrote: On 21/05/2012, at 5:12 PM, Zdenek Pavlas wrote: Three connections limit is used when the above is not available (e.g. a baseurl setup with just one mirror). I don't mind lowering it to just two, as that should work good enough in most cases. Yes please. Two is better than three from the server's point of view. Do _any_ web browsers have a connection limit lower than 4? Given that and that we obey the max connections limit of the user and that in the metalink ... it seems pretty alarmist to say 3 is too many to a single server. Yum doesn't put in the HTTP header (say, appended to User-Agent) why it decided to use our mirror, so we have no count of the sites or users which manually set baseurl or give our mirror's name to anaconda. Mailing list postings often recommend this when people complain of slow or expensive downloads. You can open an RFE in bugzilla, and we could look at it if it's really useful information ... one problem though is that we combine all bareurls+mirrors, and move between them at the urlgrabber layer. So we couldn't easily just change something on the yum side. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 21 May 2012 09:50:53 -0700 Jesse Keating jkeat...@redhat.com wrote: On 05/21/2012 08:34 AM, Matej Cepl wrote: I give you that, but do you see any alternative which would in let's say five years replaced git in Fedora? Five years is a long time in computer industry, but OTOH five years ago (plus how long it has been since we actually switched to git) it was IMHO obvious our CVS is doomed. Also, our CVS trees are still available, and for the most part all the CVS log messages are still available within git. Any migration from git to something else should follow that same path and retain the information. cvs.fedoraproject.org has been shut down for quite awhile now. we do have the cvs trees archived but you need to file a ticket with infrastructure to get access. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+7u3MACgkQkSxm47BaWfdqYgCgtifyFuky1+ALMh8B1bctyMgq NDIAnAsUSJ2sqlMiKs5rXqRSjUTdzGEu =82fG -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Replacing libusb1 with libusbx
Hi, On 05/22/2012 02:55 PM, Bastien Nocera wrote: On Tue, 2012-05-22 at 13:44 +0200, Hans de Goede wrote: Hi All, I plan to replace libusb1 with libusbx, libusx is a fork of and a drop in replacement for libusb1. The libusbx fork was started by various libusb-1.0 developers (almost all of them *), because the official maintainer of libusb-1.0 refused to do any stable / tarbal releases for over 18 months and in general was very slow with merging new developments and fixes. I'm guessing you're talking about Daniel Drake. Why didn't you ask him if you could get commit access instead? I took over libfprint and fprintd releases, and got them moved to freedesktop.org last year. No, Daniel handed it over to Peter Stuge about 18 months ago (give or take), and that didn't work out to well. I (and others) have tried pretty much every everything to avoid having to fork, but to no result. Regards, Hans -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: changelog in spec file, was Re: Stop the git abuse
On 05/20/2012 09:49 PM, Matthew Miller wrote: On Sun, May 20, 2012 at 08:02:23PM -0400, Paul Wouters wrote: Agreed. changelog and version field conflicts are 90% of my cherry-pick conflicts. I would be in favour of no longer maintaining a changelog in the spec file As long as it gets put into the final RPM in the build process somehow. `rpm --changelog` is often very, very useful in the field. +1 It's great that CVS vulnerability numbers patched by each release are mentioned in the changelog. Tracking it is a common requirement in many environments, and rpm -q --changelog provides a very nice way to find out about it. In fact, is that a policy or just something nice that people do? if the latter, could we consider adopting it officially? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Stop the git abuse
On 05/22/2012 12:33 AM, Jan Kratochvil wrote: True, I agree now. It is just so slow (0m2.693s now, 0m4.222s with drop_caches=3) I expected it waits for network. I bet if you traced it, the majority of time is waiting for rpm to return queries about the spec file. -- jlk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Weekly ARM status meeting - Wed 2012/05/23
Good day all, This weeks Fedora ARM status meeting will take place tomorrow (Wednesday May 23rd) in #fedora-meeting-1 on Freenode. Times in various time zones (please let us know if these do not work): PDT: 1pm MDT: 2pm CDT: 3pm EDT: 4pm UTC: 8pm BST: 9pm CST: 10pm Current items on the agenda: 1) F17 build status - branching, updates, updates-testing - remaining problem packages 2) Rawhide status update - how do we look for F18? - problem packages 3) ARM Koji status update - Update on latest downtime 4) Your topic here If you have any other items you would like to discuss that are not mentioned, please feel free to send an email to the list or bring it up at the end of the meeting. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Kickstart packages --default parsing query
Hello: I posted this to the Kickstart list [1], but thought of checking it here in the interest of a faster turnaround time. I am trying to add a repository to an existing KS file. This is the script [2]. The script is doing its job for KS files which do not have a '--default' switch added to the %packages section. However, for a KS file which has a %packages --default section added, the parser does not read beyond it and hence creates a KS file which do not have any of the following packages specified in the KS file. To quickly verify the problem, I have added two KS files (basically the fedora-install-fedora.ks used to create Fedora installation DVDs) with one having the --default option, and the other not having it. I have commented out the actual repo addition code so that the problem can be reproduced easily. For example, with the default.ks file: $python ks_addrepo.py #version=DEVEL repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releaseverarch=$basearch --excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome repo --name=fedora-source --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releaseverarch=$basearch --excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome # Installation logging level logging --level=info %packages --default %end And with the nodefault.ks file: $python ks_addrepo.py #version=DEVEL repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releaseverarch=$basearch --excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome repo --name=fedora-source --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-source-$releaseverarch=$basearch --excludepkgs=kernel*debug*,kernel-kdump*,syslog-ng*,java-1.5.0-gcj-devel,astronomy-bookmarks,generic*,java-1.5.0-gcj-javadoc,btanks*,GConf2-dbus*,bluez-gnome # Installation logging level logging --level=info %packages @afrikaans-support @albanian-support @arabic-support @armenian-support @assamese-support @basque-support @belarusian-support @bengali-support @bhutanese-support @bosnian-support @brazilian-support @breton-support @british-support @bulgarian-support @burmese-support .. .. [1] https://www.redhat.com/archives/kickstart-list/2012-May/msg2.html [2] https://github.com/amitsaha/gsoc2012_fbs/blob/master/scripts/ks_addrepo.py Have I hit a bug or is it something which is known can be worked around? Thanks a lot in advance. Best, Amit -- http://echorand.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 17 Final Release Candidate 4 (RC4) Available Now!
As per the Fedora 17 schedule [1], Fedora 17 Final Release Candidate 4 (RC4) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5196 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Security Lab: https://fedoraproject.org/wiki/Test_Results:Current_Security_Lab_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], Desktop [4], and Security Lab [5] should pass in order to meet the Final Release Criteria [6]. Help is available on #fedora-qa on irc.freenode.net [7], or on the test list [8]. Create Fedora 17 Final release candidate (RC) - live and traditional https://fedorahosted.org/rel-eng/ticket/5196 Current Release Blocker page (Blockers and Nice-To-Have): https://fedoraproject.org/wiki/Current_Release_Blockers Fedora 17 Final Blocker tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752650 Fedora 17 Final Nice-To-Have tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752653 [1] http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/QA:Security_Lab_validation_testing [6] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria [7] irc://irc.freenode.net/fedora-qa [8] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Test-NoPlan-v0.0.6.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Test-NoPlan: 881e04a943faede5515eea2405d92cb8 Test-NoPlan-v0.0.6.tar.gz -- 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
[perl-Test-NoPlan] Import
commit 304f340d6f5d519af9b070b2cce5c2121c035fc4
Author: Petr Písař ppi...@redhat.com
Date: Tue May 22 08:48:03 2012 +0200
Import
.gitignore|1 +
perl-Test-NoPlan.spec | 55 +
sources |1 +
3 files changed, 57 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e69de29..289f922 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Test-NoPlan-v0.0.6.tar.gz
diff --git a/perl-Test-NoPlan.spec b/perl-Test-NoPlan.spec
new file mode 100644
index 000..13c20d4
--- /dev/null
+++ b/perl-Test-NoPlan.spec
@@ -0,0 +1,55 @@
+Name: perl-Test-NoPlan
+Version:0.0.6
+Release:1%{?dist}
+Summary:Check perl test files for no_plan
+License:GPL+ or Artistic
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/Test-NoPlan/
+Source0:
http://www.cpan.org/authors/id/D/DU/DUNCS/Test-NoPlan-v%{version}.tar.gz
+BuildArch: noarch
+BuildRequires: perl(Module::Build)
+# Run-time:
+BuildRequires: perl(base)
+BuildRequires: perl(Carp)
+BuildRequires: perl(Cwd)
+BuildRequires: perl(Exporter)
+BuildRequires: perl(File::Spec)
+BuildRequires: perl(Test::Builder::Module)
+BuildRequires: perl(version)
+# Tests:
+BuildRequires: perl(Test::More)
+# Optional tests:
+BuildRequires: perl(Test::Pod) = 1.22
+BuildRequires: perl(Test::Pod::Coverage) = 1.08
+BuildRequires: perl(Pod::Coverage) = 0.18
+Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+
+%description
+It is a good idea to ensure you have defined how many tests should be run
+within each test script - to catch cases where tests bomb out part way through
+so you know how many tests were not actually run. This module checks all your
+test plan files to ensure 'no_plan' is not used.
+
+%prep
+%setup -q -n Test-NoPlan-v%{version}
+
+%build
+%{__perl} Build.PL installdirs=vendor
+./Build
+
+%install
+./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
+find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+./Build test
+
+%files
+%doc AUTHORS Changes README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Thu Apr 26 2012 Petr Pisar ppi...@redhat.com 0.0.6-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..8dfb8ff 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+881e04a943faede5515eea2405d92cb8 Test-NoPlan-v0.0.6.tar.gz
--
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
File Test-Pod-No404s-0.01.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Test-Pod-No404s: 828d11730b2a133d3150d0eb83674424 Test-Pod-No404s-0.01.tar.gz -- 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
File Module-Find-0.11.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Module-Find: 420a0796a1fbdfd5704df754872db7e1 Module-Find-0.11.tar.gz -- 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
[perl-Module-Find] Update to 0.11
commit e2e59ed967f1ce4254143d9f33965fb4b07899da
Author: Paul Howarth p...@city-fan.org
Date: Tue May 22 10:09:42 2012 +0100
Update to 0.11
- New upstream release 0.11
- defined(@array) is deprecated under Perl 5.15.7 (CPAN RT#74251)
- Don't need to remove empty directories from buildroot
- Drop %defattr, redundant since rpm 4.4
.gitignore|2 +-
perl-Module-Find.spec | 12
sources |2 +-
3 files changed, 10 insertions(+), 6 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index c8ebb98..39f4781 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/Module-Find-0.10.tar.gz
+/Module-Find-[0-9.]*.tar.gz
diff --git a/perl-Module-Find.spec b/perl-Module-Find.spec
index 6eb8259..c09dfea 100644
--- a/perl-Module-Find.spec
+++ b/perl-Module-Find.spec
@@ -1,6 +1,6 @@
Name: perl-Module-Find
-Version: 0.10
-Release: 4%{?dist}
+Version: 0.11
+Release: 1%{?dist}
Summary: Find and use installed modules in a (sub)category
Group: Development/Libraries
License: GPL+ or Artistic
@@ -37,7 +37,6 @@ make %{?_smp_mflags}
rm -rf %{buildroot}
make pure_install DESTDIR=%{buildroot}
find %{buildroot} -type f -name .packlist -exec rm -f {} \;
-find %{buildroot} -depth -type d -exec rmdir {} \; 2/dev/null
%{_fixperms} %{buildroot}
%check
@@ -47,12 +46,17 @@ make test
rm -rf %{buildroot}
%files
-%defattr(-,root,root,-)
%doc Changes README examples/
%{perl_vendorlib}/Module/
%{_mandir}/man3/Module::Find.3pm*
%changelog
+* Tue May 22 2012 Paul Howarth p...@city-fan.org - 0.11-1
+- Update to 0.11:
+ - defined(@array) is deprecated under Perl 5.15.7 (CPAN RT#74251)
+- Don't need to remove empty directories from buildroot
+- Drop %%defattr, redundant since rpm 4.4
+
* Wed Jan 25 2012 Paul Howarth p...@city-fan.org - 0.10-4
- BR: perl(ExtUtils::MakeMaker), perl(File::Find), perl(File::Spec) and
perl(Pod::Perldoc)
diff --git a/sources b/sources
index 676eede..9cdd614 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bdc4687d0782157e9335f4dc31369d01 Module-Find-0.10.tar.gz
+420a0796a1fbdfd5704df754872db7e1 Module-Find-0.11.tar.gz
--
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
[perl-Module-Find] Created tag perl-Module-Find-0.11-1.fc18
The lightweight tag 'perl-Module-Find-0.11-1.fc18' was created pointing to: e2e59ed... Update to 0.11 -- 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
Broken dependencies: perl-Net-OpenSSH
perl-Net-OpenSSH has broken dependencies in the rawhide tree:
On x86_64:
perl-Net-OpenSSH-0.57-3.fc18.noarch requires
openssh-clients(%{__isa_name}-%{__isa_bits})
On i386:
perl-Net-OpenSSH-0.57-3.fc18.noarch requires
openssh-clients(%{__isa_name}-%{__isa_bits})
Please resolve this as soon as possible.
--
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
File Test-NoBreakpoints-0.15.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Test-NoBreakpoints: 2146644134903205d509fdb46e6fc8f3 Test-NoBreakpoints-0.15.tar.gz -- 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
[perl-Test-NoBreakpoints] Import
commit c2e432f268fd968148725c083d36ba20845bfa97
Author: Petr Písař ppi...@redhat.com
Date: Tue May 22 16:43:23 2012 +0200
Import
.gitignore |1 +
perl-Test-NoBreakpoints.spec | 52 ++
sources |1 +
3 files changed, 54 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e69de29..3746eee 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Test-NoBreakpoints-0.15.tar.gz
diff --git a/perl-Test-NoBreakpoints.spec b/perl-Test-NoBreakpoints.spec
new file mode 100644
index 000..cdf172b
--- /dev/null
+++ b/perl-Test-NoBreakpoints.spec
@@ -0,0 +1,52 @@
+Name: perl-Test-NoBreakpoints
+Version:0.15
+Release:1%{?dist}
+Summary:Test that files do not contain soft breakpoints
+License:GPL+ or Artistic
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/Test-NoBreakpoints/
+Source0:
http://www.cpan.org/authors/id/J/JF/JFITZ/Test-NoBreakpoints-%{version}.tar.gz
+BuildArch: noarch
+BuildRequires: perl(ExtUtils::MakeMaker)
+# Run-time:
+BuildRequires: perl(Exporter)
+BuildRequires: perl(File::Spec)
+BuildRequires: perl(Test::Builder)
+# Tests:
+BuildRequires: perl(lib)
+BuildRequires: perl(Test::Exception)
+BuildRequires: perl(Test::More) = 0.92
+BuildRequires: perl(Test::Tester) = 0.09
+BuildRequires: perl(Test::UseAllModules)
+# Optional tests:
+BuildRequires: perl(Test::NoWarnings)
+Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+
+%description
+Test::NoBreakpoints checks that files contain neither the string
+$DB::single = 1 nor $DB::signal = 1.
+
+%prep
+%setup -q -n Test-NoBreakpoints-%{version}
+
+%build
+%{__perl} Makefile.PL INSTALLDIRS=vendor
+make %{?_smp_mflags}
+
+%install
+make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
+find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+make test
+
+%files
+%doc Changes LICENSE README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Thu Apr 26 2012 Petr Pisar ppi...@redhat.com 0.15-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..f8c24ab 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+2146644134903205d509fdb46e6fc8f3 Test-NoBreakpoints-0.15.tar.gz
--
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
[perl-Test-NoBreakpoints] Utilize Test::Pod when building
commit 776a17f7fb4a6c209f0bead834dc9eb3086f7420
Author: Petr Písař ppi...@redhat.com
Date: Tue May 22 16:59:16 2012 +0200
Utilize Test::Pod when building
perl-Test-NoBreakpoints.spec |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
---
diff --git a/perl-Test-NoBreakpoints.spec b/perl-Test-NoBreakpoints.spec
index cdf172b..550c587 100644
--- a/perl-Test-NoBreakpoints.spec
+++ b/perl-Test-NoBreakpoints.spec
@@ -1,6 +1,6 @@
Name: perl-Test-NoBreakpoints
Version:0.15
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Test that files do not contain soft breakpoints
License:GPL+ or Artistic
Group: Development/Libraries
@@ -19,6 +19,7 @@ BuildRequires: perl(Test::More) = 0.92
BuildRequires: perl(Test::Tester) = 0.09
BuildRequires: perl(Test::UseAllModules)
# Optional tests:
+BuildRequires: perl(Test::Pod) = 1.00
BuildRequires: perl(Test::NoWarnings)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -48,5 +49,8 @@ make test
%{_mandir}/man3/*
%changelog
+* Tue May 22 2012 Petr Pisar ppi...@redhat.com - 0.15-2
+- Utilize Test::Pod when building
+
* Thu Apr 26 2012 Petr Pisar ppi...@redhat.com 0.15-1
- Specfile autogenerated by cpanspec 1.78.
--
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
[perl-Getopt-Long-Descriptive/el6] Version bump
commit f6a1374463e788d5b50858ece19e66b4c8cf5aa5
Author: Mark Chappell mchap...@redhat.com
Date: Tue May 22 20:28:44 2012 +0200
Version bump
perl-Getopt-Long-Descriptive.spec |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/perl-Getopt-Long-Descriptive.spec
b/perl-Getopt-Long-Descriptive.spec
index de0e95c..990474c 100644
--- a/perl-Getopt-Long-Descriptive.spec
+++ b/perl-Getopt-Long-Descriptive.spec
@@ -1,7 +1,7 @@
Name: perl-Getopt-Long-Descriptive
Summary:Getopt::Long with usage text
Version:0.084
-Release:1%{?dist}
+Release:3%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/R/RJ/RJBS/Getopt-Long-Descriptive-%{version}.tar.gz
@@ -60,6 +60,9 @@ rm -rf %{buildroot}
%{_mandir}/man3/*
%changelog
+* Tue May 22 2012 Mark Chappell trem...@tremble.org.uk 0.084-3
+- Version bump to ensure we're built from the correct branch
+
* Sat Feb 27 2010 Chris Weyl cw...@alumni.drew.edu 0.084-1
- update by Fedora::App::MaintainerTools 0.004
- PERL_INSTALL_ROOT = DESTDIR
--
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
File rt-3.8.12.tar.gz uploaded to lookaside cache by corsepiu
A file has been added to the lookaside cache for rt3: df16396141797daf2047f676a82260e6 rt-3.8.12.tar.gz -- 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
[rt3] Upstream update.
commit 878d7300be0018655a2f866530cb2bdaffb35dad
Author: Ralf Corsépius corse...@fedoraproject.org
Date: Tue May 22 21:33:12 2012 +0200
Upstream update.
- Address various CVEs (BZ 824082).
.gitignore |2 +-
rt3.spec | 16 ++--
sources|2 +-
3 files changed, 12 insertions(+), 8 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 74e7dd0..3dd4994 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/rt-3.8.11.tar.gz
+/rt-3.8.12.tar.gz
diff --git a/rt3.spec b/rt3.spec
index 03a3ad3..1e0f65d 100644
--- a/rt3.spec
+++ b/rt3.spec
@@ -40,8 +40,8 @@
%global RT3_LOCALSTATEDIR %{_localstatedir}/lib/rt3
Name: rt3
-Version: 3.8.11
-Release: 7%{?dist}
+Version: 3.8.12
+Release: 1%{?dist}
Summary: Request tracker 3
Group: Applications/Internet
@@ -53,10 +53,10 @@ Source3:rt3.conf.in
Source4: README.fedora.in
Source5: rt3.logrotate.in
-Patch0:rt-%{version}-config.diff
-Patch1:rt-%{version}-shebang.diff
-Patch2:rt-%{version}-Makefile.diff
-Patch3:rt-%{version}-test-dependencies.diff
+Patch0:rt-3.8.11-config.diff
+Patch1:rt-3.8.11-shebang.diff
+Patch2:rt-3.8.11-Makefile.diff
+Patch3:rt-3.8.11-test-dependencies.diff
BuildArch: noarch
@@ -495,6 +495,10 @@ fi
%endif
%changelog
+* Tue May 22 2012 Ralf Corsépius corse...@fedoraproject.org - 3.8.12-1
+- Upstream update.
+- Address various CVEs (BZ 824082).
+
* Tue Feb 02 2012 Ralf Corsépius corse...@fedoraproject.org - 3.8.11-7
- Fix shebangs.
- Make testsuite files executable (enables rpm's perl module dep tracking).
diff --git a/sources b/sources
index 92df308..5e38200 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5d7a86e0a5d79de014716cf8f9301ab9 rt-3.8.11.tar.gz
+df16396141797daf2047f676a82260e6 rt-3.8.12.tar.gz
--
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
[rt3/f17] Upstream update.
Summary of changes: 878d730... Upstream update. (*) (*) This commit already existed in another branch; no separate mail sent -- 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
[rt3/f16] (4 commits) ...Upstream update.
Summary of changes: e3c498c... Fix typo. (*) 9e46a6d... Fix shebangs. (*) 24e4097... New. (*) 878d730... Upstream update. (*) (*) This commit already existed in another branch; no separate mail sent -- 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
[rt3/f15] (4 commits) ...Upstream update.
Summary of changes: e3c498c... Fix typo. (*) 9e46a6d... Fix shebangs. (*) 24e4097... New. (*) 878d730... Upstream update. (*) (*) This commit already existed in another branch; no separate mail sent -- 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
[389-devel] Please review: Ticket #382 - DS Shuts down intermittently
https://fedorahosted.org/389/ticket/382 https://fedorahosted.org/389/attachment/ticket/382/0001-Ticket-382-DS-Shuts-down-intermittently.patch -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
