Dear All.
Recently I checked powertop and the first lines are:
100.0% Device Audio codec hwC0D0:
Realtek
100.0% Device Audio codec hwC0D3:
Intel
I remember that it was only Intel codec.
Do I really need - Audi
Am 23.10.2011 04:14, schrieb Kevin Kofler:
> Jim Meyering wrote:
>> glibc-2.14.90-12.999, which has just made it to stable provokes
>> a hard-to-diagnose (for me at least) problem.
>>
>> While most things work, and it fixed two problems that affected
>> me, it caused me some frustration:
>>
>> ht
Compose started at Sun Oct 23 08:15:43 UTC 2011
Broken deps for x86_64
--
aeolus-all-0.4.0-1.fc16.noarch requires rubygem(aeolus-cli)
aeolus-conductor-0.4.0-1.fc16.noarch requires rubygem(oauth)
aeolus-conductor-devel-
Ok, as long as my sound "onboard" I disabled it, rebooted and enabled it again.
So now I got in /sys/devices/pci:00/:00:1b.0/label only:
Realtek High Definition Audio Device
Where is my Intel HDA ?
lspci:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family
High
Hello,
I am replying to let you know that I succeeded in building gwaei. It
took a fair bit of effort to get it going, because apparently the
configure script that comes with gWaei doesn't properly pick up on
64-bit libraries (or Fedora's or the maintainer's gtk+-3 pkgconfig
wasn't sane, or *somet
Please review the critical path update=20
https://admin.fedoraproject.org/updates/FEDORA-2011-14614
We're right up against the last minute to get these fixes in to ensure
that all of these features work properly from the install DVD. We very
desperately need testers (including one proventester, du
I'm following the procedure at:
http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
Does anyone know how to contact Gary T. Giesen?
I've sent him an email (also CCed on this one) a few months ago
requesting co-maintainer status for daemonize without a response.
Gary has t
Kevin Kofler wrote:
> Jim Meyering wrote:
>> glibc-2.14.90-12.999, which has just made it to stable provokes a
>> hard-to-diagnose (for me at least) problem.
>>
>> While most things work, and it fixed two problems that affected me,
>> it caused me some frustration:
>>
>> https//bugzilla.redhat.c
sön 2011-10-23 klockan 17:04 -0500 skrev Rex Dieter:
> The fail(*), imo, was with 12.999 going stable containing known-regressions.
> So, any suggestions, if any, to prevent any similar series of events?
My suggestions:
Disable automatic push to stable when there is any negative karma,
requiri
Hi.
There is a project named SOS in Fedora collection on Transifex. I'd like to
know if there is anyone maintaining it, because it seems like it needs to be
translated, but there is no maintainer assigned in Tx and no translation team
creation request has been fulfilled in 7 months. The latest
The current packaging guidelines require packages that update from sysv
init scripts to systemd scripts to provide conversion triggers that are
fired on the basis of an NVR comparison:
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Packages_migrating_to_a_systemd_unit_file_from_a_SysV_i
Linux rawhide.vmware.local 3.1.0-0.rc9.git0.0.fc17.x86_64 #1 SMP Wed Oct 5
14:37:47
this is the last kernel booting in vmware for me
all following see screenshot
--
Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / c
Camilo Mesias mesias.co.uk> writes:
>
> Hi,
>
> I tried some of these changes and they seemed to work reasonably well
> apart from the grub2 infrastructure is still a bit immature at running
> without initrd... specifically
> ...
> I'm not sure where to report this? Bugs against grub2 or somet
Tom Lane wrote:
> The current packaging guidelines require packages that update from sysv
> init scripts to systemd scripts to provide conversion triggers that are
> fired on the basis of an NVR comparison:
>
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Packages_migrating_to_a_system
WHAT: Fedora QA Meeting
WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT)
WHERE: #fedora-meeting
It's meeting time again! This one will likely turn into a blocker review
meeting, as we have the F16 RC due on Tuesday.
If anyone has anything to add to the agenda, please reply to this mail,
and whoever ends up
On 10/23/2011 07:47 PM, Henrik Nordström wrote:
> Disable automatic push to stable when there is any negative karma,
> requiring the package maintainer to initiate the push even if karma
> kriteria have been met.
This idea has been suggested:
https://fedorahosted.org/bodhi/ticket/618
--
devel mai
On 23 Oct 2011 00:18, "Reindl Harald" wrote:
>
> Linux rawhide.vmware.local 3.1.0-0.rc9.git0.0.fc17.x86_64 #1 SMP Wed Oct 5
14:37:47
>
> this is the last kernel booting in vmware for me
> all following see screenshot
It seems that the initramfs does not find any drives. Can you check if the
drive
On Sun, 2011-10-23 at 04:14 +0200, Kevin Kofler wrote:
> The fact that a glibc with showstoppers of this kind got pushed to stable
> shows that the karma system does not work at all. It just hinders getting
> legitimate fixes out and does nothing to stop regressions. glibc is even
> critpath, y
On Mon, 2011-10-24 at 02:47 +0200, Henrik Nordström wrote:
> Don't automatically push to stable until at least X days (3?) have
> passed, enabling sufficient time for regressions to be detected. Package
> maintainer can initiate push earlier by "Push to stable" if needed and
> confident there is n
On Sun, 2011-10-23 at 17:04 -0500, Rex Dieter wrote:
> The fail(*), imo, was with 12.999 going stable containing known-regressions.
> So, any suggestions, if any, to prevent any similar series of events?
We have lots of suggestions. As I've said at least fifty times, it's
pointless going too fa
On 10/24/2011 03:52 AM, Tom Lane wrote:
> I'm really getting to the point where that's a completely unacceptable
> restriction. I've already blown off one mysql bug-fix release in F15
> because of this restriction, and I see they just released another one
> that I'll be unable to ship in F15 becau
On Sun, 2011-10-23 at 23:43 -0700, Adam Williamson wrote:
> On Sun, 2011-10-23 at 04:14 +0200, Kevin Kofler wrote:
>
> > The fact that a glibc with showstoppers of this kind got pushed to stable
> > shows that the karma system does not work at all. It just hinders getting
> > legitimate fixes ou
On 10/24/2011 05:42 AM, Kevin Kofler wrote:
> FWIW, what the tomcat6 maintainers did is that they just ignored the
> guideline which says that you cannot migrate to systemd in an update and
> pushed this update:
> https://admin.fedoraproject.org/updates/FEDORA-2011-13456
> (which is already in the
23 matches
Mail list logo
