In current rawhide,
repoquery --whatrequires mod_perl-devel
returns
mod_perl-devel-0:2.0.5-1.fc16.i686
mod_perl-devel-0:2.0.5-1.fc16.x86_64
BackupPC-0:3.1.0-17.fc15.x86_64
MySQL-zrm-0:2.2.0-2.fc15.noarch
Perlbal-0:1.78-1.fc15.noarch
Sprog-0:0.14-20.fc15.noarch
TeXmacs-0:1.0.7.10-1.fc16.x86_64
ac
On 04/10/2011 01:23 PM, Sven Lankes wrote:
> On Sun, Apr 10, 2011 at 12:45:56PM -0400, Doug Ledford wrote:
>
>> And here we are, about to go down the same road again. I have an update
>> in updates-testing, it's getting no love, and the package that's in the
>> release is *known broken*. It has
On Sun, Apr 10, 2011 at 18:19:26 -0700,
Christopher Aillon wrote:
>
> I just realized today for the first time that our nightlies are based on
> stable, not testing. I think that's something we need to address. It's
> probably still useful to have nightlies based on stable, but I think
> i
On 04/10/2011 01:34 PM, Adam Williamson wrote:
> On Sun, 2011-04-10 at 12:45 -0400, Doug Ledford wrote:
>
>> And here we are, about to go down the same road again. I have an update
>> in updates-testing, it's getting no love, and the package that's in the
>> release is *known broken*. It has not
Comment inline below:
Sent from my iPhone
On Apr 10, 2011, at 4:34 PM, Adam Williamson wrote:
> On Sun, 2011-04-10 at 12:45 -0400, Doug Ledford wrote:
>
>> And here we are, about to go down the same road again. I have an update
>> in updates-testing, it's getting no love, and the package that
One of the changes in the updated mdadm package is to ghost /var/run/mdadm and
to create it in the mdmonitor init script and also to set the SELinux state on
the new dir. So while things booted ok for you, monitoring of arrays is DOA in
the version prior to the update.
Sent from my iPhone
On A
That's good to know since I'm now out of contact after tonight. Can someone
close out the erroneous mdadm bug if it's caused by something else then please?
Sent from my iPhone
On Apr 10, 2011, at 4:38 PM, Adam Williamson wrote:
> On Sun, 2011-04-10 at 20:34 +0100, Piscium wrote:
>> On 10 April
Christoph Wickert wrote:
> But I can and I haven't seen any instructions what I should do. I am
> willing to try broken update again in order to provide more info, but I
> can only provide the info I am asked for.
Well, one thing worth testing is trying to figure out what part of kdepim or
Akonad
Am Sonntag, den 10.04.2011, 23:12 +0200 schrieb Kevin Kofler:
> Christoph Wickert wrote:
> > As someone who is still suffering from the KDE 4.6.1 update and who has
> > not received notable support from your or the KDE SIG I object to
> > lowering the test requirements for updates.
>
> Uh, we're d
Christoph Wickert wrote:
> As someone who is still suffering from the KDE 4.6.1 update and who has
> not received notable support from your or the KDE SIG I object to
> lowering the test requirements for updates.
Uh, we're doing what we can about the Akonadi issues. The thing is, we
cannot reprod
On Sun, 2011-04-10 at 21:47 +0100, Peter Robinson wrote:
> I would generally agree with the brokenness of critical path. I
> maintain the libraries that provide support for certain fruit based
> iDevices and for some reason they're classed as crit path where as
> clutter which is one of the core l
On Sat, Apr 9, 2011 at 1:27 AM, Tom Lane wrote:
> For the past several days I've been getting daily nagmails about the
> fact that libtiff hasn't been pushed into f13 (example attached).
> Because it's a critpath package, I as the lowly maintainer do not have
> privileges to push it stable, not ev
On Sun, 2011-04-10 at 20:34 +0100, Piscium wrote:
> On 10 April 2011 20:01, Doug Ledford wrote:
> > The bug I'm looking at right now is specifically against the live image, so
> > no I can't test that with something in updates testing. It needs to make it
> > to the base before it gets on the li
On Sun, 2011-04-10 at 15:01 -0400, Doug Ledford wrote:
> The bug I'm looking at right now is specifically against the live
> image, so no I can't test that with something in updates testing. It
> needs to make it to the base before it gets on the live media to see
> if it solves the problem there.
On Sun, 2011-04-10 at 12:45 -0400, Doug Ledford wrote:
> And here we are, about to go down the same road again. I have an update
> in updates-testing, it's getting no love, and the package that's in the
> release is *known broken*. It has not been updated for systemd to begin
> with. Nor for tm
Am Samstag, den 09.04.2011, 05:32 +0200 schrieb Kevin Kofler:
> Will Woods wrote:
> > The solution is simple: ASK FOR HELP.
>
> The solution is simple: The red tape on update pushing needs to be repealed.
As someone who is still suffering from the KDE 4.6.1 update and who has
not received notable
On 10 April 2011 20:01, Doug Ledford wrote:
> The bug I'm looking at right now is specifically against the live image, so
> no I can't test that with something in updates testing. It needs to make it
> to the base before it gets on the live media to see if it solves the problem
> there.
--
The bug I'm looking at right now is specifically against the live image, so no
I can't test that with something in updates testing. It needs to make it to the
base before it gets on the live media to see if it solves the problem there.
Sent from my iPhone
On Apr 10, 2011, at 1:13 PM, Björn Pers
On Sun, Apr 10, 2011 at 12:45:56PM -0400, Doug Ledford wrote:
> And here we are, about to go down the same road again. I have an update
> in updates-testing, it's getting no love, and the package that's in the
> release is *known broken*. It has not been updated for systemd to begin
> with. Nor
Doug Ledford wrote:
> Now I'm seeing new bugs trickle in about mdadm in the live image, and I
> have no clue if there is something I need to fix because I haven't
> gotten my update pushed to stable yet so these people are running
> against a known broken mdadm. The fixed mdadm makes changes
> spe
On Fri, 2011-04-08 at 21:28 -0500, Bruno Wolff III wrote:
> On Fri, Apr 08, 2011 at 20:43:05 -0400,
> Will Woods wrote:
> >
> > The only thing broken here is the expectation that testing doesn't
> > require your assistance, or isn't your problem.
>
> Except this affects more than Tom. Some peo
Hi,
F15 Apr 9 nightly boots and works, but when attempting to install on drive
it fails
https://bugzilla.redhat.com/show_bug.cgi?id=695098
All this in a virtualbox machine.
Is this a known issue?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listin
Hello Andrea,
On Sun, 2011-04-10 at 15:39 +0200, Andrea Francia wrote:
> Dear Fedora developers,
>I'm the upstream developer of trash-cli.
> I saw in package announce[1] that you decided to change of
> restore-trash into trash-restore.
> I appreciate your work but in this case I'm not happy wi
Dear Fedora developers,
I'm the upstream developer of trash-cli.
I saw in package announce[1] that you decided to change of restore-trash
into trash-restore.
I appreciate your work but in this case I'm not happy with one of the last
change.
I'm preparing [4] a program called trash-restore to be
Compose started at Sun Apr 10 08:15:03 UTC 2011
Broken deps for x86_64
--
GMT-4.5.6-1.fc15.i686 requires libnetcdf.so.6
GMT-4.5.6-1.fc15.x86_64 requires libnetcdf.so.6()(64bit)
HippoDraw-python-1.21.1-14.fc15.x86_64 re
25 matches
Mail list logo
