Re: Builder update
On 08/28/2013 06:35 PM, Kevin Fenzi wrote: On Wed, 28 Aug 2013 18:22:57 +0300 Panu Matilainen pmati...@laiskiainen.org wrote: Hum... a question, or perhaps more like two: Are you planning to move the remaining RHEL-6 builders to Fedora too, and if so, is this (builders running on Fedora ~latest) going to be a permament arrangement? Quite possibly. Left is a pair of buildhw (hardware builders), buildppc (power7 boxes, mostly for epel6), and bkernel (kernel and secureboot builders). We are going to look and see if those can be moved over too without pain. yeah, I think the plan is to do this moving forward (Fedora latest that is). Awesome. Just awesome. If the answer to both is yes then this is wonderful news for the package-management department. It's good for infrastructure as well, in that we don't need to carry any 'special' rpm or anything if we need to change formats or the like. From package-management POV this makes it *possible* to meaningfully introduce certain types of new features. The builders being stuck on several years old, practically frozen version of rpm (and yum etc) has been one of, or perhaps *the* biggest roadblock and demotivating aspect in rpm development: 1) implement installation-related feature X in upstream git 2) wait for it to make its way next stable upstream release 3) wait for the upstream release to make its way into Fedora 4) grow many more gray hairs while waiting for next major RHEL version 5) wait a bit more for the builders to move to the new RHEL 6) wait for the feature to be sanctioned for use in Fedora by FPC 7) wait for packagers to start adopting the new thing ... 8) realize there's a flaw in X, hindering or even preventing its real-world usage 9) pray and beg for approval to fix it in RHEL 10) wait at least half a year for the next RHEL update to come out 11) go back to 7), rinse and repeat as necessary For a practical example of the timescale of this process as things have been so far: opt-in install-time macro-expansion of scriptlets was implemented upstream in March 2010 and has been in Fedora since F15. Yet this relatively trivial thing *still* cannot be actually used in any version of Fedora, and nobody knows (or would not be allowed to say) when RHEL+1 comes out, so after 3.5 years from implementing the stupid thing, we're only at step 4) with an unknown (but in any case lengthy) time before being anywhere near 7). So if people are still wondering why rpm moves at such glacial pace... Having builders run Fedora latest-stable cuts the time from implementation to being deployable (or at least real-world testable) in Fedora literally by *years*, and the turn-around for steps 8-11 from months to days. Let me say AWESOME one more time :) Of course it does mean we could run into breakage if there's breakage in Fedora land, but thats good to know and fix too. Yes, dogfooding on the builders can IMO only be a good thing for overall stability of Fedora, even if it might initially cause some extra hickups. Breaking the builders a couple of times and getting scolded for that ought to make people think a bit more about pushing potentially destabilizing updates :) - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Announcing Design Software
Design software is a special interest group intended to package and maintain software for design team. It was born to fill the need to include design related tools unavailable in Fedora repository. The following mission is to - Maintain the Design group in the comps.xml, - Promote more the Design Suite, - Actively maintain design-related packages, - Tracking bugs and fix them when the main maintainer is inactive for a certain periods Design Software has FAS account named design-sw (Design Software in short). The mailing list is design-de...@lists.fedoraproject.org where the activity on maintaining packages occur. The bugzilla alias is DESIGN-SW for tracking review related to design packages and cc'ed to the design staff. The wiki is located to http://fedoraproject.org/wiki/SIGs/Design_Software with currently who active members. Members can be design team or packagers. At long term, Design Software will actively maintain the Design Suite based on latest version on Gnome Desktop, participate reporting some issue of development software packaged by some design team members and be close with upstream as possible. A thank you for Design Team for helping making this Special Interest Group a reality and the Infrastructure team for setting up the FAS account and the mailing list. Comments and feedback are welcome. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Thu, Aug 29, 2013 at 07:56:28AM +0200, Till Maas wrote: On Thu, Aug 29, 2013 at 12:32:19AM +0100, Peter Robinson wrote: python-quantumclient orphan, jruzicka, vaneldik, pbrady, apevec, gkotton, markmc, rkukura Depending on: python-quantumclient openstack-quantum (maintained by: rkukura, itamarjp, otherwiseguy, mmagr, josecastroleon, vaneldik, pbrady, rackerjoe, apevec, chrisw, gkotton, markmc) python-quantum-2013.2-0.3.b1.fc20.noarch requires python-quantumclient = 2:2.2.1-4.fc20 All of those have been renamed upstream and have been replaced with packages in Fedora with the new name 's/quantum/neutron' so openstack-quantum, python-quantum and python-quantumclient should all just be retired. python-quantumclient openstack-quantum are now blocked in f20+, but I did not find a python-quantum package. I now see that it is a subpackage of openstack-quantum, which I also retired now. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: bisect on fedora kernels
On 29 August 2013 01:53, Josh Boyer jwbo...@fedoraproject.org wrote: On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmal...@gmail.com wrote: Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread). Er... it doesn't? Where did you try to get it from, and how did it fail? Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summary Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations. -- imalone http://ibmalone.blogspot.co.uk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphaning of freemind and all my remaining Java packages
On Sat, Aug 24, 2013 at 11:43 AM, Johannes Lips johannes.l...@gmail.comwrote: Hi all, I finally came to the conclusion, that I no longer want to invest time and effort in keeping all my Java packages in good shape. I don't have the time anymore to unbundle all the bundled libraries and keep a dozen downstream patches to make it work. freemind is close to a 1.0.0 release and I provided packages for that already in a small side repo [1]. There are also some review requests for additional libraries [2],[3]. So I will orphan the packages next week and will block them if no one applies for taking them over. - freemind - SimplyHTML - jansi - jansi-native - jarbundler - jibx - xpp3 Ok, so I am going to orphan the remaining packages: - SimplyHTML - freemind Perhaps someone is willing to pick them up. - Johannes I hope someone will take good care of them. Johannes [1] http://repos.fedorapeople.org/**repos/hannes/freemind-1.0.0/http://repos.fedorapeople.org/repos/hannes/freemind-1.0.0/ [2] https://bugzilla.redhat.com/**show_bug.cgi?id=923960https://bugzilla.redhat.com/show_bug.cgi?id=923960 [3] https://bugzilla.redhat.com/**show_bug.cgi?id=923959https://bugzilla.redhat.com/show_bug.cgi?id=923959 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: bisect on fedora kernels
On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote: On 29 August 2013 01:53, Josh Boyer jwbo...@fedoraproject.org wrote: On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmal...@gmail.com wrote: Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread). Er... it doesn't? Where did you try to get it from, and how did it fail? Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summary Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations. -- imalone http://ibmalone.blogspot.co.uk Hmm. I've read article from jwb and I see koji-bisect should good couple with my proposal [0], but I can't find sources koji-bisect.. [0]https://lists.fedoraproject.org/pipermail/devel/2013-August/188461.html -- Igor Gnatenko Fedora release 19 (Schrödinger’s Cat) Linux 3.10.7-200.fc19.x86_64 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
By mere curiosity, why didn't we follow the usual renaming process (and avoid losing the previous history in git) ? It was just an upstream rename due to a trademark issue. H. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
Quoting Dave Johansen (2013-08-28 21:58:38)
On Wed, Aug 28, 2013 at 9:13 AM, Remi Collet fed...@famillecollet.com wrote:
Le 28/08/2013 18:09, Dave Johansen a écrit :
I'm trying to make a spec file that uses the devtoolset in RHEL 5/6 (
rhn.redhat.com/errata/RHEA-2013-0175.html ) but I haven't been able
to figure out how to enable devtoolset in the spec file. If I run 'scl
enable devtoolset-1.1 bash' before doing rpmbuild it works, but how do
I run a command like that in the spec file?
In %build:
. /opt/rh/devtoolset-or-sclname/enable
The enable script wasn't executable, but sourcing it worked like a charm.
Technically, yes...the above works but doesn't ensure it will keep working. I
believe normally this convoluted way is proper way to execute some commands in
an SCL within spec file:
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
This way you can use the same spec file as SCL and out of SCL.
--
Stanislav Ochotnicky sochotni...@redhat.com
Software Engineer - Developer Experience
PGP: 7B087241
Red Hat Inc. http://cz.redhat.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Dear Fedora Packagers!
Dne 28.8.2013 16:27, Miloslav Trmač napsal(a): On Wed, Aug 28, 2013 at 3:15 PM, Michael Schwendt mschwe...@gmail.com wrote: Thanks for your interest. It is a reoccuring problem that both the rename request submitter *and* the reviewer get the Obsoletes tags wrong. Perhaps the guidelines should be more clear, then. (No, I don't have a specific proposal.) Mirek I always wondered, why there is no tool which would do that automatically ... (not that I'm going to write one ;) Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
Dne 29.8.2013 08:05, Panu Matilainen napsal(a): For a practical example of the timescale of this process as things have been so far: opt-in install-time macro-expansion of scriptlets was implemented upstream in March 2010 and has been in Fedora since F15. Yet this relatively trivial thing *still* cannot be actually used in any version of Fedora, and nobody knows (or would not be allowed to say) when RHEL+1 comes out, so after 3.5 years from implementing the stupid thing, we're only at step 4) with an unknown (but in any case lengthy) time before being anywhere near 7). Reading such great news, Panu, would you mind to prepare list of features we could start using in next Fedoras? Thanks Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Dear Fedora Packagers!
On Wed, 28 Aug 2013 09:04:23 -0700, Toshio Kuratomi wrote:
I've highlighted the %{?dist} tag issue. see if this is better now:
https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages
Any change like that could help. :) Thanks for the effort!
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
Dne 29.8.2013 10:19, Stanislav Ochotnicky napsal(a):
Quoting Dave Johansen (2013-08-28 21:58:38)
On Wed, Aug 28, 2013 at 9:13 AM, Remi Collet fed...@famillecollet.com wrote:
Le 28/08/2013 18:09, Dave Johansen a écrit :
I'm trying to make a spec file that uses the devtoolset in RHEL 5/6 (
rhn.redhat.com/errata/RHEA-2013-0175.html ) but I haven't been able
to figure out how to enable devtoolset in the spec file. If I run 'scl
enable devtoolset-1.1 bash' before doing rpmbuild it works, but how do
I run a command like that in the spec file?
In %build:
. /opt/rh/devtoolset-or-sclname/enable
The enable script wasn't executable, but sourcing it worked like a charm.
Technically, yes...the above works but doesn't ensure it will keep working. I
believe normally this convoluted way is proper way to execute some commands in
an SCL within spec file:
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
This way you can use the same spec file as SCL and out of SCL.
Or using heredoc sytax:
%{?scl:scl enable %scl - \EOF}
# this is a shell
command 1
command 2
...
%{?scl:EOF}
Vít
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Schedule for Thursday's FPC Meeting (2013-08-29 16:00 UTC)
Le Jeu 29 août 2013 01:11, Toshio Kuratomi a écrit : #topic #336 Please clarify the General Naming Guidelines for packages .fpc 336 https://fedorahosted.org/fpc/ticket/336 BTW Fedora font packages allow lowercase naming only. The notion that tarball naming reflects in any accurate way upstream preferences is as weird as it comes. Are we supposed to rename packages every time upstream slightly changes its tarball naming? (as every project that did not automate its release process commonly does?) Moreover, our naming guidelines already mandate scores of adjustments to try to make some sort of coherent repository of upstreams with wildly different whims. Allowing mixed casing just sows confusion and induces new packager mistakes (that they sorely regret once they can not change the naming easily anymore). Finally, if you want to strictly follow upstream choices please allow unicode and not just base latin in package names. Arguing about case when one can not even use upstream letters is a joke. Regards, -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Thu, 29 Aug 2013 09:57:18 +0200, 80 wrote: By mere curiosity, why didn't we follow the usual renaming process (and avoid losing the previous history in git) ? It was just an upstream rename due to a trademark issue. The rename process may have been followed, but the renamed packages have not been reviewed painstakingly. At least 15 subpackages had not been replaced ( https://bugzilla.redhat.com/1001603 ). And retiring packages is too difficult in Fedora. The process is complex or not known by all packagers: http://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Some retire only in pkgdb (some create orphans instead, which somebody else picks up without checking history), others only create the dead.package file. Renaming is particularly more complicated, if another packager needs to take action and retire something properly prior to another (mass-)rebuild. I've opened tickets about the undeads below, but I'm not sure there will be a response to all of them. Basically, all of them should be blocked in koji for F20 and newer *and* retired in pkgdb, and the undeads are not marked dead in git yet. Dead and all builds obsoleted: -- classads ibus-table-array30 openstack-quantum pdfbook python-cryptsetup python-quantumclient Undead and all builds obsoleted: drupal6-drush jaxen-bootstrap joystick kdirstat latexdiff nss-myhostname pdfjam ps2eps seahorse-plugins zeitgeist-datahub -- http://mschwendt.fedorapeople.org/obscheck-remote.py -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
On 08/29/2013 10:19 AM, Stanislav Ochotnicky wrote:
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
Just one command with this syntax. If you need more command, you have to use
heredoc as Vít said in this thread.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphaning of freemind and all my remaining Java packages
Quoting Johannes Lips (2013-08-29 09:00:28) On Sat, Aug 24, 2013 at 11:43 AM, Johannes Lips johannes.l...@gmail.comwrote: Hi all, I finally came to the conclusion, that I no longer want to invest time and effort in keeping all my Java packages in good shape. I don't have the time anymore to unbundle all the bundled libraries and keep a dozen downstream patches to make it work. freemind is close to a 1.0.0 release and I provided packages for that already in a small side repo [1]. There are also some review requests for additional libraries [2],[3]. So I will orphan the packages next week and will block them if no one applies for taking them over. - freemind - SimplyHTML - jansi - jansi-native - jarbundler - jibx - xpp3 Ok, so I am going to orphan the remaining packages: - SimplyHTML - freemind Perhaps someone is willing to pick them up. I don't have that much time to spend on them at the moment, but I took freemind and simplyHTML. Co-maintainers welcome -- Stanislav Ochotnicky sochotni...@redhat.com Software Engineer - Developer Experience PGP: 7B087241 Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
On 08/29/2013 11:47 AM, Vít Ondruch wrote: Dne 29.8.2013 08:05, Panu Matilainen napsal(a): For a practical example of the timescale of this process as things have been so far: opt-in install-time macro-expansion of scriptlets was implemented upstream in March 2010 and has been in Fedora since F15. Yet this relatively trivial thing *still* cannot be actually used in any version of Fedora, and nobody knows (or would not be allowed to say) when RHEL+1 comes out, so after 3.5 years from implementing the stupid thing, we're only at step 4) with an unknown (but in any case lengthy) time before being anywhere near 7). Reading such great news, Panu, would you mind to prepare list of features we could start using in next Fedoras? All in good time... First we need to see this change actually go through all the way and stick. Secondly there isn't a whole lot of such features right now, as efforts have been concentrated on improving the existing, usable features rather than implementing new things because of the insane deployment process. Finally, the use of such features within Fedora needs to be sanctioned by FPC and that's by no means guaranteed to happen (eg tilde-versioning was explicitly banned although it actually could already be used). - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [RFC] Easiest making kernel rpms from upstream git
On 08/28/2013 08:31 PM, Kashyap Chamarthy wrote: On 08/28/2013 07:23 PM, Igor Gnatenko wrote: Today I've wrote article w/ many notes about bisecting kernel [0], but I've used make bzImage, make install and the same commands bypassing RPM and I have IMHO good idea to write utility, that will be build rpm w/o/ Fedora patches, changelogs, etc. simple rpms w/ one command. We will use utilityname `git rev-parse HEAD` f19 instead of make bzImage make modules and yum install ./rpms/*.rpm instead of make install make modules_install. This software should increase the effectiveness, simplify the build test kernels, simplify to work w/ installed kernels (e.g. remove). Also we can easy provide rpms to bugreport for testing regressions, etc. Incidentally, just today, I was building upstream kernels manually (for testing some KVM specific things). I don't build Kernels often. After some trial and error, I ended up with this sequence: $ make -j6 make bzImage make modules $ make modules_install make install Couple of times Dracut failed to generate correct initramfs, resulting in froze. With a hint from Haralad Hoyer on IRC, I generated the initramfs manually (usually, using the host initrd should be sufficient): $ dracut /boot/initramfs-3.11.0-rc1+.img 3.11.0-rc1+ $ depmod -a That should be: $ depmod -a $ dracut /boot/initramfs-3.11.0-rc1+.img 3.11.0-rc1+ I see alike software at bubuntu wiki [1]. Would anyone besides me find this useful enough for me to keep working on it? Sure, I can certainly be a user here :-) . Note to self: Still have to debug/bisect an offending Kernel commit which is causing some KVM unit test failures. [0]https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection [1]https://wiki.ubuntu.com/Kernel/KernelBisection#Build_Upstream_Test_Kernel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Wed, Aug 28, 2013 at 10:53:53PM +0200, Till Maas wrote: Package(co)maintainers === directfb orphan, kwizart tslib orphan These seem to be retired by accident: https://lists.fedoraproject.org/pipermail/devel/2013-June/183702.html Nicolas, can you please comment on this? Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
On Thu, Aug 29, 2013 at 2:17 AM, Miroslav Suchý msu...@redhat.com wrote:
On 08/29/2013 10:19 AM, Stanislav Ochotnicky wrote:
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
Just one command with this syntax. If you need more command, you have to
use heredoc as Vít said in this thread.
So does that mean that this is the correct statement to put in the .spec
file?
%{?scl:scl enable %{scl} }
source /opt/rh/devtoolset-1.1/enable
%{?scl:}
What is the %{?scl} macro doing? And am I using it correctly in the above?
Thanks,
Dave
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Thu, Aug 29, 2013 at 11:09:12AM +0200, Michael Schwendt wrote: And retiring packages is too difficult in Fedora. The process is complex or not known by all packagers: http://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Some retire only in pkgdb (some create orphans instead, which somebody else picks up without checking history), others only create the dead.package file. Renaming is particularly more complicated, if another packager needs to take action and retire something properly prior to another (mass-)rebuild. It recently became easier, because fedpkg retire takes care of the most important steps since recently. I've opened tickets about the undeads below, but I'm not sure there will be a response to all of them. Basically, all of them should be blocked in koji for F20 and newer *and* retired in pkgdb, and the undeads are not marked dead in git yet. I guess you won't get responses to packages that are orphaned, because then the bug report is assigned to the orphan user. Dead and all builds obsoleted: -- classads ibus-table-array30 openstack-quantum pdfbook python-cryptsetup python-quantumclient These are now all blocked (some of them were already). You might want to use the koji repos directly to get more up-to-date results: http://kojipkgs.fedoraproject.org/mash/rawhide/i386/os Undead and all builds obsoleted: drupal6-drush jaxen-bootstrap joystick kdirstat latexdiff nss-myhostname pdfjam ps2eps seahorse-plugins zeitgeist-datahub If nobody objects, I can take care of above packages as well and retire them properly. Can you maybe tweak your script to also show which package obsoletes the package? This would make it easier to create a meaningful dead.package file. Here is some more detailed information about the packages, created with http://till.fedorapeople.org/tmp/pkginfo.py - you mind find some code in there helpful. === drupal6-drush: Drush is a command line shell and scripting interface for Drupal === Tags: None Branch: devel: Owner: afsilva (asrob, siwinski) Status: 3 (Approved) (2012-03-22 14:19:47.169709+00:00) Critpath: False Dead: Branch: f20: Owner: afsilva (siwinski, asrob) Status: 3 (Approved) (2013-08-20 20:14:10.217109+00:00) Critpath: False Dead: Branch: f19: Owner: afsilva (asrob, siwinski) Status: 3 (Approved) (2013-03-12 02:04:59.645238+00:00) Critpath: False Dead: === jaxen-bootstrap: A convenience package for build of dom4j === Tags: None Branch: devel: Owner: s4504kr () Status: 3 (Approved) (2011-12-01 16:09:36.313808+00:00) Critpath: False Dead: Branch: f20: Owner: s4504kr () Status: 3 (Approved) (2013-08-20 20:14:10.217109+00:00) Critpath: False Dead: Branch: f19: Owner: s4504kr () Status: 3 (Approved) (2013-03-12 02:23:38.768624+00:00) Critpath: False Dead: === joystick: Utilities for configuring most popular joysticks. === Tags: None Branch: devel: Owner: orphan (karsten) Status: 20 (Deprecated) (2013-01-15 17:23:50.239890+00:00) Critpath: False Dead: Branch: f20: Owner: orphan (karsten) Status: 20 (Deprecated) (2013-08-20 20:14:10.217109+00:00) Critpath: False Dead: Branch: f19: Owner: orphan (karsten) Status: 20 (Deprecated) (2013-03-12 02:35:26.583016+00:00) Critpath: False Dead: === kdirstat: Graphical Directory Statistics for Used Disk Space === Tags: None Branch: devel: Owner: chitlesh () Status: 3 (Approved) (2008-07-22 17:12:54.972471+00:00) Critpath: False Dead: Branch: f20: Owner: chitlesh () Status: 3 (Approved) (2013-08-20 20:31:55.339085+00:00) Critpath: False Dead: Branch: f19: Owner: chitlesh () Status: 3 (Approved) (2013-03-12 02:35:26.583016+00:00) Critpath: False Dead: === latexdiff: Determine and mark up significant differences between latex files === Tags: None Branch: devel: Owner: danken () Status: 3 (Approved) (2009-01-13 20:36:55.000710+00:00) Critpath: False Dead: Branch: f20: Owner: danken () Status: 3 (Approved) (2013-08-20 20:31:55.339085+00:00) Critpath: False Dead: Branch: f19: Owner: danken () Status: 3 (Approved) (2013-03-12 02:35:26.583016+00:00) Critpath: False Dead: === nss-myhostname: glibc plugin for local system host name resolution === Tags: None Branch: devel: Owner: lennart () Status: 3 (Approved) (2009-05-10 19:16:52.484515+00:00) Critpath: True Dead: Branch: f20: Owner: lennart () Status: 3 (Approved) (2013-08-20 20:31:55.339085+00:00) Critpath: False Dead: Branch: f19: Owner: lennart () Status: 3 (Approved) (2013-03-12 02:55:37.326894+00:00) Critpath: False Dead: === pdfjam: Utilities for join, rotate and align PDFs === Tags: None Branch: devel: Owner: salimma () Status: 3 (Approved)
[perl-XML-LibXML/f18] Rebuilt with newer libxml2
commit a304e69913df90663d87b3c3474d0d346ec8ac45
Author: Jitka Plesnikova jples...@redhat.com
Date: Thu Aug 29 12:52:54 2013 +0200
Rebuilt with newer libxml2
perl-XML-LibXML.spec |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/perl-XML-LibXML.spec b/perl-XML-LibXML.spec
index 06db05d..2537455 100644
--- a/perl-XML-LibXML.spec
+++ b/perl-XML-LibXML.spec
@@ -4,7 +4,7 @@ Name: perl-XML-LibXML
# it might not be needed anymore
# this module is maintained, the other is not
Version:2.0004
-Release:1%{?dist}
+Release:2%{?dist}
Epoch: 1
Summary:Perl interface to the libxml2 library
@@ -98,6 +98,9 @@ fi
%{_mandir}/man3/*.3*
%changelog
+* Thu Aug 29 2013 Jitka Plesnikova jples...@redhat.com - 1:2.0004-2
+- Rebuilt with newer libxml2
+
* Thu Aug 09 2012 Petr Šabata con...@redhat.com - 1:2.0004-1
- 2.0004 bump
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Running a command in spec file?
On 08/29/2013 12:04 PM, Dave Johansen wrote:
So does that mean that this is the correct statement to put in the .spec file?
%{?scl:scl enable %{scl} }
source /opt/rh/devtoolset-1.1/enable
%{?scl:}
What is the %{?scl} macro doing? And am I using it correctly in the above?
This scriplet:
%{?scl:scl enable %{scl} }
command 1
%{?scl:}
basicaly expand to:
%if 0%{?scl}
scl enable command 1
%endif
Therefore your scriplet:
%{?scl:scl enable %{scl} }
source /opt/rh/devtoolset-1.1/enable
%{?scl:}
would expand to:
%if 0%{?scl}
scl enable source /opt/rh/devtoolset-1.1/enable
%endif
which does not have sense.
I see that you want to enable SCL and from that moment you want to have
collection enabled.
This is not recommended (and therefore there is no such tool to do that).
You must enable collection for each specific command. Or block of commands by
heredoc syntax.
For operating on command line, you can do:
scl enable devtoolset-1.1 bash
which will open you shell where collection is enabled until you exit. But for spec file, please enable collection for
each command/block.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
Dne 29.8.2013 11:17, Miroslav Suchý napsal(a):
On 08/29/2013 10:19 AM, Stanislav Ochotnicky wrote:
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
Just one command with this syntax. If you need more command, you have
to use heredoc as Vít said in this thread.
Actually the syntax is correct. However, one advantage of heredoc is
that you can use quotes freely, e.g. this does *not* work (unless you
escape the double quotes):
%{?scl:scl enable %{scl} }
# this is a shell
command 1
command 2
...
%{?scl:}
while this is perfectly OK:
%{?scl:scl enable %scl - \EOF}
# this is a shell
command 1
command 2
...
%{?scl:EOF}
In other words, heredoc makes the conversion from regular .spec to SCL
.spec a bit easier in some cases.
Vít
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: bisect on fedora kernels
On Thu, Aug 29, 2013 at 3:32 AM, Igor Gnatenko i.gnatenko.br...@gmail.com wrote: On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote: On 29 August 2013 01:53, Josh Boyer jwbo...@fedoraproject.org wrote: On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmal...@gmail.com wrote: Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread). Er... it doesn't? Where did you try to get it from, and how did it fail? Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summary Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations. Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 903609] perl-XML-LibXSLT-1.80 is available
https://bugzilla.redhat.com/show_bug.cgi?id=903609 --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- perl-XML-LibXSLT-1.80-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/perl-XML-LibXSLT-1.80-1.fc18 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FKtiL1WUhOa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: bisect on fedora kernels
On Thu, Aug 29, 2013 at 8:26 AM, Josh Boyer jwbo...@fedoraproject.org wrote: On Thu, Aug 29, 2013 at 3:32 AM, Igor Gnatenko i.gnatenko.br...@gmail.com wrote: On Thu, 2013-08-29 at 07:54 +0100, Ian Malone wrote: On 29 August 2013 01:53, Josh Boyer jwbo...@fedoraproject.org wrote: On Wed, Aug 28, 2013 at 6:59 PM, Ian Malone ibmal...@gmail.com wrote: Just to follow up, thanks, your instructions for building worked fine (I'd worried it wouldn't be so straightforward). Thought I'd best mention koji-bisect doesn't seem to exist anymore (in case anyone else finds this thread). Er... it doesn't? Where did you try to get it from, and how did it fail? Followed the link from http://jwboyer.livejournal.com/43007.html to http://fedorapeople.org/gitweb?p=jwboyer/public_git/koji-bisect.git;a=summary Also tried various yum searches for it in case it had quietly been moved into a package. yum search koji-bisect yum whatprovides */koji-bisect yum whatprovides */koji-bisect.py Google doesn't seem to suggest any other possible locations. Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage. Ok, you can clone it with: git clone git://fedorapeople.org/~jwboyer/koji-bisect.git I'm guessing the web browsing part broken when Infrastructure switched from gitweb to cgit. Hopefully I'll get whatever is needed fixed up and it will show up at: http://fedorapeople.org/cgit/jwboyer/public_git/koji-bisect.git in the near future. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Multiple Loopback Interfaces
I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? --- John Chludzinski john-chludzin...@myopera.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Multiple Loopback Interfaces
I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? ---John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: bisect on fedora kernels
On 29 August 2013 13:32, Josh Boyer jwbo...@fedoraproject.org wrote: On Thu, Aug 29, 2013 at 8:26 AM, Josh Boyer jwbo...@fedoraproject.org wrote: Strange. The source is definitely still on that machine. I'll look into why it's not showing up on the webpage. Ok, you can clone it with: git clone git://fedorapeople.org/~jwboyer/koji-bisect.git I'm guessing the web browsing part broken when Infrastructure switched from gitweb to cgit. Hopefully I'll get whatever is needed fixed up and it will show up at: http://fedorapeople.org/cgit/jwboyer/public_git/koji-bisect.git Ah, cloning was probably the one thing I hadn't tried. Both the gitweb and cgit web access locations seem to work now. -- imalone http://ibmalone.blogspot.co.uk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Rebuilding in dependency order
On 08/22/2013 07:35 PM, Björn Persson wrote: Miroslav Suchy wrote: On 08/22/2013 06:47 PM, Kevin Fenzi wrote: Well, I noticed the rebuild was running only some times. I assume when they were there to launch the builds in that batch? Is there any way all the builds could be listed and just fired off and queued all at once? Peter queue honor build requires (Dennis script for mass rebuilds does not) so if some build fail, the queue is heavily reduced or stopped at all. This last until the failed build is manually resolved. Firing off all builds at once will not help, because they would fail anyway due missing build requires. You make it sound like Peter has a tool for rebuilding in dependency order. I need such a thing. Can it be made to work for other things than Perl? It can take a list of packages and count dependencies, so it could be used for different languages. He didn't release the latest version yet. Archive of older releases http://ppisar.fedorapeople.org/Fedora-Rebuild/ Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File qpid-proton-0.5.tar.gz uploaded to lookaside cache by mcpierce
A file has been added to the lookaside cache for perl-qpid_proton: fb2dc704e4d2727d664966f301bfb017 qpid-proton-0.5.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: F21 schedule: what would you do with more time?
On 08/22/2013 05:15 PM, Jaroslav Reznik wrote: - Original Message - On Thu, Aug 22, 2013 at 11:03 PM, Matthew Miller mat...@fedoraproject.org wrote: What things we do _now_ could be improved with the investment of some effort? Perl rebuild always take a lot of time, and as a result it will affect the mass rebuild. It's unfortunately about Perl release timing... Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Upstream was asking for Fedora usual date of release, so what could we say ;-) It's twice a year. Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
El Jueves, 29 de agosto de 2013 06:38:00 John Chludzinski escribió: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? ---John In IPv4 you can get any IP in the 127.0.0.0/8 subnet for the lo interface. What are you trying to do? binding more than one process to the same port number? PS. It's probably better to use the fedora-users list for this kind of topics. signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
On Thu, Aug 29, 2013 at 06:34:57AM -0700, John Chludzinski wrote: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. It doesn't short circuit the network stack, thats why we have the loopback driver in the first place. How do I define multiple loopback interfaces? you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number. Neil BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? --- John Chludzinski john-chludzin...@myopera.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
On Thu, Aug 29, 2013 at 03:55:32PM +0200, Reindl Harald wrote: Am 29.08.2013 15:53, schrieb Neil Horman: you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number. that does not help you much in case as example a multi-postfix-installation when the software is not interested in using a different port and you want simulate real world by different IP's, binding services to specific ones and work with *hostnames* via /etc/hosts Then add multiple address aliases to the existing loopback interface. Either way, theres really no reason at all to create multiple loopback interfaces Neil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora 20 Alpha TC2 AMI's
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, images for Alpha TC2 have been uploaded to us-east-1 i386: eb82cf82 x86_64: ami-1583ce7c Happy Testing Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (GNU/Linux) iEYEARECAAYFAlIfVnoACgkQkSxm47BaWfcaYwCgmIms/nBOFUld5PjzM89hxZLp wiAAoIN0/lbSYwZok0hgYrU+wGtpgVAI =0XZe -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Thu, 29 Aug 2013 12:52:25 +0200, Till Maas wrote:
I guess you won't get responses to packages that are orphaned, because
then the bug report is assigned to the orphan user.
Only few were orphaned when filing the bugs. I just didn't think about
using the pkgdb API to fetch the list.
Dead and all builds obsoleted:
--
classads
ibus-table-array30
openstack-quantum
pdfbook
python-cryptsetup
python-quantumclient
These are now all blocked (some of them were already). You might want to
use the koji repos directly to get more up-to-date results:
http://kojipkgs.fedoraproject.org/mash/rawhide/i386/os
Can you maybe tweak your script to also show which
package obsoletes the package? This would make it easier to create a
meaningful dead.package file.
These are all src.rpm %{name}s and using the koji rawhide repo.
Dead and all builds obsoleted:
--
classads
obsoleted by: condor
ibus-table-array30
obsoleted by: ibus-table-chinese
pdfbook
obsoleted by: texlive
python-cryptsetup
obsoleted by: cryptsetup
Undead and all builds obsoleted:
drupal6-drush
obsoleted by: php-drush-drush
jaxen-bootstrap
obsoleted by: jaxen
joystick
obsoleted by: linuxconsoletools
kdirstat
obsoleted by: k4dirstat
latexdiff
obsoleted by: texlive
nss-myhostname
obsoleted by: systemd
pdfjam
obsoleted by: texlive
ps2eps
obsoleted by: texlive
seahorse-plugins
obsoleted by: seahorse-nautilus
zeitgeist-datahub
obsoleted by: zeitgeist
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
On Thu, Aug 29, 2013 at 9:47 AM, Juan Orti Alcaine juan.o...@miceliux.com wrote: In IPv4 you can get any IP in the 127.0.0.0/8 subnet for the lo interface. And in current fedora, they are already assigned to localhost. You can ping 127.0.0.22 if you want. AIUI, you can bind to it freely, too. m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Alpha TC2 AMI's
On Thu, Aug 29, 2013 at 09:11:01AM -0500, Dennis Gilmore wrote: images for Alpha TC2 have been uploaded to us-east-1 i386: eb82cf82 x86_64: ami-1583ce7c Thanks Dennis! Booted one up and it looks good at very first glance. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 999370] perl-POE-Test-Loops-1.352 is available
https://bugzilla.redhat.com/show_bug.cgi?id=999370 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-POE-Test-Loops-1.352-1 ||.fc19 Resolution|--- |CURRENTRELEASE Last Closed||2013-08-29 10:45:13 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Yc3anDhm7Pa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Rebuilding in dependency order
On 08/29/2013 07:42 AM, Marcela Mašláňová wrote: You make it sound like Peter has a tool for rebuilding in dependency order. I need such a thing. Can it be made to work for other things than Perl? It can take a list of packages and count dependencies, so it could be used for different languages. He didn't release the latest version yet. Archive of older releases http://ppisar.fedorapeople.org/Fedora-Rebuild/ So awhile back Seth sent me his buildorder.py scripts you can see it here. http://skvidal.wordpress.com/2013/05/17/sorting-srpms-by-buildorder/ Its nice in that it also does grouping so that it tells you what can be built in parallel. -- Nathanael d. Noblet t 403.875.4613 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
Both 127.0.0.7 and 127.0.0.10 exist in /etc/hosts for the client apps to use when connecting to the server.The clients use both gethostbyname() and getservbyname() for connecting. Currently, there are *no* multiple loopback interfaces defined. I wrote my own example TCP socket code to test the set up and found problems. Without defining multiple loopback interfaces using 127.0.0.7 and 127.0.0.10, are 127.0.0.7 and 127.0.0.10 simply the same interface? BTW, this is code I inherited. ---John On Thu, Aug 29, 2013, at 06:49 AM, Reindl Harald wrote: BTW: try to ping 127.0.0.1, 127.0.0.2, 127.0.0.3 here they are pingable as default the instruction below if only needed if the application checks that a configured IP exists via ifconfig or lookalike Am 29.08.2013 15:46, schrieb Reindl Harald: Am 29.08.2013 15:38, schrieb John Chludzinski: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? if you are running network.service it's trivial NetworkManager - no ida, i do not touch it ___ [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1 DEVICE=lo:1 IPADDR=127.0.0.2 ONPARENT=yes [root@rh:/etc/sysconfig/network-scripts]$ ifup lo:1 [root@rh:/etc/sysconfig/network-scripts]$ ifconfig lo:1 lo:1: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.2 netmask 255.0.0.0 loop txqueuelen 0 (Lokale Schleife) [root@rh:/etc/sysconfig/network-scripts]$ ping 127.0.0.2 PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. 64 bytes from 127.0.0.2: icmp_seq=1 ttl=50 time=0.056 ms ___ that's the lo config shipped with Fedora [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback Email had 1 attachment: + signature.asc 1k (application/pgp-signature) -- --- John Chludzinski john-chludzin...@myopera.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
On Thu, Aug 29, 2013 at 08:32:56AM -0700, John Chludzinski wrote: Both 127.0.0.7 and 127.0.0.10 exist in /etc/hosts for the client apps to use when connecting to the server.The clients use both gethostbyname() and getservbyname() for connecting. Currently, there are *no* multiple loopback interfaces defined. I wrote my own example TCP socket code to test the set up and found problems. What problems? Without defining multiple loopback interfaces using 127.0.0.7 and 127.0.0.10, are 127.0.0.7 and 127.0.0.10 simply the same interface? Yes. BTW, this is code I inherited. ---John On Thu, Aug 29, 2013, at 06:49 AM, Reindl Harald wrote: BTW: try to ping 127.0.0.1, 127.0.0.2, 127.0.0.3 here they are pingable as default the instruction below if only needed if the application checks that a configured IP exists via ifconfig or lookalike Am 29.08.2013 15:46, schrieb Reindl Harald: Am 29.08.2013 15:38, schrieb John Chludzinski: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? if you are running network.service it's trivial NetworkManager - no ida, i do not touch it ___ [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1 DEVICE=lo:1 IPADDR=127.0.0.2 ONPARENT=yes [root@rh:/etc/sysconfig/network-scripts]$ ifup lo:1 [root@rh:/etc/sysconfig/network-scripts]$ ifconfig lo:1 lo:1: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.2 netmask 255.0.0.0 loop txqueuelen 0 (Lokale Schleife) [root@rh:/etc/sysconfig/network-scripts]$ ping 127.0.0.2 PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. 64 bytes from 127.0.0.2: icmp_seq=1 ttl=50 time=0.056 ms ___ that's the lo config shipped with Fedora [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) Alternatively you can set /proc/net/ipv4/conf/l0/route_localnet to true -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review Request 47: Remove extra messages during sync
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/47/ --- Review request for blockerbugs. Bugs: 411 https://fedorahosted.org/fedora-qa/ticket/411 Repository: blockerbugs Description --- This is a simple change to get rid of the cron noise on sync in production so that it's easier to see and detect issues. The messages are changed from print statements to debug log messages. Diffs - blockerbugs/__init__.py e8283612c785459fc461d223dc6908187d2ab3f1 Diff: http://reviewboard-tflink.rhcloud.com/r/47/diff/ Testing --- I've done testing in my local env but the change itself is trivial and shouldn't cause problems Thanks, Tim Flink ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: EPEL pypy 2.1; sandbox, with shared library
Thank you, Kevin. I will re-subscribe with dan@worldquant.com. Will do what you suggest. Thanks, Dan -Original Message- From: Kevin Fenzi [mailto:ke...@scrye.com] Sent: Wednesday, August 28, 2013 12:13 PM To: EPEL Development List Cc: Guo, Dan (WorldQuant); 'Ralph Angenendt' Subject: Re: EPEL pypy 2.1; sandbox, with shared library On Wed, 28 Aug 2013 13:05:22 + Guo, Dan (WorldQuant) dan@worldquant.com wrote: Greeting, I just found out this list and subscribe to it. my subscription is new. Your post was stopped in moderation because you weren't subscribed with the same address you were posting with. Make sure the one you subscribe with is the same as the one you send from. ;) Pypy2.1 is now released. I see repo has pypy 2.0.2 as latest. Can I request this is updated for 2.1? also, I wonder if someone has made shared library for pypy sandboxing, for 2.0.2. when I looked at it, it does not seem it has. As I am new, please give me pointers and tell me how this list works. If my email is off mark, be frank and let me know. Thank you very much, Dan Welcome. I'd suggest filing a bug on it and the maintainer can discuss with you: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPELversion=el6component=pypy kevin ### The information contained in this communication is confidential, may be subject to legal privilege, and is intended only for the individual named. If you are not the named addressee, please notify the sender immediately and delete this email from your system. The views expressed in this email are the views of the sender only. Outgoing and incoming electronic communications to this address are electronically archived and subject to review and/or disclosure to someone other than the recipient. ### ___ epel-devel mailing list epel-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: Multiple Loopback Interfaces
Am 29.08.2013 15:53, schrieb Neil Horman: you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number. that does not help you much in case as example a multi-postfix-installation when the software is not interested in using a different port and you want simulate real world by different IP's, binding services to specific ones and work with *hostnames* via /etc/hosts signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
Am 29.08.2013 15:38, schrieb John Chludzinski: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? if you are running network.service it's trivial NetworkManager - no ida, i do not touch it ___ [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1 DEVICE=lo:1 IPADDR=127.0.0.2 ONPARENT=yes [root@rh:/etc/sysconfig/network-scripts]$ ifup lo:1 [root@rh:/etc/sysconfig/network-scripts]$ ifconfig lo:1 lo:1: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.2 netmask 255.0.0.0 loop txqueuelen 0 (Lokale Schleife) [root@rh:/etc/sysconfig/network-scripts]$ ping 127.0.0.2 PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. 64 bytes from 127.0.0.2: icmp_seq=1 ttl=50 time=0.056 ms ___ that's the lo config shipped with Fedora [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
BTW: try to ping 127.0.0.1, 127.0.0.2, 127.0.0.3 here they are pingable as default the instruction below if only needed if the application checks that a configured IP exists via ifconfig or lookalike Am 29.08.2013 15:46, schrieb Reindl Harald: Am 29.08.2013 15:38, schrieb John Chludzinski: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? if you are running network.service it's trivial NetworkManager - no ida, i do not touch it ___ [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1 DEVICE=lo:1 IPADDR=127.0.0.2 ONPARENT=yes [root@rh:/etc/sysconfig/network-scripts]$ ifup lo:1 [root@rh:/etc/sysconfig/network-scripts]$ ifconfig lo:1 lo:1: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.2 netmask 255.0.0.0 loop txqueuelen 0 (Lokale Schleife) [root@rh:/etc/sysconfig/network-scripts]$ ping 127.0.0.2 PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. 64 bytes from 127.0.0.2: icmp_seq=1 ttl=50 time=0.056 ms ___ that's the lo config shipped with Fedora [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Multiple Loopback Interfaces
On Thu, 2013-08-29 at 15:46 +0200, Reindl Harald wrote: Am 29.08.2013 15:38, schrieb John Chludzinski: I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose. How do I define multiple loopback interfaces? BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question? if you are running network.service it's trivial NetworkManager - no ida, i do not touch it NM does nothing with lo, so the same procedure below would certainly apply if you're running NM. Touch lo all you want. Dan ___ [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1 DEVICE=lo:1 IPADDR=127.0.0.2 ONPARENT=yes [root@rh:/etc/sysconfig/network-scripts]$ ifup lo:1 [root@rh:/etc/sysconfig/network-scripts]$ ifconfig lo:1 lo:1: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.2 netmask 255.0.0.0 loop txqueuelen 0 (Lokale Schleife) [root@rh:/etc/sysconfig/network-scripts]$ ping 127.0.0.2 PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. 64 bytes from 127.0.0.2: icmp_seq=1 ttl=50 time=0.056 ms ___ that's the lo config shipped with Fedora [root@rh:/etc/sysconfig/network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Where does loopback short circuit ?
I've had a debate with some co-workers about whether or not a message that's sent to the loopback interface makes it way into the IP layer and is fragmented before flowing back up the network stack. Does it? ---John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Where does loopback short circuit ?
On Thu, Aug 29, 2013 at 10:02:27AM -0700, John Chludzinski wrote: I've had a debate with some co-workers about whether or not a message that's sent to the loopback interface makes it way into the IP layer and is fragmented before flowing back up the network stack. Does it? Can you please not keep creating new top level threads. Furthermore, this is not an appropriate mailing list to discuss any general (not even Linux) networking issues that you may have. It's more appropriate for a venue such as stackoverflow. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
On Thu, 29 Aug 2013 09:05:24 +0300 Panu Matilainen pmati...@laiskiainen.org wrote: ...snip... Let me say AWESOME one more time :) :) I actually didn't know that this was so much of a bottleneck for you folks. ;( Anyhow, glad we can move forward and hopefully get things rolling faster. Of course it does mean we could run into breakage if there's breakage in Fedora land, but thats good to know and fix too. Yes, dogfooding on the builders can IMO only be a good thing for overall stability of Fedora, even if it might initially cause some extra hickups. Breaking the builders a couple of times and getting scolded for that ought to make people think a bit more about pushing potentially destabilizing updates :) Exactly. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Packages depending on retired packages
On Thu, Aug 29, 2013 at 04:15:15PM +0200, Michael Schwendt wrote: Undead and all builds obsoleted: drupal6-drush obsoleted by: php-drush-drush jaxen-bootstrap obsoleted by: jaxen joystick obsoleted by: linuxconsoletools kdirstat obsoleted by: k4dirstat latexdiff obsoleted by: texlive nss-myhostname obsoleted by: systemd pdfjam obsoleted by: texlive ps2eps obsoleted by: texlive seahorse-plugins obsoleted by: seahorse-nautilus zeitgeist-datahub obsoleted by: zeitgeist They should be retired, blocked and dead now. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
X2Go - plea for reviewers
So, after some quick initial progress, we seemed to have stalled out on the X2Go package reviews. Any help would be appreciated. Thanks. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
X2Go - plea for reviewers
So, after some quick initial progress, we seemed to have stalled out on the X2Go package reviews. Any help would be appreciated. Thanks. See: https://fedoraproject.org/wiki/Changes/X2Go#Scope for packages to review. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Where does loopback short circuit ?
On Thu, 2013-08-29 at 18:04 +0100, Richard W.M. Jones wrote: On Thu, Aug 29, 2013 at 10:02:27AM -0700, John Chludzinski wrote: I've had a debate with some co-workers about whether or not a message that's sent to the loopback interface makes it way into the IP layer and is fragmented before flowing back up the network stack. Does it? Can you please not keep creating new top level threads. Furthermore, this is not an appropriate mailing list to discuss any general (not even Linux) networking issues that you may have. It's more appropriate for a venue such as stackoverflow. Rich. I am unsure of the standards for this. I am also curious about the Fedora implementation. I would suspect that the loopback mechanism would be implementation dependent, and that the method used on a particular system would provide valuable information. A usergroup such as stackoverflow would not likely have that information. Therefore this would seem to be the most accurate source for such information IMO. A short and reasonable answer would be beneficial to the group. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Where does loopback short circuit ?
On Thu, Aug 29, 2013 at 01:06:23PM -0700, Les Howell wrote: On Thu, 2013-08-29 at 18:04 +0100, Richard W.M. Jones wrote: On Thu, Aug 29, 2013 at 10:02:27AM -0700, John Chludzinski wrote: I've had a debate with some co-workers about whether or not a message that's sent to the loopback interface makes it way into the IP layer and is fragmented before flowing back up the network stack. Does it? Can you please not keep creating new top level threads. Furthermore, this is not an appropriate mailing list to discuss any general (not even Linux) networking issues that you may have. It's more appropriate for a venue such as stackoverflow. Rich. I am unsure of the standards for this. I am also curious about the Fedora implementation. I would suspect that the loopback mechanism would be implementation dependent, and that the method used on a particular system would provide valuable information. A usergroup such as stackoverflow would not likely have that information. Therefore this would seem to be the most accurate source for such information IMO. A short and reasonable answer would be beneficial to the group. The answer is simple, and as always, contained in the source. lo is defined in: drivers/net/loopback.c It registers an interface using the network driver api, and contains a transmit routine. Therefore, all frames that go to the loopback interface go through the entire routing stack, and get looped at the driver. honestly, doing anything less tends to get pretty messy anyway, as you start to have to handle all sorts of special cases. Consider the possibility that a packet socket is listening on lo when you transmit a tcp frame out of it. If you looped it back higher in the stack, you'd have to be sure to clone the skb and offer the packet to the packet protocol somewhere in the ip stack. Multiply that by every protocol listener available in the kernel and the fan out gets unmanageable. Its better to just go down to the driver layer and loop there. Neil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
On 29 Aug 2013 18:12, Kevin Fenzi ke...@scrye.com wrote: On Thu, 29 Aug 2013 09:05:24 +0300 Panu Matilainen pmati...@laiskiainen.org wrote: ...snip... Let me say AWESOME one more time :) :) I actually didn't know that this was so much of a bottleneck for you folks. ;( Anyhow, glad we can move forward and hopefully get things rolling faster. Of course it does mean we could run into breakage if there's breakage in Fedora land, but thats good to know and fix too. Yes, dogfooding on the builders can IMO only be a good thing for overall stability of Fedora, even if it might initially cause some extra hickups. Breaking the builders a couple of times and getting scolded for that ought to make people think a bit more about pushing potentially destabilizing updates :) Exactly. I know we discovered a few issues in the last couple of years doing this with arm because of using the stable fedora arm release so I'm glad we're able to help :-) Pete kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
On 08/29/2013 01:10 PM, Kevin Fenzi wrote: On Thu, 29 Aug 2013 09:05:24 +0300 Panu Matilainen pmati...@laiskiainen.org wrote: ...snip... Let me say AWESOME one more time :) :) I actually didn't know that this was so much of a bottleneck for you folks. ;( Anyhow, glad we can move forward and hopefully get things rolling faster. Of course it does mean we could run into breakage if there's breakage in Fedora land, but thats good to know and fix too. Yes, dogfooding on the builders can IMO only be a good thing for overall stability of Fedora, even if it might initially cause some extra hickups. Breaking the builders a couple of times and getting scolded for that ought to make people think a bit more about pushing potentially destabilizing updates :) Exactly. kevin I'm not saying this was a bad idea, but the Koji developers now have to test on both RHEL 6 and Fedora now. Let this message serve as a warning to them if they did not already know. ;) - Jay -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
I'm not saying this was a bad idea, but the Koji developers now have to test on both RHEL 6 and Fedora now. Let this message serve as a warning to them if they did not already know. ;) They already were anyway due to the ARM builders in secondary so they've been getting reports from us for 3 years or so :-) Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Alpha TC2 AMI's
On Thu, Aug 29, 2013 at 7:38 AM, Matthew Miller mat...@fedoraproject.org wrote: On Thu, Aug 29, 2013 at 09:11:01AM -0500, Dennis Gilmore wrote: images for Alpha TC2 have been uploaded to us-east-1 i386: eb82cf82 x86_64: ami-1583ce7c Thanks Dennis! Booted one up and it looks good at very first glance. -- How does one bring one down? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Alpha TC2 AMI's
On Thu, Aug 29, 2013 at 03:21:36PM -0700, Richard Vickery wrote: i386: eb82cf82 x86_64: ami-1583ce7c Thanks Dennis! Booted one up and it looks good at very first glance. How does one bring one down? You can download the same images in raw.xz or qcow2 format from http://alt.fedoraproject.org/pub/alt/stage/20-Alpha-TC2/Images/x86_64/ -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Alpha TC2 AMI's
On Thu, Aug 29, 2013 at 3:55 PM, Matthew Miller mat...@fedoraproject.org wrote: On Thu, Aug 29, 2013 at 03:21:36PM -0700, Richard Vickery wrote: i386: eb82cf82 x86_64: ami-1583ce7c Thanks Dennis! Booted one up and it looks good at very first glance. How does one bring one down? You can download the same images in raw.xz or qcow2 format from http://alt.fedoraproject.org/pub/alt/stage/20-Alpha-TC2/Images/x86_64/ is it possible to use the fedup command? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self Introduction
Hello friends, I have been part of the Fedora Project for several years (mainly as an Ambassador) and now I've decided to join the Packaging team! I live in Buenos Aires, Argentina, I work for IBM and I only have to pass 1 exam (RH401) to become a RHCA. I have been using Linux since the 90's. Starting with Red Hat Linux, passing to Mandrake, SuSE, Slackware and finally a strong user of Fedora since version 5. I have submitted some packages to review. I look forward to use my Linux skills to help make this distribution great and to learn a lot of things on the way. This is what I have submitted so far: https://bugzilla.redhat.com/show_bug.cgi?id=1002319 https://bugzilla.redhat.com/show_bug.cgi?id=1002321 https://bugzilla.redhat.com/show_bug.cgi?id=1002324 https://bugzilla.redhat.com/show_bug.cgi?id=894119 zodbot will describe me as: User: delete, Name: Matías Kreder, email: mkre...@gmail.com, Creation: 2009-06-01, IRC Nick: delete, Timezone: America/Argentina/Buenos_Aires, Locale: en, GPG key ID: 2048R/54A62E60, Status: active Approved Groups: ambassadors cla_fedora cla_done freemedia marketing +fedora-socialmedia cla_fpca I look forward to get sponsorship for this group. If someone wants to mentor me, the position is still open. Best Regards, Matias Kreder -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Builder update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Thu, 29 Aug 2013 16:59:44 -0400 Jay Greguske jgreg...@redhat.com escribió: On 08/29/2013 01:10 PM, Kevin Fenzi wrote: On Thu, 29 Aug 2013 09:05:24 +0300 Panu Matilainen pmati...@laiskiainen.org wrote: ...snip... Let me say AWESOME one more time :) :) I actually didn't know that this was so much of a bottleneck for you folks. ;( Anyhow, glad we can move forward and hopefully get things rolling faster. Of course it does mean we could run into breakage if there's breakage in Fedora land, but thats good to know and fix too. Yes, dogfooding on the builders can IMO only be a good thing for overall stability of Fedora, even if it might initially cause some extra hickups. Breaking the builders a couple of times and getting scolded for that ought to make people think a bit more about pushing potentially destabilizing updates :) Exactly. kevin I'm not saying this was a bad idea, but the Koji developers now have to test on both RHEL 6 and Fedora now. Let this message serve as a warning to them if they did not already know. ;) Its been something i've been doing for years, testing my koji changes on el6 and fedora. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (GNU/Linux) iEYEARECAAYFAlIf8/EACgkQkSxm47BaWffE2gCgrQU2ykIvkM9OZBKeG7dxwg/i /dcAn3MK6IB4rhXdsIwHglz+T55yQtSS =D34I -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Running a command in spec file?
On Thu, Aug 29, 2013 at 4:09 AM, Miroslav Suchý msu...@redhat.com wrote:
On 08/29/2013 12:04 PM, Dave Johansen wrote:
So does that mean that this is the correct statement to put in the .spec
file?
%{?scl:scl enable %{scl} }
source /opt/rh/devtoolset-1.1/enable
%{?scl:}
What is the %{?scl} macro doing? And am I using it correctly in the above?
This scriplet:
%{?scl:scl enable %{scl} }
command 1
%{?scl:}
basicaly expand to:
%if 0%{?scl}
scl enable command 1
%endif
Therefore your scriplet:
%{?scl:scl enable %{scl} }
source /opt/rh/devtoolset-1.1/enable
%{?scl:}
would expand to:
%if 0%{?scl}
scl enable source /opt/rh/devtoolset-1.1/enable
%endif
which does not have sense.
I see that you want to enable SCL and from that moment you want to have
collection enabled.
This is not recommended (and therefore there is no such tool to do that).
You must enable collection for each specific command. Or block of commands
by heredoc syntax.
For operating on command line, you can do:
scl enable devtoolset-1.1 bash
which will open you shell where collection is enabled until you exit. But
for spec file, please enable collection for each command/block.
Based on my understanding of what you said, this is my best guess at what
the lines in the .spec should be:
%{?scl:scl enable devtoolset-1.1 }
%configure --disable-static
%{?scl:}
But that doesn't work, so I'm obviously doing something wrong.
If I just do these two lines, then it works:
source /opt/rh/devtoolset-1.1/enable
%configure --disable-static
But my understanding was that there was something wrong with doing that, so
what is the proper way to enable the devtoolset-1.1 scl for use with the
configure macro?
Thanks,
Dave
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1002402] New: exclude DBD::CSV in RHEL-7
https://bugzilla.redhat.com/show_bug.cgi?id=1002402 Bug ID: 1002402 Summary: exclude DBD::CSV in RHEL-7 Product: Fedora Version: rawhide Component: perl-SQL-Statement Assignee: psab...@redhat.com Reporter: jfe...@redhat.com QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, psab...@redhat.com Created attachment 791614 -- https://bugzilla.redhat.com/attachment.cgi?id=791614action=edit Spec file patch to exclude DBD::CSV on RHEL-7 Description of problem: RHEL-7 doesn't carry DBD::CSV, so it should never be pulled in. Version-Release number of selected component (if applicable): 1.402-2 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=v27kluhrBza=cc_unsubscribe -- 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 WWW-OrangeHRM-Client-v0.6.0.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-WWW-OrangeHRM-Client: db24c0565c505226a9c48ac5162d56b0 WWW-OrangeHRM-Client-v0.6.0.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-WWW-OrangeHRM-Client] 0.6.0 bump
commit 2b9c403f26e2e6a8c2c494f70582d826904bef35
Author: Petr Písař ppi...@redhat.com
Date: Thu Aug 29 09:35:54 2013 +0200
0.6.0 bump
.gitignore |1 +
perl-WWW-OrangeHRM-Client.spec |7 +--
sources|2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index dab8a2b..87b557e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
/WWW-OrangeHRM-Client-v0.3.0.tar.gz
/WWW-OrangeHRM-Client-v0.4.0.tar.gz
/WWW-OrangeHRM-Client-v0.5.0.tar.gz
+/WWW-OrangeHRM-Client-v0.6.0.tar.gz
diff --git a/perl-WWW-OrangeHRM-Client.spec b/perl-WWW-OrangeHRM-Client.spec
index 83757e6..0a743c3 100644
--- a/perl-WWW-OrangeHRM-Client.spec
+++ b/perl-WWW-OrangeHRM-Client.spec
@@ -1,7 +1,7 @@
%global tarname WWW-OrangeHRM-Client
Name: perl-%{tarname}
-Version:0.5.0
-Release:3%{?dist}
+Version:0.6.0
+Release:1%{?dist}
Summary:Client for OrangeHRM
License:GPL+
Group: Development/Libraries
@@ -42,6 +42,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Thu Aug 29 2013 Petr Pisar ppi...@redhat.com - 0.6.0-1
+- 0.6.0 bump
+
* Sun Aug 04 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.5.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 292dec6..f64030d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bd1a7262f07df7240a745f7297abce38 WWW-OrangeHRM-Client-v0.5.0.tar.gz
+db24c0565c505226a9c48ac5162d56b0 WWW-OrangeHRM-Client-v0.6.0.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-WWW-OrangeHRM-Client/f20] 0.6.0 bump
Summary of changes: 2b9c403... 0.6.0 bump (*) (*) 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
[perl-WWW-OrangeHRM-Client/f19] 0.6.0 bump
commit 8db68ad4f15c5ea3cba3f9c006af552ae8e9bea2
Author: Petr Písař ppi...@redhat.com
Date: Thu Aug 29 09:35:54 2013 +0200
0.6.0 bump
.gitignore |1 +
perl-WWW-OrangeHRM-Client.spec |5 -
sources|2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index dab8a2b..87b557e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
/WWW-OrangeHRM-Client-v0.3.0.tar.gz
/WWW-OrangeHRM-Client-v0.4.0.tar.gz
/WWW-OrangeHRM-Client-v0.5.0.tar.gz
+/WWW-OrangeHRM-Client-v0.6.0.tar.gz
diff --git a/perl-WWW-OrangeHRM-Client.spec b/perl-WWW-OrangeHRM-Client.spec
index c892bfc..6eb8359 100644
--- a/perl-WWW-OrangeHRM-Client.spec
+++ b/perl-WWW-OrangeHRM-Client.spec
@@ -1,6 +1,6 @@
%global tarname WWW-OrangeHRM-Client
Name: perl-%{tarname}
-Version:0.5.0
+Version:0.6.0
Release:1%{?dist}
Summary:Client for OrangeHRM
License:GPL+
@@ -42,6 +42,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Thu Aug 29 2013 Petr Pisar ppi...@redhat.com - 0.6.0-1
+- 0.6.0 bump
+
* Thu Apr 11 2013 Petr Pisar ppi...@redhat.com - 0.5.0-1
- 0.5.0 bump
diff --git a/sources b/sources
index 292dec6..f64030d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bd1a7262f07df7240a745f7297abce38 WWW-OrangeHRM-Client-v0.5.0.tar.gz
+db24c0565c505226a9c48ac5162d56b0 WWW-OrangeHRM-Client-v0.6.0.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-WWW-OrangeHRM-Client/f18] 0.6.0 bump
Summary of changes: 8db68ad... 0.6.0 bump (*) (*) 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
[Bug 1002402] exclude DBD::CSV in RHEL-7
https://bugzilla.redhat.com/show_bug.cgi?id=1002402 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-SQL-Statement-1.402-3. ||el7 --- Comment #1 from Petr Šabata psab...@redhat.com --- Ok, I see you've already pushed this. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=0XgcKht1vIa=cc_unsubscribe -- 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-Alien-ROOT
perl-Alien-ROOT has broken dependencies in the F-20 tree: On armhfp: perl-Alien-ROOT-5.34.3.1-3.fc20.noarch requires root-core 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
Broken dependencies: perl-IPTables-libiptc
perl-IPTables-libiptc has broken dependencies in the F-20 tree: On x86_64: perl-IPTables-libiptc-0.52-5.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-IPTables-libiptc-0.52-5.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-IPTables-libiptc-0.52-5.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-Encode-JP-Mobile
perl-Encode-JP-Mobile has broken dependencies in the F-20 tree: On x86_64: perl-Encode-JP-Mobile-0.30-2.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Encode-JP-Mobile-0.30-2.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Encode-JP-Mobile-0.30-2.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-ParseUtil-Domain
perl-ParseUtil-Domain has broken dependencies in the F-20 tree: On x86_64: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-ParseUtil-Domain-2.22-3.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-MooseX-TrackDirty-Attributes
perl-MooseX-TrackDirty-Attributes has broken dependencies in the F-20 tree: On x86_64: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-PDL
perl-PDL has broken dependencies in the F-20 tree: On x86_64: perl-PDL-2.4.10-6.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit) On i386: perl-PDL-2.4.10-6.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) perl-PDL-2.4.10-6.fc19.i686 requires libgd.so.2 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
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the F-20 tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: slic3r
slic3r has broken dependencies in the F-20 tree: On x86_64: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On i386: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On armhfp: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) 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
Broken dependencies: perl-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the F-20 tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-19.fc20.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-19.fc20.noarch requires perl(Bio::Index::AbstractSeq) On armhfp: perl-Bio-ASN1-EntrezGene-1.091-19.fc20.noarch requires perl(Bio::Index::AbstractSeq) 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
Broken dependencies: perl-MIME-Lite-HTML
perl-MIME-Lite-HTML has broken dependencies in the F-20 tree: On x86_64: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On i386: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On armhfp: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) 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
Broken dependencies: perl-Qt
perl-Qt has broken dependencies in the F-20 tree: On x86_64: perl-Qt-0.96.0-6.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.x86_64 requires libperl.so()(64bit) On i386: perl-Qt-0.96.0-6.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.i686 requires libperl.so On armhfp: perl-Qt-0.96.0-6.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.armv7hl requires libperl.so 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
Broken dependencies: perl-Jemplate
perl-Jemplate has broken dependencies in the F-20 tree: On x86_64: perl-Jemplate-0.262-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Jemplate-0.262-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Jemplate-0.262-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-Padre
perl-Padre has broken dependencies in the F-20 tree: On x86_64: perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On i386: perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On armhfp: perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) 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
[Bug 903609] perl-XML-LibXSLT-1.80 is available
https://bugzilla.redhat.com/show_bug.cgi?id=903609 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-XML-LibXML-2.0004-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/perl-XML-LibXML-2.0004-2.fc18 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=lmK78PVXDza=cc_unsubscribe -- 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-XML-LibXSLT/f18] 1.80 bump
commit eb558fa87d533783e4b09640c840f283a930ad14
Author: Jitka Plesnikova jples...@redhat.com
Date: Thu Aug 29 13:48:27 2013 +0200
1.80 bump
perl-XML-LibXSLT.spec | 32 +---
1 files changed, 17 insertions(+), 15 deletions(-)
---
diff --git a/perl-XML-LibXSLT.spec b/perl-XML-LibXSLT.spec
index 47c0b44..14e712a 100644
--- a/perl-XML-LibXSLT.spec
+++ b/perl-XML-LibXSLT.spec
@@ -1,28 +1,28 @@
Name: perl-XML-LibXSLT
# NOTE: also update perl-XML-LibXML to a compatible version. See below why.
-Version: 1.77
-Release: 3%{?dist}
+Version: 1.80
+Release: 1%{?dist}
Summary: Perl module for interfacing to GNOME's libxslt
Group: Development/Libraries
License: GPL+ or Artistic
URL: http://search.cpan.org/dist/XML-LibXSLT/
-Source0:
http://search.cpan.org/CPAN/authors/id/P/PA/PAJAS/XML-LibXSLT-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/S/SH/SHLOMIF/XML-LibXSLT-%{version}.tar.gz
BuildRequires: perl(Carp)
-BuildRequires: perl(DynaLoader)
+BuildRequires: perl(DynaLoader)
BuildRequires: perl(Encode)
BuildRequires: perl(Exporter)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Test::More)
-BuildRequires: libxslt-devel = 1.1.18, gdbm-devel, libgcrypt-devel,
libgpg-error-devel
+BuildRequires: libxslt-devel = 1.1.28, gdbm-devel, libgcrypt-devel,
libgpg-error-devel
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
# the package shares code with perl-XML-LibXML, we have to require a
compatible version
# see https://bugzilla.redhat.com/show_bug.cgi?id=469480
# for testing is needed the same version of XML::LibXML
# BUT XML::LibXML has new bugfix releases, but XML::LibXSLT not
-BuildRequires: perl(XML::LibXML::Boolean)
-BuildRequires: perl(XML::LibXML::Literal)
-BuildRequires: perl(XML::LibXML::NodeList)
-BuildRequires: perl(XML::LibXML::Number)
+BuildRequires: perl(XML::LibXML::Boolean)
+BuildRequires: perl(XML::LibXML::Literal)
+BuildRequires: perl(XML::LibXML::NodeList)
+BuildRequires: perl(XML::LibXML::Number)
BuildRequires: perl(XML::LibXML) = %{version}
Requires: perl(XML::LibXML) = %{version}
@@ -40,10 +40,9 @@ perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE=%{optflags}
make %{?_smp_mflags}
%install
-make pure_install PERL_INSTALL_ROOT=%{buildroot}
-find %{buildroot} -type f -name .packlist -exec rm -f {} ';'
-find %{buildroot} -type f -name '*.bs' -a -size 0 -exec rm -f {} ';'
-find %{buildroot} -type d -depth -exec rmdir {} 2/dev/null ';'
+make pure_install DESTDIR=%{buildroot}
+find %{buildroot} -type f -name .packlist -exec rm -f {} +
+find %{buildroot} -type f -name '*.bs' -a -size 0 -exec rm -f {} +
chmod -R u+w %{buildroot}/*
%check
@@ -56,6 +55,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Thu Aug 29 2013 Jitka Plesnikova jples...@redhat.com - 1.80-1
+- 1.80 bump
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.77-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
@@ -170,14 +172,14 @@ make test
- new upstream
- use dist macro
-* Fri Apr 7 2005 Michael Schwendt mschwendt[AT]users.sf.net
+* Fri Apr 8 2005 Michael Schwendt mschwendt[AT]users.sf.net
- rebuilt
* Sat Mar 5 2005 Ville Skyttä ville.skytta at iki.fi - 1.57-3
- Drop pre-FC2 LD_RUN_PATH hack.
- Install benchmark.pl only as %%doc.
-* Fri Feb 26 2005 Zing shi...@hotpop.com - 1.57-2
+* Fri Feb 25 2005 Zing shi...@hotpop.com - 1.57-2
- QA from Ville Skyttä
- BuildRequires XML::LibXML = 1.57
- BuildRequires libxslt-devel
--
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-XML-LibXSLT/f18] 1.80 bump
commit 407d8894f01024fc81edaecf55395fc381ddaf62 Author: Jitka Plesnikova jples...@redhat.com Date: Thu Aug 29 13:48:35 2013 +0200 1.80 bump .gitignore |1 + sources|2 +- 2 files changed, 2 insertions(+), 1 deletions(-) --- diff --git a/.gitignore b/.gitignore index f02cfde..79281f6 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,4 @@ XML-LibXSLT-1.70.tar.gz /XML-LibXSLT-1.75.tar.gz /XML-LibXSLT-1.76.tar.gz /XML-LibXSLT-1.77.tar.gz +/XML-LibXSLT-1.80.tar.gz diff --git a/sources b/sources index 73ab410..961a619 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -a9cf4adb3637a0a42eb69a2998fa488e XML-LibXSLT-1.77.tar.gz +bd8d0eaeee311a6dc148963a3f7753c6 XML-LibXSLT-1.80.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
Broken dependencies: perl-PDL
perl-PDL has broken dependencies in the rawhide tree: On x86_64: perl-PDL-2.4.10-6.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit) On i386: perl-PDL-2.4.10-6.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) perl-PDL-2.4.10-6.fc19.i686 requires libgd.so.2 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
Broken dependencies: perl-Qt
perl-Qt has broken dependencies in the rawhide tree: On x86_64: perl-Qt-0.96.0-6.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.x86_64 requires libperl.so()(64bit) On i386: perl-Qt-0.96.0-6.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.i686 requires libperl.so On armhfp: perl-Qt-0.96.0-6.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) perl-Qt-0.96.0-6.fc19.armv7hl requires libperl.so 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
Broken dependencies: perl-MooseX-TrackDirty-Attributes
perl-MooseX-TrackDirty-Attributes has broken dependencies in the rawhide tree: On x86_64: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the rawhide tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: perl-MIME-Lite-HTML
perl-MIME-Lite-HTML has broken dependencies in the rawhide tree: On x86_64: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On i386: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) On armhfp: perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) 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
Broken dependencies: perl-Encode-JP-Mobile
perl-Encode-JP-Mobile has broken dependencies in the rawhide tree: On x86_64: perl-Encode-JP-Mobile-0.30-2.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Encode-JP-Mobile-0.30-2.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Encode-JP-Mobile-0.30-2.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) 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
Broken dependencies: slic3r
slic3r has broken dependencies in the rawhide tree: On x86_64: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On i386: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) On armhfp: slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3) 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
Broken dependencies: perl-Unix-Statgrab
perl-Unix-Statgrab has broken dependencies in the rawhide tree: On x86_64: perl-Unix-Statgrab-0.04-20.fc20.x86_64 requires libstatgrab.so.6()(64bit) On i386: perl-Unix-Statgrab-0.04-20.fc20.i686 requires libstatgrab.so.6 On armhfp: perl-Unix-Statgrab-0.04-20.fc20.armv7hl requires libstatgrab.so.6 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
Broken dependencies: perl-Alien-ROOT
perl-Alien-ROOT has broken dependencies in the rawhide tree: On armhfp: perl-Alien-ROOT-5.34.3.1-3.fc20.noarch requires root-core 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
Broken dependencies: perl-IPTables-libiptc
perl-IPTables-libiptc has broken dependencies in the rawhide tree: On x86_64: perl-IPTables-libiptc-0.52-5.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-IPTables-libiptc-0.52-5.fc19.i686 requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-IPTables-libiptc-0.52-5.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) 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
