2010/6/30 Rich Mattes richmat...@gmail.com:
Hi all,
I'm trying to build a package that has a BuildRequires: libjpeg-devel in
Rawhide [1]. I get a message in root.log that libjpeg-turbo-devel
obsoletes libjpeg-devel, so yum pulls in libjpeg-turbo-devel instead.
Unfortunately, when it pulls
On Tue, Jun 29, 2010 at 05:58:42PM -0700, Jay Hankinson wrote:
Thanks for the quick response, spot. See below...
On 6/29/10 5:25 PM, Tom spot Callaway wrote:
On 06/29/2010 08:12 PM, Jay Hankinson wrote:
Hello Fedora Devs,
I'm currently going through the pre-review process for adding
On Wed, 30 Jun 2010 14:04:51 +0800, Chen wrote:
2010/6/30 Rich Mattes richmat...@gmail.com:
Hi all,
I'm trying to build a package that has a BuildRequires: libjpeg-devel in
Rawhide [1]. I get a message in root.log that libjpeg-turbo-devel
obsoletes libjpeg-devel, so yum pulls in
2010/6/30 Michael Schwendt mschwe...@gmail.com:
On Wed, 30 Jun 2010 14:04:51 +0800, Chen wrote:
2010/6/30 Rich Mattes richmat...@gmail.com:
Hi all,
I'm trying to build a package that has a BuildRequires: libjpeg-devel in
Rawhide [1]. I get a message in root.log that libjpeg-turbo-devel
On Wed, Jun 30, 2010 at 10:21 AM, Chen Lei supercyp...@gmail.com wrote:
2010/6/30 Michael Schwendt mschwe...@gmail.com:
On Wed, 30 Jun 2010 14:04:51 +0800, Chen wrote:
2010/6/30 Rich Mattes richmat...@gmail.com:
Hi all,
I'm trying to build a package that has a BuildRequires:
On Wed, 30 Jun 2010 10:25:37 +0100, Peter wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils. I don't know why
Rich's package failed to build on koji, the problem is a bit weird.
Among 5 packages which require
Hi.
On Wed, 30 Jun 2010 17:21:37 +0800, Chen Lei wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils.
I assume that you cannot really install libjpeg-turbo-utils without
pulling in libjpeg-turbo, so the the obsoletes
On 06/29/2010 05:27 PM, Trever L. Adams wrote:
Hello,
I am wondering if someone would be willing to package
http://samba.org/~tridge/junkcode/tsig-gss/ and maybe work with the
ddclient people to add support for adding A and records with this.
(I do not know if bind shipped in Fedora has
Compose started at Wed Jun 30 08:15:25 UTC 2010
Broken deps for i386
--
BackupPC-3.1.0-14.fc14.noarch requires perl-suidperl
1:anjuta-2.30.0.0-2.fc14.i686 requires libgladeui-1.so.9
1:control-center-2.31.3-2.fc14.i686
On 6/30/2010 5:35 AM, Michael Schwendt wrote:
On Wed, 30 Jun 2010 10:25:37 +0100, Peter wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils. I don't know why
Rich's package failed to build on koji, the problem is a
On Wed, 30 Jun 2010 17:21:37 +0800, Chen wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils.
root.log of
http://koji.fedoraproject.org/koji/taskinfo?taskID=2282066
doesn't refer to libjpeg-turbo-utils at all, but just
2010/6/30 Rich Mattes richmat...@gmail.com:
I played with it a little bit more last night, the problem occurred when
my package pulled in graphviz. Graphviz has a BR:libjpeg-devel, and
makes no mention of libjpeg-utils. It only relies on libjpeg for the
libraries, and doesn't need any of the
2010/6/30 Michael Schwendt mschwe...@gmail.com:
On Wed, 30 Jun 2010 17:21:37 +0800, Chen wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils.
root.log of
http://koji.fedoraproject.org/koji/taskinfo?taskID=2282066
On 06/30/2010 05:01 AM, Stephen Gallagher wrote:
I'm not sure what the utility of this is. nsupdate in Fedora already has
support for GSS-TSIG.
For an example of its use,
http://freeipa.org/page/Dynamic_updates_with_GSS-TSIG#Configuring_the_client
Does this nsupdate-gss feature do
Hi, due to a shift in requirements and time constrains I just orphanned
or am about to orphan the following:
About to orphan in a couple of days:
rubygem-bacon -- A ruby-based testing framework
rubygem-configuration -- Pure Ruby scoped configuration files
rubygem-diff-lcs -- Provide a list of
On 06/30/2010 08:29 AM, Trever L. Adams wrote:
On 06/30/2010 05:01 AM, Stephen Gallagher wrote:
I'm not sure what the utility of this is. nsupdate in Fedora already has
support for GSS-TSIG.
For an example of its use,
A file has been added to the lookaside cache for perl-GPS-OID:
8de80ba7f41075a7514e9a3aa9d3b9fb GPS-OID-0.07.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
Author: spot
Update of /cvs/pkgs/rpms/perl-GPS-OID/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv10699/devel
Modified Files:
.cvsignore sources
Added Files:
import.log perl-GPS-OID.spec
Log Message:
import
--- NEW FILE import.log ---
Author: spot
Update of /cvs/pkgs/rpms/perl-GPS-PRN/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv11408
Added Files:
dead.package
Removed Files:
Makefile perl-GPS-PRN.spec sources
Log Message:
package dead, renamed to perl-GPS-OID
--- NEW FILE dead.package ---
Package perl-GPS-PRN in Fedora devel has been retired by spot
To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/acls/name/perl-GPS-PRN
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
On 06/30/2010 06:31 AM, Simo Sorce wrote:
NetworkManger has support for running scripts when an interface comes
up (goes down), read the docs, it should be easy to create your
nsupdate script and drop it in the right place.
Simo.
I am looking at that and dhcp documentation now. My
Author: tremble
Update of /cvs/pkgs/rpms/perl-Test-YAML-Valid/EL-6
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv12703
Modified Files:
perl-Test-YAML-Valid.spec
Log Message:
Fix Source URL
Index: perl-Test-YAML-Valid.spec
On Wed, Jun 30, 2010 at 8:06 AM, Chen Lei supercyp...@gmail.com wrote:
2010/6/30 Michael Schwendt mschwe...@gmail.com:
On Wed, 30 Jun 2010 17:21:37 +0800, Chen wrote:
libjpeg is split into libjpeg-turbo and libjpeg-turbo-utils, Obsoletes
libjpeg is already added to libjpeg-turbo-utils.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=563935
Fedora Update System upda...@fedoraproject.org changed:
What|Removed |Added
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=592101
--- Comment #12 from Fedora Update System upda...@fedoraproject.org
2010-06-30 10:26:17 EDT ---
mldonkey-3.0.2-1.el5 has been
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=601232
Fedora Update System upda...@fedoraproject.org changed:
What|Removed |Added
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=601232
--- Comment #13 from Fedora Update System upda...@fedoraproject.org
2010-06-30 10:26:00 EDT ---
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=592101
Fedora Update System upda...@fedoraproject.org changed:
What|Removed |Added
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=601232
--- Comment #12 from Fedora Update System upda...@fedoraproject.org
2010-06-30 10:25:31 EDT ---
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=601232
Fedora Update System upda...@fedoraproject.org changed:
What|Removed |Added
On Wed, 2010-06-30 at 10:04 -0400, Rich Mattes wrote:
So this is a bug with yum not handling package obsoletes correctly
when it processes the libjpeg.so.62 dep for graphviz?
I suspect the problem is that libjpeg-turbo does not _provide_ libjpeg.
So yum does:
1. pkg XYZ requires libjpeg
2.
On Wed, 2010-06-30 at 11:11 -0400, James Antill wrote:
On Wed, 2010-06-30 at 10:04 -0400, Rich Mattes wrote:
So this is a bug with yum not handling package obsoletes correctly
when it processes the libjpeg.so.62 dep for graphviz?
I suspect the problem is that libjpeg-turbo does not
On Wed, 30 Jun 2010 11:16:11 -0400, seth wrote:
On Wed, 2010-06-30 at 11:11 -0400, James Antill wrote:
On Wed, 2010-06-30 at 10:04 -0400, Rich Mattes wrote:
So this is a bug with yum not handling package obsoletes correctly
when it processes the libjpeg.so.62 dep for graphviz?
Luke Macken lmac...@redhat.com writes:
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community member.
Even for security updates? My experience says that this requirement
will prevent me from *ever* pushing updates. Case
Tom Lane wrote:
Even for security updates? My experience says that this requirement
will prevent me from*ever* pushing updates. Case in point: libtiff,
which is a critpath package, has been in testing with a significant
security update for a week now. Its karma is still zero. When I get
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
Luke Macken lmac...@redhat.com writes:
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community member.
Even for security updates? My experience says that this
On 06/30/2010 06:18 PM, Adam Williamson wrote:
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
The proposed policy might be workable if we had a surplus of
proventester manpower available, but we obviously have not got that.
And you think re-allocating the already scarce manpower to this
On Wed, Jun 30, 2010 at 11:35:17AM -0400, Tom Lane wrote:
Luke Macken lmac...@redhat.com writes:
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community member.
Even for security updates? My experience says that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 9:31 AM, Ralf Corsepius wrote:
On 06/30/2010 06:18 PM, Adam Williamson wrote:
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
The proposed policy might be workable if we had a surplus of
proventester manpower available, but we
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
I would be willing to accept *negative* karma from more than
one proventester as being an override. But it is utterly unacceptable
for inaction to represent a veto.
I would argue that it's utterly unacceptable for untested code to be
pushed
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: cduce : does not adhere to Static Library Packaging Guidelines
https://bugzilla.redhat.com/show_bug.cgi?id=609600
Summary: cduce : does not adhere to Static
James Antill wrote:
# repoquery --repoid=rawhide --provides libjpeg-turbo-utils | fgrep .so.
# /usr/bin/yum --disablerepo=\* --enablerepo=rawhide \
--installroot /tmp/mock-tst install graphviz
[...]
-- Processing Dependency: libjpeg.so.62()(64bit) for package:
Rex Dieter wrote:
James Antill wrote:
# repoquery --repoid=rawhide --provides libjpeg-turbo-utils | fgrep .so.
# /usr/bin/yum --disablerepo=\* --enablerepo=rawhide \
--installroot /tmp/mock-tst install graphviz
[...]
-- Processing Dependency: libjpeg.so.62()(64bit) for package:
On Wed, Jun 30, 2010 at 12:10:11 -0500,
Rex Dieter rdie...@math.unl.edu wrote:
Another wrinkle here is both libjpeg and libjpeg-turbo existing in
rawhide/repo. Shouldn't libjpeg get removed now? Doing so should help
matters too.
If someone looks at that, they might also want to look at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 10:48 AM, Ralf Corsepius wrote:
My perception is: marketing has directed into a direction which drains
away man-power into an uncertain process whose only immediate effect is
bureaucracy, whose long term outcome is uncertain and who
A file has been added to the lookaside cache for perl-Test-YAML-Meta:
9f7db9e1699e25bb254315141ef9306c Test-YAML-Meta-0.16.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
Luke Macken lmac...@redhat.com writes:
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community member.
Even for security updates? My experience says that this
Author: tremble
Update of /cvs/pkgs/rpms/perl-Test-YAML-Meta/EL-6
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv26211
Modified Files:
.cvsignore perl-Test-YAML-Meta.spec sources
Log Message:
Update to latest version before initial build
Index: .cvsignore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 11:09 AM, Ralf Corsepius wrote:
On 06/30/2010 07:58 PM, Jesse Keating wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 10:48 AM, Ralf Corsepius wrote:
My perception is: marketing has directed into a direction which
On Wed, 2010-06-30 at 11:25 -0700, Jesse Keating wrote:
Well yes, you always can be relied upon for the cheery optimistic
outlook :)
If I were perceiving competence in Fedora's leadership, my comments
would sound differently.
You're welcome to try your hand at leadership, or find a
On Tue, 2010-06-29 at 18:37 -0400, Luke Macken wrote:
proventesters strict critical path update handling
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community
2010/7/1 Bruno Wolff III br...@wolff.to:
On Wed, Jun 30, 2010 at 12:10:11 -0500,
Rex Dieter rdie...@math.unl.edu wrote:
Another wrinkle here is both libjpeg and libjpeg-turbo existing in
rawhide/repo. Shouldn't libjpeg get removed now? Doing so should help
matters too.
If someone looks
Adam Williamson awill...@redhat.com writes:
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
The proposed policy might be workable if we had a surplus of
proventester manpower available, but we obviously have not got that.
See above, you cannot judge this on current experience.
Yes I can.
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Adam Williamson awill...@redhat.com writes:
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
The proposed policy might be workable if we had a surplus of
proventester manpower available, but we obviously have not got that.
See above,
Will Woods wwo...@redhat.com writes:
Is it really so hard for you to find someone to test the thing? If so,
maybe you could use the assistance of a co-maintainer?
Huh? I don't need a co-maintainer, I need testers. proventesters,
even. Or are you suggesting that the way to deal with this is
Michael Cronenworth m...@cchtml.com writes:
Should the bodhi whine mail be CC'd to the test mailing list in a
digest-type mail like the updates-testing pushes?
+1. As is, old-package whine mail is going to be directed to somebody
who *isn't allowed to do anything about it*. A more
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Adam Williamson awill...@redhat.com writes:
On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
The proposed policy might be workable if we had a surplus of
proventester manpower available, but we obviously have not got that.
See above,
On Wed, 2010-06-30 at 15:08 -0400, Tom Lane wrote:
Will Woods wwo...@redhat.com writes:
Is it really so hard for you to find someone to test the thing? If so,
maybe you could use the assistance of a co-maintainer?
Huh? I don't need a co-maintainer, I need testers.
I was suggesting that -
Will Woods wwo...@redhat.com writes:
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Yes I can. I have two critpath packages that are in testing with
security bugs, both pretty small and easy to test, and both still have
karma zero. That seems to me to be adequate proof that there's not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/30/2010 03:29 PM, Tom Lane wrote:
Will Woods wwo...@redhat.com writes:
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Yes I can. I have two critpath packages that are in testing with
security bugs, both pretty small and easy to test,
On Wed, Jun 30, 2010 at 8:29 PM, Tom Lane t...@redhat.com wrote:
Will Woods wwo...@redhat.com writes:
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Yes I can. I have two critpath packages that are in testing with
security bugs, both pretty small and easy to test, and both still have
On Wed, Jun 30, 2010 at 8:37 PM, Stephen Gallagher sgall...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/30/2010 03:29 PM, Tom Lane wrote:
Will Woods wwo...@redhat.com writes:
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Yes I can. I have two critpath
On Wed, 2010-06-30 at 15:37 -0400, Stephen Gallagher wrote:
A suggestion: when critical path updates hit updates-testing, a
notification should go to both devel@lists.fedoraproject.org and
q...@lists.fedoraproject.org to encourage testing.
This would probably be too high traffic. We're
On Wed, Jun 30, 2010 at 03:37:11PM -0400, Stephen Gallagher wrote:
A suggestion: when critical path updates hit updates-testing, a
notification should go to both devel@lists.fedoraproject.org and
q...@lists.fedoraproject.org to encourage testing.
The qa-list has already lost a lot of it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 12:29 PM, Tom Lane wrote:
Will Woods wwo...@redhat.com writes:
On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
Yes I can. I have two critpath packages that are in testing with
security bugs, both pretty small and easy to test, and
On Thu, Jun 24, 2010 at 11:28:16AM -0700, Adam Williamson wrote:
* The desktop default update manager must not periodically check for
updates when the system is booted live, but must periodically check for
updates when running on an installed system
tangentally related:
Do we ever
On Wed, Jun 30, 2010 at 4:49 PM, Dave Jones da...@redhat.com wrote:
On Thu, Jun 24, 2010 at 11:28:16AM -0700, Adam Williamson wrote:
* The desktop default update manager must not periodically check for
updates when the system is booted live, but must periodically check for
updates
Hello,
I've been watching the discussion in the bodhi thread. As a long time fedora
/ redhat system user (since 0.5.1). Recently I've been getting myself involved
in the community, packaging and what not. I have watched the discussions
related to testing for the last few releases. I
On Wed, Jun 30, 2010 at 10:03 PM, Michael Cronenworth m...@cchtml.com wrote:
Nathanael Noblet wrote:
#1) Easy way to know where a package came from.
man repoquery
#2 ) Easy way to downgrade if I were to run into problems
yum downgrade packagename
#3) Reminders
bodhi -T
#4) Easy way to
On Jun 30, 2010, at 3:03 PM, Michael Cronenworth wrote:
Nathanael Noblet wrote:
#1) Easy way to know where a package came from.
man repoquery
#2 ) Easy way to downgrade if I were to run into problems
yum downgrade packagename
#3) Reminders
bodhi -T
I presume a fedora account with
On Wed, 2010-06-30 at 16:49 -0400, Dave Jones wrote:
On Thu, Jun 24, 2010 at 11:28:16AM -0700, Adam Williamson wrote:
* The desktop default update manager must not periodically check for
updates when the system is booted live, but must periodically check for
updates when running on
On Wed, 2010-06-30 at 14:59 -0600, Nathanael Noblet wrote:
#1) Easy way to know where a package came from.
For example, as far as I am aware, I cannot query anything that tells
me X packages are from Y repo. If I were to become a 100% always
enabled updates-testing, most of my
Nathanael Noblet wrote:
I presume a fedora account with certs are required for this?
Yes, but for your karma to have any merit, you need a Fedora account.
Non-Fedora account karma does not count.
I agree a GUI would be nice for all of this, and I would be willing to
create one, but time has
On Jun 30, 2010, at 3:44 PM, Michael Cronenworth wrote:
Nathanael Noblet wrote:
I presume a fedora account with certs are required for this?
Yes, but for your karma to have any merit, you need a Fedora account.
Non-Fedora account karma does not count.
Yup, and that's fine, just making
https://bugzilla.redhat.com/show_bug.cgi?id=609590 - main bug - 10
different patches attached
https://bugzilla.redhat.com/show_bug.cgi?id=602530 - split off from main bug
https://bugzilla.redhat.com/show_bug.cgi?id=602531 - split off from main bug
--
389-devel mailing list
On Wed, Jun 30, 2010 at 04:44:37PM -0500, Michael Cronenworth wrote:
Nathanael Noblet wrote:
I presume a fedora account with certs are required for this?
Yes, but for your karma to have any merit, you need a Fedora account.
Non-Fedora account karma does not count.
Actually bodhi -T seems
On Wed, Jun 30, 2010 at 10:07:03PM +0100, mike cloaked wrote:
Or if you have updates-testing off by default but want to test a
specific package then yum --enablerepo updates-testing update foo will
do it for the package foo that you want to test
And if you have non Fedora repos enabled, yum
On Wed, Jun 30, 2010 at 12:50:53PM -0700, Adam Williamson wrote:
On Wed, 2010-06-30 at 15:37 -0400, Stephen Gallagher wrote:
A suggestion: when critical path updates hit updates-testing, a
notification should go to both devel@lists.fedoraproject.org and
q...@lists.fedoraproject.org to
Jesse Keating jkeat...@j2solutions.net writes:
On 6/30/10 12:29 PM, Tom Lane wrote:
I mentioned libtiff in my first comment in this thread. The other one
is libpng. But in any case, are maintainers supposed to have to scare
up testers on their own? Especially for packages that are supposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/30/10 3:38 PM, Tom Lane wrote:
Jesse Keating jkeat...@j2solutions.net writes:
On 6/30/10 12:29 PM, Tom Lane wrote:
I mentioned libtiff in my first comment in this thread. The other one
is libpng. But in any case, are maintainers supposed to
Luke Macken wrote:
Critical path package[0] updates now require positive karma from two
proventesters[1], and a single +1 from one other community member.
Why two? The policy FESCo voted said one (plus one other community member,
giving a total karma of 2).
Kevin Kofler
--
devel
Some of these require yum/yum-utils from rawhide...
On Wed, 2010-06-30 at 14:59 -0600, Nathanael Noblet wrote:
#1) Easy way to know where a package came from.
For example, as far as I am aware, I cannot query anything that tells
me X packages are from Y repo. If I were to become a
Adam Williamson wrote:
...or convince enough others of your position that they will vote for
the candidates you favour in our leadership elections. Since there've
been several of these since you first stated you don't approve of
Fedora's leadership, it seems the electorate doesn't agree with
On Thu, 2010-07-01 at 00:20 +0200, Till Maas wrote:
On Wed, Jun 30, 2010 at 12:50:53PM -0700, Adam Williamson wrote:
You can already view all pending critpath updates in Bodhi's web
interface and command line client, as per Luke's initial mail.
But a yum enhancement or plugin to restrict
On Thu, 2010-07-01 at 06:29 +0200, Kevin Kofler wrote:
Adam Williamson wrote:
...or convince enough others of your position that they will vote for
the candidates you favour in our leadership elections. Since there've
been several of these since you first stated you don't approve of
Jesse Keating wrote:
One of the big reasons the manpower was scarce is we did not have a
proper system to locate, train, and promote new people into this
manpower. The QA team has made great strides into fixing that and we
do now have a process in place, and a good stream of incoming people
Adam Williamson wrote:
I'd remind you that we've actually already had a period of several weeks
where this system was active - before the F13 release, when critpath
package pushes required feedback from a member of qa or releng - and
that worked out fine, the packages got pushed and we did the
Jesse Keating wrote:
There is a slight wrinkle in that right now, the bodhi code will
automatically request a push of an item that reaches this karma threshold,
and I don't believe there is a way yet to force it to wait for even
greater amounts of karma. I believe that fine grained tuning of
Tom Lane wrote:
The right way to go about this is to ramp up proventester manpower
first before making it a required gating factor.
+1
Why was this implemented BEFORE proventester requests were approved? If we
don't even have the mentoring process defined, then that should have
happened
I wrote:
Why two? The policy FESCo voted said one (plus one other community member,
giving a total karma of 2).
Nevermind, I just noticed the later mail from Luke correcting this.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
Dave Airlie wrote:
So in your mind, there is a majority of people on your side, but they
are just too lazy to stand for election and take over the board?
s/too lazy/too busy doing actual work/
(as opposed to wasting their time with politics or bureaucracy)
Have you noticed that all the people
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: perl-Perl-Critic-1.108 is available
https://bugzilla.redhat.com/show_bug.cgi?id=609440
Summary: perl-Perl-Critic-1.108 is available
Product: Fedora
perl-Data-Alias has broken dependencies in the rawhide tree:
On x86_64:
perl-Data-Alias-1.07-6.fc13.x86_64 requires perl(:MODULE_COMPAT_5.10.1)
On i386:
perl-Data-Alias-1.07-6.fc13.i686 requires perl(:MODULE_COMPAT_5.10.1)
Please resolve this as soon as possible.
--
Fedora
perl-DBI-Dumper has broken dependencies in the rawhide tree:
On x86_64:
perl-DBI-Dumper-2.01-8.fc12.x86_64 requires perl(:MODULE_COMPAT_5.10.0)
On i386:
perl-DBI-Dumper-2.01-8.fc12.i686 requires perl(:MODULE_COMPAT_5.10.0)
Please resolve this as soon as possible.
--
Fedora
perl-Pugs-Compiler-Rule has broken dependencies in the rawhide tree:
On x86_64:
perl-Pugs-Compiler-Rule-0.37-4.fc13.noarch requires
perl(:MODULE_COMPAT_5.10.1)
On i386:
perl-Pugs-Compiler-Rule-0.37-4.fc13.noarch requires
perl(:MODULE_COMPAT_5.10.1)
Please resolve this as soon
A file has been added to the lookaside cache for perl-Test-YAML-Valid:
553374b7e9f906e005b979e1d6853708 Test-YAML-Valid-0.04.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
Author: tremble
Update of /cvs/pkgs/rpms/perl-Test-YAML-Valid/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv8172
Modified Files:
.cvsignore perl-Test-YAML-Valid.spec sources
Log Message:
Update to latest version
Index: .cvsignore
97 matches
Mail list logo
