Broken dependencies with Fedora 12 + updates-testing - 2009-12-05
by Michael Schwendt
======================================================================
The results in this summary consider Test Updates!
======================================================================
Summary of broken packages (by src.rpm name):
libmthca
linuxwacom
lsvpd
mingw32-plib
msp430-libc
php-ZendFramework
whatsup
======================================================================
Broken packages in fedora-12-i386:
libmthca-devel-static-1.0.5-3.fc12.i686 requires libmthca = 0:1.0.5-3.fc12
libnodeupdown-backend-openib-1.9-2.fc12.i686 requires libosmvendor.so.2(OSMVENDOR_2.0)
libnodeupdown-backend-openib-1.9-2.fc12.i686 requires libosmvendor.so.2
lsvpd-1.6.5-3.fc12.i686 requires libvpd_cxx-2.1.so.2
php-ZendFramework-tests-1.8.4-3.PL1.fc12.noarch requires php-ZendFramework = 0:1.8.4-3.PL1.fc12
======================================================================
Broken packages in fedora-12-ppc:
libmthca-devel-static-1.0.5-3.fc12.ppc requires libmthca = 0:1.0.5-3.fc12
libnodeupdown-backend-openib-1.9-2.fc12.ppc requires libosmvendor.so.2(OSMVENDOR_2.0)
libnodeupdown-backend-openib-1.9-2.fc12.ppc requires libosmvendor.so.2
lsvpd-1.6.5-3.fc12.ppc requires libvpd_cxx-2.1.so.2
php-ZendFramework-tests-1.8.4-3.PL1.fc12.noarch requires php-ZendFramework = 0:1.8.4-3.PL1.fc12
======================================================================
Broken packages in fedora-12-ppc64:
libmthca-devel-static-1.0.5-3.fc12.ppc64 requires libmthca = 0:1.0.5-3.fc12
libnodeupdown-backend-openib-1.9-2.fc12.ppc64 requires libosmvendor.so.2(OSMVENDOR_2.0)(64bit)
libnodeupdown-backend-openib-1.9-2.fc12.ppc64 requires libosmvendor.so.2()(64bit)
lsvpd-1.6.5-3.fc12.ppc64 requires libvpd_cxx-2.1.so.2()(64bit)
php-ZendFramework-tests-1.8.4-3.PL1.fc12.noarch requires php-ZendFramework = 0:1.8.4-3.PL1.fc12
======================================================================
Broken packages in fedora-12-x86_64:
libmthca-devel-static-1.0.5-3.fc12.x86_64 requires libmthca = 0:1.0.5-3.fc12
libnodeupdown-backend-openib-1.9-2.fc12.x86_64 requires libosmvendor.so.2(OSMVENDOR_2.0)(64bit)
libnodeupdown-backend-openib-1.9-2.fc12.x86_64 requires libosmvendor.so.2()(64bit)
lsvpd-1.6.5-3.fc12.x86_64 requires libvpd_cxx-2.1.so.2()(64bit)
php-ZendFramework-tests-1.8.4-3.PL1.fc12.noarch requires php-ZendFramework = 0:1.8.4-3.PL1.fc12
======================================================================
Broken packages in fedora-updates-12-ppc64:
msp430-libc-0-3.20090726cvs.fc12.noarch requires msp430-gcc
======================================================================
Broken packages in fedora-updates-testing-12-i386:
linuxwacom-devel-0.8.2.2-17.fc12.i686 requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.i686 requires libwacomcfg.so.0
mingw32-plib-static-1.8.5-0.fc12.noarch requires mingw32-plib = 0:{version}-{release}
======================================================================
Broken packages in fedora-updates-testing-12-ppc:
linuxwacom-devel-0.8.2.2-17.fc12.ppc requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.ppc requires libwacomcfg.so.0
linuxwacom-devel-0.8.2.2-17.fc12.ppc64 requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.ppc64 requires libwacomcfg.so.0()(64bit)
mingw32-plib-static-1.8.5-0.fc12.noarch requires mingw32-plib = 0:{version}-{release}
======================================================================
Broken packages in fedora-updates-testing-12-ppc64:
linuxwacom-devel-0.8.2.2-17.fc12.ppc64 requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.ppc64 requires libwacomcfg.so.0()(64bit)
mingw32-plib-static-1.8.5-0.fc12.noarch requires mingw32-plib = 0:{version}-{release}
======================================================================
Broken packages in fedora-updates-testing-12-x86_64:
linuxwacom-devel-0.8.2.2-17.fc12.i686 requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.i686 requires libwacomcfg.so.0
linuxwacom-devel-0.8.2.2-17.fc12.x86_64 requires linuxwacom = 0:0.8.2.2-17.fc12
linuxwacom-devel-0.8.2.2-17.fc12.x86_64 requires libwacomcfg.so.0()(64bit)
mingw32-plib-static-1.8.5-0.fc12.noarch requires mingw32-plib = 0:{version}-{release}
14 years, 4 months
Re: Fedora release criteria completely revised
by Adam Williamson
On Tue, 2009-12-08 at 09:19 -0500, Colin Walters wrote:
> Hi Adam,
>
> Looks really great in general!
Thanks!
> One specific comment, for Final 9; I
> think we need a more specific definition of "and subsequent login".
> Does that mean that you just type your username/password and look at
> the default desktop?
This is what it was intended to mean, actually running apps I would have
defined as 'login and use'. How would you suggest wording a
clarification?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 4 months
Re: Fedora release criteria completely revised
by Adam Williamson
On Tue, 2009-12-08 at 10:52 +0100, Andy Green wrote:
> On 12/07/09 23:55, Somebody in the thread at some point said:
>
> Hi -
>
> > these pages, not nice-to-haves. You must be able to commit to the idea
> > that, if any criterion on the page is not met, we would slip the release in
> > question.
>
> I think it's great you guys are looking to increase
> Quality-with-a-capital-Q.
>
> ''9 There must be no SELinux 'AVC: denied' messages or abrt crash
> notifications on initial boot and subsequent login''
>
> https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria
>
> It might be wise to specify on what particular set of test machines or
> platforms you want to see not abrt stuff from. Because current F12
> kernels kill a 4-core box here and iwlagn gives abrt warnings on this
> laptop, but it's still otherwise fine as a released kernel.
>
> It's not realistic to hold a release until the kernel never crashes on
> any platform.
Luckily, we have a tailor-made get-out clause for that one (actually I
pointed out the same problem as you, and wrote it, shortly before
FUDCon):
https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_lo...
I'll turn that criterion into a 'in most cases' one with a link to that
FAQ entry, as we did for the other similar criteria. Thanks.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 4 months
DHCP 4 and ldap messages
by Scott Robbins
I did some cursory googling for this, as well as a brief look at isc.org
but didn't see anything non-Fedora specific on this.
In F12 and F13, when one starts the dhcp server daemon, a
message is given:
Not searching LDAP since ldap-server, ldap-port, ldap-username,
ldap-password and ldap-baes-dn were not specified in the config file.
Is this a standard dhcp-4 thing, or a Fedora-ism.
There's no mention of LDAP in the dhcpd.conf(5) man page. I know there
used to be a separate dhcp-ldap package (at least in CentOS). (I also
see that the man page seems to be a general ISC one, not Fedora's.)
It's not an error per se, DHCPD still works.
I don't see mention of it in the release notes. (I didn't scour them
thoroughly, I just glanced at the changes for sysadmins.)
Might be worth a mention, if only to avoid confusion--at least one
person on the forums figured they'd broken something.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Spike: We like to talk big... vampires do. 'I'm going to destroy
the world.' That's just tough-guy talk. Strutting around with
your friends over a pint of blood. The truth is, I _like_ this
world. You've got...dog racing, Manchester United. And you've
got people. Billions of people walking around like Happy Meals
with legs. It's all right here. But then someone comes along
with a vision. With a real... passion for destruction. Angel
could pull it off. Good-bye, Picadilly. Farewell,
Leicester-bloody-Square.
14 years, 4 months
Introduction
by Jerome Whyte
Hello Zappers,
My name is Jerome Ian Patrick, my irc nickname is patrickian.
I am familiar with fedora in the sense that I have been using it since FC1,
and before that red hat linux. However, this has been purely functional,
and I haven't delved into its' guts. I have for sometime wanted to contribute
to the operating system that I have used for the last decade so I am starting here.
I have recently finished school at York University, in Toronto, and am familiar with
C++, Java, and FORTRAN (yes people still use fortran).
I am looking forward to contributing, thanks,
Pats
14 years, 4 months
New BugZapper Introduction
by Chris Byrd
Hello,
My name is Chris Byrd (irc nick: cbyrda). I am following the instructions
at http://fedoraproject.org/wiki/BugZappers/Joining in the hopes of being
able to contribute to bug triage.
I have been a Fedora user since Core 4, although I was a Linux user prior to
that (SuSe and Mandrake). I came to Fedora just to give it a spin and I
liked it so much it has been my primary distro since. Fedora just feels
like home and I'd like to take the next step and contribute where I can. I
live on the west coast of the United States (in California) where I work as
a software engineer. Most often I'm writing Java code these days but I have
had occasion to write C++, C# and python code in the past. I hope that I
can be of some help in the triage group and that eventually as I get more
experience with Fedora and its community that I might find other ways to
contribute. I have tried to follow the linked instructions above as closely
as possible, if I have missed something please let me know and I'll correct
it.
If I am admitted to the triage group I would very much appreciate some
advice from existing triage veterans on how I can best come up to speed and
become productive. I hope to hear back from the group and I hope I can
help.
Chris Byrd
cbyrda(a)gmail.com
cbyrda @ irc.freenode.net
14 years, 4 months
Is there information on the status of rawhide?
by Bruno Wolff III
It's been 5 days since the last rawhide compose. So far I have seen one
message mentioning a compose failure. Is there some more information on
when it is likely for composes to start appearing again?
14 years, 4 months
Ralink wireless interface
by James W. Bennett
I am trying to use my Ralink 2561 chip set on Fedora 12. I have tried
using dhcp and the address I get is 10.43.42.0 which is good address but
could not have gotten the address from my router because it delivers ip
address of 192.168.0.100 to 192.168.0.199. I have tried to use static
address but still 10.43.42.0. Now is that a default address, that is not
use able to me. My router will not except 10.43.42.0 addresses. Fedora
11 works as it should. I get a 192.168.0.* addresses. I wish I had
tested this sooner. I didn't do that. I will test sooner on 13.
Does anyone else have same or similar problem.
Thank You
Jim Bennett
14 years, 4 months