On 9/20/18 1:56 PM, Matthew Miller wrote:
> If it's "they'll find out when dnf system-upgrade errors out!", then see
> above. I'm ... not enthused. Something in dnf system-upgrade needs to do it;
> possibly a "dnf system-upgrade prep" step before "download".
I agree. Would it be feasible for the s
On Thu, 20 Sep 2018 at 18:17, Jonathan Underwood
wrote:
>
> Hi,
>
> In the process of orphaning a few packages lately, I noticed that the
> user "cicku" (Christopher Meng) still had commit or admin privelidges
> on the package. That user hasn't been active for a couple of years,
> and I vaguely re
On 20/09/18 09:38, Sérgio Basto wrote:
> On Thu, 2018-09-20 at 07:58 +1000, David Timms wrote:
> The conditional is correct but [1] from the previous %endif you leave
> two blanks lines which you can't, one blank line makes terminate the
> ./configure command and so last option "--disable-sse" is n
The Fedora 29 Beta RC5 compose [1] is GO and is going to be shipped
live on Tuesday, September 25, 2018.
For more information please check the Go/No-Go meeting minutes [2] or logs [3].
Thank you to everyone who has and still is working on this release!
[1] http://dl.fedoraproject.org/pub/alt/sta
On Thu, Sep 20, 2018 at 04:20:49PM +0200, Adam Samalik wrote:
> > > And when that module is EOL, what is the user experience?
> > What I described in my reply earlier: the upgrade should not work and
> > the user should be required to switch to a new stream on their current
> > environment first. W
On Thu, Sep 20, 2018 at 09:35:41AM -0400, Stephen Gallagher wrote:
> > > Independently of this, you could also retire 1.7 with the end of F27 if
> > > there was no need to have it in the future releases.
> > Is there a way for users to say "keep me on whatever module is the default"
> > when upgrad
Hi,
In the process of orphaning a few packages lately, I noticed that the
user "cicku" (Christopher Meng) still had commit or admin privelidges
on the package. That user hasn't been active for a couple of years,
and I vaguely remember packages that he owned being orphaned. But, it
seems like packa
On Thu, Sep 20, 2018 at 10:22 AM, Peter Robinson wrote:
>> There was a bug[1] filed recently that indicated that printing was
>> broken on certain printers. As a result of that discussion, it became
>> apparent that there was no criteria for printing to work at all, which
>> seems like an oversigh
> There was a bug[1] filed recently that indicated that printing was
> broken on certain printers. As a result of that discussion, it became
> apparent that there was no criteria for printing to work at all, which
> seems like an oversight.
>
> I discussed this briefly with Matthias Clasen this mor
Hi,
as CUPS maintainer, I agree with the idea of working printing as beta
criteria for Fedora.
I have two printers (Canon, HP) at my disposal, which I test cups,
cups-filters and hplip on when they have rebase. IMO it would be perfect
if such tests can be run every time when a component, which CU
I'm planning to orphan the following packages tomorrow, as I don't use
them any more and don't have time to maintain them properly:
* nodejs-spdx-expression-parse-v2.0.2
* nodejs-aproba-v2.0.0
* nodejs-read-package-tree
* nodejs-less-3.8.1
If anyone would like to pick them up, let me know and I'l
On Thu, Sep 20, 2018, 5:05 AM Vascom wrote:
> Hi all.
>
> I have big bug with Fedora 29 Beta Candidate 1.5.
> Live-usb just stuck boot just before start graphical mode. I am can't
> understand what component causes this so can't create bugreport in
> bugzilla.
>
> This happen on my netbook Asus 1
On Thu, Sep 20, 2018 at 9:12 AM Matthew Miller wrote:
>
> On Tue, Sep 18, 2018 at 10:48:46AM +0200, Adam Samalik wrote:
> > There is another concept in Modularity we can use here: defaults. You could
> > have both streams 1.7 and 1.8 built for all active (non-EOL) Fedora
> > releases, but have dif
On Thu, Sep 20, 2018, 7:50 AM Stephen Gallagher wrote:
> On Thu, Sep 20, 2018 at 9:47 AM Ben Cotton wrote:
> >
> > On Thu, Sep 20, 2018 at 8:33 AM Stephen Gallagher
> wrote:
> > >
> > > I'd like to propose that we add the following criteria to Beta for
> Fedora 30+:
> > > * Printing must work o
On Thu, Sep 20, 2018 at 4:17 PM Stephen Gallagher
wrote:
> On Thu, Sep 20, 2018 at 10:16 AM Matthew Miller
> wrote:
> >
> > On Thu, Sep 20, 2018 at 03:58:20PM +0200, Petr Šabata wrote:
> > > > Is there a way for users to say "keep me on whatever module is the
> default"
> > > > when upgrading?
>
On Thu, Sep 20, 2018 at 10:16 AM Matthew Miller
wrote:
>
> On Thu, Sep 20, 2018 at 03:58:20PM +0200, Petr Šabata wrote:
> > > Is there a way for users to say "keep me on whatever module is the
> > > default"
> > > when upgrading?
> > If they enable the module explicitly, they will keep that strea
On Thu, Sep 20, 2018 at 03:58:20PM +0200, Petr Šabata wrote:
> > Is there a way for users to say "keep me on whatever module is the default"
> > when upgrading?
> If they enable the module explicitly, they will keep that stream,
> regardless of what the current defaults are.
And when that module i
On Thu, Sep 20, 2018 at 09:11:57AM -0400, Matthew Miller wrote:
> On Tue, Sep 18, 2018 at 10:48:46AM +0200, Adam Samalik wrote:
> > There is another concept in Modularity we can use here: defaults. You could
> > have both streams 1.7 and 1.8 built for all active (non-EOL) Fedora
> > releases, but h
On Thu, Sep 20, 2018 at 9:47 AM Ben Cotton wrote:
>
> On Thu, Sep 20, 2018 at 8:33 AM Stephen Gallagher wrote:
> >
> > I'd like to propose that we add the following criteria to Beta for Fedora
> > 30+:
> > * Printing must work on at least one printer available to Fedora QA.
> > "Work" is defined
On Thu, Sep 20, 2018 at 8:33 AM Stephen Gallagher wrote:
>
> I'd like to propose that we add the following criteria to Beta for Fedora 30+:
> * Printing must work on at least one printer available to Fedora QA.
> "Work" is defined as the output from the device matching a preview
> shown on the GNO
On Tue, Sep 18, 2018 at 10:48:46AM +0200, Adam Samalik wrote:
> There is another concept in Modularity we can use here: defaults. You could
> have both streams 1.7 and 1.8 built for all active (non-EOL) Fedora
> releases, but have different default for each. So in your case, F27 could
> have 1.7 as
On Thu, Sep 20, 2018 at 8:40 AM Stephen Gallagher
wrote:
> I'd like to propose that we add the following criteria to Beta for Fedora
> 30+:
> * Printing must work on at least one printer available to Fedora QA.
>
> and this to Final for Fedora 30+:
> * Printing must work on at least one printer
DevConf.cz 2019 is the 11th annual, free, Red Hat sponsored community
conference for developers, admins, DevOps engineers, testers,
documentation writers and other contributors to Open Source Linux,
middleware, virtualization, storage, cloud and mobile technologies
where FLOSS communities sync, sha
On Thu, Sep 20, 2018 at 08:33:05AM -0400, Stephen Gallagher wrote:
> There was a bug[1] filed recently that indicated that printing was
> broken on certain printers. As a result of that discussion, it became
> apparent that there was no criteria for printing to work at all, which
> seems like an ov
This one is interesting as well, since I was bitten by it:
https://bugzilla.redhat.com/show_bug.cgi?id=1614978
V.
Dne 20.9.2018 v 14:33 Stephen Gallagher napsal(a):
> There was a bug[1] filed recently that indicated that printing was
> broken on certain printers. As a result of that discussion
Cloud Base and Atomic Host AMIs are available to test for various regions.
Cloud Base AMIs are here:
Fedora-Cloud-Base-29_Beta-1.5.x86_64 ap-northeast-1
ami-0a24cb0b129391f91 hvm standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64 ap-northeast-2
ami-025a265da1a333635 hvm standard
Fedora-Cloud-Base
There was a bug[1] filed recently that indicated that printing was
broken on certain printers. As a result of that discussion, it became
apparent that there was no criteria for printing to work at all, which
seems like an oversight.
I discussed this briefly with Matthias Clasen this morning and he
Hi all.
I have big bug with Fedora 29 Beta Candidate 1.5.
Live-usb just stuck boot just before start graphical mode. I am can't
understand what component causes this so can't create bugreport in
bugzilla.
This happen on my netbook Asus 1225c with Atom N2800 and gma500
graphics. The same behaviour
Hi Adam,
On Wed, 19 Sep 2018 at 20:51, Adam Jackson wrote:
>
> On Wed, 2018-09-19 at 00:02 +0100, Jonathan Underwood wrote:
>
> > I don't have the time to continue maintaining this package,
> > unfortunately. Please get in touch if you want to maintain the
> > package and I'll hand it over to you
No missing expected images.
Failed openQA tests: 2/132 (x86_64), 1/24 (i386), 1/2 (arm)
ID: 283213 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/283213
ID: 283219 Test: arm Minimal-raw_xz-raw.xz
install_arm_image_deployment_uplo
> On 20 Sep 2018, at 06:47, Alexander Bokovoy wrote:
>
> On ke, 19 syys 2018, Björn Persson wrote:
>> Alexander Bokovoy wrote:
>>> Can you provide output from
>>>
>>> export KRB5_TRACE=/dev/stderr
>>> klist -A
>>> kinit
>>> fedpkg build
>>>
>>> ?
>>
>> The log is attached. I tried it twice a
31 matches
Mail list logo
