On Tue, 2013-01-22 at 19:30 -0800, Adam Williamson wrote:
> The 'new style' tracker bug aliases are as follows:
>
> AlphaBlocker
> AlphaFreezeException
> BetaBlocker
> BetaFreezeException
> FinalBlocker
> FinalFreezeException
> Versioned aliases will still be applied to all the tracker bugs, so
The following Fedora 18 Security updates need testing:
Age URL
3
https://admin.fedoraproject.org/updates/FEDORA-2013-1357/dnsmasq-2.65-4.fc18
13
https://admin.fedoraproject.org/updates/FEDORA-2013-1277/python-tw2-jquery-2.0.3-5.fc18
87
https://admin.fedoraproject.org/updates/FEDORA-2
The following Fedora 16 Security updates need testing:
Age URL
55
https://admin.fedoraproject.org/updates/FEDORA-2012-20157/libproxy-0.4.11-1.fc16
3 https://admin.fedoraproject.org/updates/FEDORA-2013-1748/sssd-1.8.6-1.fc16
3
https://admin.fedoraproject.org/updates/FEDORA-2013-1713/l
The following Fedora 17 Security updates need testing:
Age URL
3
https://admin.fedoraproject.org/updates/FEDORA-2013-1734/libupnp-1.6.18-1.fc17
13
https://admin.fedoraproject.org/updates/FEDORA-2013-1244/libexif-0.6.21-2.fc17
13
https://admin.fedoraproject.org/updates/FEDORA-2013-128
On Wed, 23 Jan 2013 11:52:13 -0700
Tim Flink wrote:
> Everything is still very much in the early stages of planning, so
> constructive comments and suggestions (or contributions) would
> certainly be appreciated.
I have the first draft of the form done and up as a demo at:
http://209.132.184.1
On Feb 4, 2013, at 1:35 PM, Michael Cronenworth wrote:
> Chris Murphy wrote:
>> I'm not understanding the problem in the bug.
>
> The "Date/Time" setting is required by anaconda before package
> installation may begin. I wanted to make this an optional setting. In
> order for it to be optional
Chris Murphy wrote:
> I'm not understanding the problem in the bug.
The "Date/Time" setting is required by anaconda before package
installation may begin. I wanted to make this an optional setting. In
order for it to be optional the date/time must be set to something
reasonable from a trusted sour
On Feb 4, 2013, at 11:36 AM, Michael Cronenworth wrote:
> Michael Cronenworth wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=883182
>>
>> I wasn't sure on the component. Feel free to correct. Thanks!
>
> Apparently lorax was incorrect.
>
> Does anyone have any input on what component
#332: Add Fedora 19 Milestones
---+---
Reporter: tflink| Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 19
Component: Blocker
Michael Cronenworth wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=883182
>
> I wasn't sure on the component. Feel free to correct. Thanks!
Apparently lorax was incorrect.
Does anyone have any input on what component this should be filed against?
--
test mailing list
test@lists.fedorapro
On Feb 4, 2013, at 9:01 AM, Adam Jackson wrote:
> If I can abuse this thread for design discussion for a moment, what if
> instead of the grub editor horrorshow for things like this, we had a
> list of debugging tickboxes you could check that appended the right
> thing to kcmdline (and just remem
Hello all,
After many years of using Red Hat Linux and Fedora I'd like to step up and
contribute to the Fedora Project by zapping bugs.
Some weeks ago I reported a KSH bug and found it to be very nice to get it
to be recognized and worked on by people. I would like to give a helping
hand to peopl
Once upon a time, Adam Jackson said:
> If I can abuse this thread for design discussion for a moment, what if
> instead of the grub editor horrorshow for things like this, we had a
> list of debugging tickboxes you could check that appended the right
> thing to kcmdline (and just remember the defa
On Fri, 2013-02-01 at 16:26 -0800, Adam Williamson wrote:
> Just dropping 'nomodeset' from the cmdline should probably do the job.
> It's actually also supposed to write an xorg.conf snippet which forces
> use of the vesa driver, but I believe that mechanism's been broken for a
> while, so you onl
around to last week, mostly.
This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
https://fedoraproject.org/wiki/QA/Meetings/20130204
The current proposed agenda is included below.
== Proposed Agenda Topics ==
1. Criteria Revision
2. Test C
Compose started at Mon Feb 4 08:15:37 UTC 2013
Broken deps for x86_64
--
[bootconf]
bootconf-1.4-6.fc18.noarch requires grub
[compat-gcc-34]
compat-gcc-34-c++-3.4.6-24.fc17.x86_64 requires libstdc++ < 0:4.8.0
[couchdb]
> > And there are dozens of applications out there that used to utilize
> > the UPower signal and haven't been given proper chance to adjust to
> > the "new approach", so they are broken at the moment.
>
> Dozens ? Name them, please. I've fixed the ones I've found (which was
> just NM, really).
F
17 matches
Mail list logo
