date:20151021

Re: To someone with power to push packages on Fedora 21

2015-10-21 Thread Zbigniew Jędrzejewski-Szmek

On Wed, Oct 21, 2015 at 11:18:09AM +0200, Reindl Harald wrote:
> 
> 
> Am 21.10.2015 um 02:22 schrieb Kevin Kofler:
> >Zbigniew Jędrzejewski-Szmek wrote:
> >>The testers write "works for me" or report a new bug. When things work,
> >>there's nothing to evaluate. Doing the counting by hand is just a way to
> >>waste time.
> >
> >10 "works for me" and 1 "deletes all my data" do not make a quality of +9.
> >They mean a package that should be unpushed ASAP and most definitely NEVER
> >be pushed to stable.
True. That's why I usually set the karma thresholds assymetricaly to
+3/-1 or such, if I bother to set it. Arguably the default should
be just -1 for stopping the automatic push.

> >I mostly ignore generic "works for me" feedback with no details. It is not
> >useful
> 
> it *is* useful in case nobody reports a problem because you get the
> confirmation the package not only works for you
Exactly. Automatic karma is certainly imperfect, but it works good enough
most of the time and frees maintainer time to do more interesting things.

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

limb changed wfp's branch request for perl-Regexp-Grammars in epel7 from Awaiting Review to Approved

2015-10-21 Thread notifications

limb changed wfp's branch request for perl-Regexp-Grammars in epel7 from 
Awaiting Review to Approved
https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Grammars/
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

wfp requested branch epel7 for package perl-Regexp-Grammars

2015-10-21 Thread notifications

wfp requested branch epel7 for package perl-Regexp-Grammars
https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Grammars/
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[389-devel] Please Review 48321 Improve is_a_dn check to prevent mistakes with lib389 auth

2015-10-21 Thread William Brown

https://fedorahosted.org/389/ticket/48321

https://fedorahosted.org/389/attachment/ticket/48321/0001-Ticket-48321-
Improve-is_a_dn-check-to-prevent-mistak.patch

-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane



signature.asc
Description: This is a digitally signed message part
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel

Re: To someone with power to push packages on Fedora 21

2015-10-21 Thread Sérgio Basto

On Qua, 2015-10-21 at 02:22 +0200, Kevin Kofler wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > The testers write "works for me" or report a new bug. When things work,
> > there's nothing to evaluate. Doing the counting by hand is just a way to
> > waste time.
> 
> 10 "works for me" and 1 "deletes all my data" do not make a quality of +9. 
> They mean a package that should be unpushed ASAP and most definitely NEVER 
> be pushed to stable.
> 
> I mostly ignore generic "works for me" feedback with no details. It is not 
> useful. I mainly care about whether there was any legitimate negative 
> feedback or not. (Unfortunately, there is also plenty of invalid negative 
> feedback, e.g., regressions that are actually caused by other updates, "does 
> not fix bug #nnn" when it was never claimed to be fixed, etc.)

Kevin, Sounds like the experiences with an update with 50 packages like
a KDE , but most cases are just a leaf package, which a "works for me"
is a good feedback, for me . 
Conclusion bodhi auto-karma are in the correct proportions , and
should /can be adjust for popular packages .

What I'm trying point out, after a general availability of a release,
I'm a beta tester, I disable update-testings repo and after some weeks I
do a: dnf list extras, I see many packages that still in update-testing
and yes I can make dnf distro-sync, and I can downgrade a bunch of
packages but isn't it more logical push that packages to stable ?, that
way all users (beta testers and others) as the same experience 





-- 
Sérgio M. B.

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Urgent F23 testing request: logout bugs

2015-10-21 Thread Adam Williamson

Hi folks!

So we're building 23 Final RC2 now, but we have a couple of outstanding
proposed blocker bugs, and we could use some more data to evaluate
them.

The way to test is really simple:

* Install F23 Final TC11 Workstation or KDE live[1]
* Create a user and log in
* Log out a bunch of times. Just keep logging in and out.

Ideally try this both in a VM and on a real system, if you have a spare
system to test on.

There are two bugs that you might hit:

1. https://bugzilla.redhat.com/show_bug.cgi?id=1272737
2. https://bugzilla.redhat.com/show_bug.cgi?id=1273247

With the first one, the system gets stuck at a black screen after
logging out. You won't be able to switch to a TTY or anything, but if
you have another system, you'll find that ssh'ing in still works. So
far it seems this bug *only* affects Workstation (we believe it
involves Wayland, and Workstation has GDM-on-Wayland). It seems easy to
reproduce in a KVM, harder to reproduce on a real system, but some
testers have reproduced it on a real system after several attempts.
We're particularly interested in whether you hit it on a real system,
and if so, how often.

With the second bug, assuming you don't hit the first bug, the cursor
disappears on the login screen, possibly after you click somewhere
(e.g. the password text entry box). Roshi says he sees something like
this on Workstation but not KDE, kparal says he sees it on KDE but not
Workstation, and I can't reproduce it on either. This one is probably
only reproducible in a KVM, but of course let us know if you manage to
trigger it on a real system!

If you could report back to the list what configuration you tested on,
and whether and how often you managed to reproduce either bug, that
would be a great help. For virtual machine testing, please let us know:

* What virtualization system you used (KVM/virt-manager is preferred)
* For a KVM:
** Whether your VM has a virtual 'tablet' input device (one
is often created by default, so check in virt-manager)
** What video adapter and viewer you're using (e.g. qxl/SPICE or
std/VNC)
** What OS and release is running on the host system
** The graphics adapter and driver being used on the host system

Thanks!

[1] Downloads:

https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Workstation/i386/iso/Fedora-Live-Workstation-i686-23-TC11.iso

https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-23-TC11.iso

https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Live/i386/Fedora-Live-KDE-i686-23-TC11.iso

https://dl.fedoraproject.org/pub/alt/stage/23_TC11/Live/x86_64/Fedora-Live-KDE-x86_64-23-TC11.iso
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

74 matches

Mail list logo