Ditto! That seems like a much simpler solution overall. -- John Florian > -----Original Message----- > From: Petr Spacek [mailto:pspacek@xxxxxxxxxx] > Sent: Friday, December 11, 2015 03:48 > To: devel@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: Bodhi front page after login > > On 11.12.2015 01:34, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Dec 10, 2015 at 02:57:55PM -0700, Kevin Fenzi wrote: > >> On Thu, 10 Dec 2015 15:39:16 +0000 > >> John Florian <john.florian@xxxxxxxx> wrote: > >> > >>>> From: Michael Schwendt [mailto:mschwendt@xxxxxxxxx] > >>>> Sent: Sunday, December 06, 2015 14:49 > >>>> To: devel@xxxxxxxxxxxxxxxxxxxxxxx > >>>> Subject: Re: Bodhi front page after login > >>>> > >>>> On Sun, 6 Dec 2015 20:17:37 +0100, Reindl Harald wrote: > >>> > >>> > >>>> As far as I know, bodhi posts to bugzilla tickets about test > >>>> updates. Unfortunately, it does that too early with a first > >>>> notification. Bug reporters read the mail, try to apply the > >>>> update, but it is not available for download. It has not been > >>>> pushed, and even when the second notification tells it has been > >>>> pushed, it has not arrived on mirrors. > >>> > >>> This gets me all the time. Then I simply forget to test the update > >>> unless it's something I need badly. Perhaps these two messages in BZ > >>> should indicate that the update will be available when it reaches the > >>> mirrors and a 3rd message could indicate when that has happened > >>> through the use of some mirror probing. Such a 3rd message should be > >>> carefully worded to indicate that the package has started reaching > >>> *some* mirrors and that most should have it within another day. > >> > >> How many is some though? And if those happen to not be ones you are > >> hitting you wouldn't see it then either. > >> > >> Perhaps we could get a dnf plugin thats advised in bugs for testers > >> that checks enabled mirrors, then master mirrors, then koij for a > >> specific update that someone wants to test? The downsides would be if > >> everyone just decided to enable it, or if it's only in koji it possibly > >> wouldn't be signed yet. > > > > What about scrapping the existing bugzilla message, and instead posting > > the direct link to koji download the package: > > > > """To test the update now run: > > dnf upgrade https://koji.fp.o/update-yyyy/path-to.rpm > https://koji.fp.o/update-yyyy/path-to-another.rpm > https://koji.fp.o/update-yyyy/path-to-yet-another.rpm > > > > After that go to https://bodhi.fp.o/update-yyyy/ to leave karma. > > """ > > I like this idea! > > > dnf will skip packages that are not already installed with 'upgrade'. > > Since this would be only run manually, and the dependent packages > > would be downloaded from mirrors, this shouldn't cause too much load > > on koji servers. The advantage would be that the message would be > > actionable and feedback from the bug reporters would be as fast as > > possible. > > -- > Petr Spacek @ Red Hat > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
