#154: Tracker: critical path test case creation
--+-
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major| Milestone:
Component: Wiki
Hello!
My name is Andy and I'd like to contribute to the BugZappers.
I was a client/server Windows developer for about 12 years before moving
into IT operations about 6 years ago. For the past 14 months, I've been a
RHEL 5 administrator at Boise State University in the Office of IT.
Overall, I
The following Fedora 13 Security updates need testing:
https://admin.fedoraproject.org/updates/openttd-1.0.5-1.fc13
https://admin.fedoraproject.org/updates/bind-9.7.2-1.P3.fc13,bind-dyndb-ldap-0.1.0-0.10.a1.20091210git.fc13,dnsperf-1.0.1.0-19.fc13
https://admin.fedoraproject.org/updat
The following Fedora 14 Security updates need testing:
https://admin.fedoraproject.org/updates/openttd-1.0.5-1.fc14
https://admin.fedoraproject.org/updates/fontforge-20100501-5.fc14
https://admin.fedoraproject.org/updates/clamav-0.96.5-1400.fc14
https://admin.fedoraproject.org/upda
On Sun, Dec 05, 2010 at 17:43:40 +,
Frank Murphy wrote:
> On 05/12/10 17:35, Bruno Wolff III wrote:
> > On Sun, Dec 05, 2010 at 17:34:33 +,
> >Frank Murphy wrote:
> >> Are packages from updates-testing meant to be signed?
> >> Whether from FN, FN-1.
> >
> > Yes.
>
> How does one wo
On 05/12/10 17:35, Bruno Wolff III wrote:
> On Sun, Dec 05, 2010 at 17:34:33 +,
>Frank Murphy wrote:
>> Are packages from updates-testing meant to be signed?
>> Whether from FN, FN-1.
>
> Yes.
How does one work in an unsigned pks, when using fedora-easy-karma
or would unsigned be ignored
On Sun, Dec 05, 2010 at 17:34:33 +,
Frank Murphy wrote:
> Are packages from updates-testing meant to be signed?
> Whether from FN, FN-1.
Yes.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Are packages from updates-testing meant to be signed?
Whether from FN, FN-1.
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On 05/12/10 16:45, Jon Stanley wrote:
> You can also 'yum install keychecker' which is a somewhat simple
> python script that I wrote to do this and present the data in a
> coherent fashion.
>
> https://fedorahosted.org/keychecker/
Nice Christmas present :)
--
Regards,
Frank Murphy
UTF_8 Enco
On Sun, Dec 5, 2010 at 11:34 AM, Michal Jaegermann wrote:
> In a sense this is only half of an answer as this will show, among
> other things, something like "key ID e8e40fde". Only if you will
> do
>
> rpm -qi gpg-pubkey-e8e40fde
>
> then you will see something which you will likely find info
On Sun, Dec 05, 2010 at 07:04:17PM +0800, Ed Greshko wrote:
> On 12/05/2010 06:21 PM, Frank Murphy wrote:
> > How do I find\know the exact key that signed a package?
> >
> rpm --checksig -v foo.rpm
In a sense this is only half of an answer as this will show, among
other things, something like "key
On 12/05/2010 11:11 AM, Alexander Kurtakov wrote:
> On 01:04:02 pm Sunday, December 05, 2010 Jóhann B. Guðmundsson wrote:
>> On 12/05/2010 12:06 AM, Brendan Jones wrote:
>>> Is it really so bad?
>> Yes and reporters should be able to opt out from this process chooses
>> they do so.
> Well, how abou
Compose started at Sun Dec 5 08:15:15 UTC 2010
Broken deps for x86_64
--
balsa-2.4.9-1.fc15.x86_64 requires libesmtp.so.5()(64bit)
beagle-0.3.9-19.fc14.x86_64 requires libmono.so.0()(64bit)
beagle-0.3.9-19.fc14.x86_64
On 01:04:02 pm Sunday, December 05, 2010 Jóhann B. Guðmundsson wrote:
> On 12/05/2010 12:06 AM, Brendan Jones wrote:
> > Is it really so bad?
>
> Yes and reporters should be able to opt out from this process chooses
> they do so.
Well, how about giving maintainers the power to opt out from having
On 12/05/2010 06:21 PM, Frank Murphy wrote:
> How do I find\know the exact key that signed a package?
>
> Have tried "rpm -Kv foo.rpm"
> but it just bring backs back:
> Header SHA1 digest: OK (yadayada)
> MD5 digest: OK (yadayada)
>
> But what I'm looking for is to end up like:
> https://fedor
How do I find\know the exact key that signed a package?
Have tried "rpm -Kv foo.rpm"
but it just bring backs back:
Header SHA1 digest: OK (yadayada)
MD5 digest: OK (yadayada)
But what I'm looking for is to end up like:
https://fedoraproject.org/keys
Currently used keys
RPM-GPG-KEY-fedora-13
> > There are so many open bugs - anything which helps us zappers out to
> > maintain some kind of continuity is very welcome in my book. What's a
> > few emails every 6 months?
>
> It isn't "a few".
>
i had many f12 bugs which double filled my inbox at f12 end of life. this
happened before with p
On Sun, 05 Dec 2010 10:58:25 +1000, Brendan wrote:
>
>
> On 12/05/2010 10:30 AM, Michael Schwendt wrote:
> > For issues that persist, a different user will [need to] open a new
> > ticket. And who will pay attention and notice that it's the same issue
> > that was closed WONTFIX N*6 months ago?
18 matches
Mail list logo