On 9/22/19 9:09 PM, Neal Gompa wrote:
On Sun, Sep 22, 2019 at 7:25 PM Ty Young wrote:
On 9/22/19 5:51 PM, Samuel Sieb wrote:
On 9/22/19 3:10 PM, Ty Young wrote:
I couldn't actually install the drivers because the update GUI in the
cinnamon spin is broken and/or the repo/update servers are
https://fedorapeople.org/groups/389ds/ci/nightly/2019/09/23/report-389-ds-base-1.4.2.1-20190922git16cf97e.fc30.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Sun, Sep 22, 2019 at 7:25 PM Ty Young wrote:
>
>
> On 9/22/19 5:51 PM, Samuel Sieb wrote:
> > On 9/22/19 3:10 PM, Ty Young wrote:
> >> I couldn't actually install the drivers because the update GUI in the
> >> cinnamon spin is broken and/or the repo/update servers are down. Again.
> >
> > I
On 9/22/19 5:51 PM, Samuel Sieb wrote:
On 9/22/19 3:10 PM, Ty Young wrote:
I couldn't actually install the drivers because the update GUI in the
cinnamon spin is broken and/or the repo/update servers are down. Again.
I don't know why you're having so much trouble with updates. But just
in
On 9/22/19 3:10 PM, Ty Young wrote:
I couldn't actually install the drivers because the update GUI in the
cinnamon spin is broken and/or the repo/update servers are down. Again.
I don't know why you're having so much trouble with updates. But just
in case you're referring to rpmfusion as you
On 9/22/19 3:08 AM, Leigh Scott wrote:
On Sat, Sep 21, 2019 at 8:33 PM Ty Young
Do you mean 'Support non-root X'? if so some DM's still don't support it.
https://github.com/canonical/lightdm/issues/18
This is Nvidia's fault. It was hidden from you because sometimes the
packaging for the
On Sat, Sep 21, 2019 at 11:04:29PM +0200, Pavel Raiskup wrote:
> On Friday, September 20, 2019 6:08:46 PM CEST Kevin Fenzi wrote:
> > On 9/20/19 4:39 AM, jkone...@redhat.com wrote:
> > > What COPR was doing (I think they changed it after F31) then before a
> > > new chroot in COPR appeared they
On Sat, Sep 21, 2019 at 02:51:48PM -0400, Christopher wrote:
> Why do sometimes notifications have empty message lines like the following?
This is some mismatch between the bodhi messages and the way FMN expects
them to be formatted. ;(
https://github.com/fedora-infra/fmn/issues/298 if you want
On Wed, Sep 18, 2019 at 03:30:58PM -0400, Ben Cotton wrote:
> Now that Modularity is available for all Fedora variants, it's time to
> address issues discovered and improve the experience for packagers and
> users. The Modularity team identified a number of projects that will
> improve the
On Fri, Sep 20, 2019 at 12:12:58PM -0400, Kaleb Keithley wrote:
> Okay. Other builds I've done for f32 (gluster, nfs-ganesha, earlier ceph
> builds even) all went straight to stable in bodhi, but this one didn't,
> despite waiting several hours.
Well, all of those likely were autosubmitted by
On 9/22/19 4:08 PM, Miro Hrončok wrote:
On 22. 09. 19 16:01, Till Hofmann wrote:
So the guidelines allow package retirement without any announcement on
devel. That's certainly unexpected, at least to me. I also don't think
this is a good idea, because maintainers of packages that depend on
On 22. 09. 19 16:01, Till Hofmann wrote:
So the guidelines allow package retirement without any announcement on devel.
That's certainly unexpected, at least to me. I also don't think this is a good
idea, because maintainers of packages that depend on the retired package are
still clueless
OLD: Fedora-Rawhide-20190921.n.0
NEW: Fedora-Rawhide-20190922.n.1
= SUMMARY =
Added images:1
Dropped images: 2
Added packages: 8
Dropped packages:15
Upgraded packages: 191
Downgraded packages: 2
Size of added packages: 336.72 MiB
Size of dropped packages
On 9/22/19 3:40 PM, Miro Hrončok wrote:
On 22. 09. 19 14:37, Till Hofmann wrote:
Hi all,
So I've just been notified that tolua++ has been retired, which is a
dependency of one of my packages (fawkes). BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1736911
I've closed this bug because it
No missing expected images.
Compose FAILS proposed Rawhide gating check!
4 of 45 required tests failed, 11 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
FAILED:
On 22. 09. 19 15:40, Miro Hrončok wrote:
"7. A week before the mass branching, any packages which still have open FTBFS
bugs from the previous release will be retired."
Whether this is a reasonable thing or not has been discussed in:
On 22. 09. 19 14:37, Till Hofmann wrote:
Hi all,
So I've just been notified that tolua++ has been retired, which is a dependency
of one of my packages (fawkes). BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1736911
I've closed this bug because it "was already retired", not because of that
https://bugzilla.redhat.com/show_bug.cgi?id=1754282
Paul Howarth changed:
What|Removed |Added
Depends On||1753674, 1754281
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1754281
Paul Howarth changed:
What|Removed |Added
Blocks||1754282
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1754282
Bug ID: 1754282
Summary: [RFE] EPEL-8 branch for perl-Compress-LZF
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: perl-Compress-LZF
Assignee: dd...@cpan.org
https://bugzilla.redhat.com/show_bug.cgi?id=1754281
Bug ID: 1754281
Summary: [RFE] EPEL-8 branch for perl-Coro-Multicore
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Coro-Multicore
Assignee:
On 9/22/19 3:01 PM, Hans de Goede wrote:
But I do have something to say about the specific example used. tolua++
being retired
is not a problem for fawkes, as fawkes depends on compat-tolua++, which
is maintained
by me and has NOT been retired.
Thanks for pointing this out! I assumed
Hi,
On 22-09-2019 14:37, Till Hofmann wrote:
Hi all,
So I've just been notified that tolua++ has been retired, which is a dependency
of one of my packages (fawkes). BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1736911
This would have been fine (as no action has been taken), if the
Hi all,
So I've just been notified that tolua++ has been retired, which is a
dependency of one of my packages (fawkes). BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1736911
This would have been fine (as no action has been taken), if the
automation had actually followed the FTBFS
No missing expected images.
Failed openQA tests: 5/152 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-31-20190921.n.0):
ID: 456306 Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/456306
ID: 456318 Test: x86_64 KDE-live-iso
OLD: Fedora-31-20190921.n.0
NEW: Fedora-31-20190922.n.0
= SUMMARY =
Added images:0
Dropped images: 9
Added packages: 0
Dropped packages:0
Upgraded packages: 24
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size
Hello,
I am looking to give away freemedforms[1]. It isn't part of our packages
for NeuroFedora, and those are what I'd like to focus my limited
resources on now.
It does not currently build in f31+ and may require dialogue with
upstream to fix.
https://src.fedoraproject.org/rpms/freemedforms
Hi all,
We have an odd issue with a module build of sway for F30: It looks like
the module was actually built with a F32 buildroot.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1754167
Here's the build:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1376355
The modulemd file
On Sat, Sep 21, 2019 14:56:36 -0400, Danny Lee wrote:
> Congrats Alciregi! And thank you for helping! :)
>
> Im also interested, my time is limited for a couple of months, but after the
> Jan 3, I will have much more time.
Welcome @bt0dotninja and @dan1mal too---I've sponsored you now. We can
On 22. 09. 19 1:07, Neal Gompa wrote:
ok. That does give developers 2 less weeks to finish up any changes (or
get FE/blockers for them), but we could do that, sure.
What does everyone else think?
I'm not really in favor of any more time compressions in the schedule
than we already have. It's
On 9/22/19 3:32 AM, Leigh Scott wrote:
I'll just cut to the chase.
Rawhide with Nvidia drivers because of debug kernel. There is a lack of
software compared to other Linux distros like Ubuntu or Arch(no
Vivaldi!?!?). Fedora developers tend to be hostile towards proprietary
software. etc.
I
On 9/22/19 3:08 AM, Leigh Scott wrote:
On Sat, Sep 21, 2019 at 8:33 PM Ty Young
Do you mean 'Support non-root X'? if so some DM's still don't support it.
https://github.com/canonical/lightdm/issues/18
...and it's Open Source. Ironic.
Anyway, I did a google search and apparently running
> I'll just cut to the chase.
> Rawhide with Nvidia drivers because of debug kernel. There is a lack of
> software compared to other Linux distros like Ubuntu or Arch(no
> Vivaldi!?!?). Fedora developers tend to be hostile towards proprietary
> software. etc.
I guess debugging symbols are an
On Sun, Sep 22, 2019, 10:09 Leigh Scott wrote:
> > On Sat, Sep 21, 2019 at 8:33 PM Ty Young wrote:
> > Fedora and other distributions have been working on rootless Xorg
> > since 2013. We've had it in place since at least 2015. This change was
> > made way back in Fedora 24.
> >
>
> Do you mean
> On Sat, Sep 21, 2019 at 8:33 PM Ty Young Fedora and other distributions have been working on rootless Xorg
> since 2013. We've had it in place since at least 2015. This change was
> made way back in Fedora 24.
>
Do you mean 'Support non-root X'? if so some DM's still don't support it.
On 9/22/19 2:40 AM, John M. Harris Jr wrote:
On Saturday, September 21, 2019 5:32:37 PM MST Ty Young wrote:
I'll just cut to the chase.
About 2-3 months ago I filed a bug report that overclocking on Nvidia
hardware wasn't working on Fedora.
I then later sent an email about this issue wherein
On Sunday, September 22, 2019 12:26:46 AM MST Ty Young wrote:
> I'm of course also interested in ensuring compatibility with Fedora for
> my application but given how hostile y'all are to Nvidia it doesn't seem
> like it's ever going to happen. I guess it's not the end of the word
> since noone
On Saturday, September 21, 2019 5:32:37 PM MST Ty Young wrote:
> I'll just cut to the chase.
>
>
> About 2-3 months ago I filed a bug report that overclocking on Nvidia
> hardware wasn't working on Fedora.
> I then later sent an email about this issue wherein Nvidia was immediately
> blamed for
On Saturday, September 21, 2019 11:46:40 PM MST Ty Young wrote:
> That's a load of bull dung if there ever was one. There are *MANY* bugs
> in Intel/AMD's drivers and MESA that have yet to be fixed(which affect
> everyone) despite being Open Source. You can't fix those bugs as is but
> then
https://bugzilla.redhat.com/show_bug.cgi?id=1751411
Emmanuel Seyman changed:
What|Removed |Added
Status|NEW |CLOSED
Fixed In Version|
On 9/22/19 1:57 AM, Samuel Sieb wrote:
On 9/21/19 11:46 PM, Ty Young wrote:
That's a load of bull dung if there ever was one. There are *MANY*
bugs in Intel/AMD's drivers and MESA that have yet to be fixed(which
affect everyone) despite being Open Source. You can't fix those bugs
as is but
On 9/21/19 11:46 PM, Ty Young wrote:
That's a load of bull dung if there ever was one. There are *MANY* bugs
in Intel/AMD's drivers and MESA that have yet to be fixed(which affect
everyone) despite being Open Source. You can't fix those bugs as is but
then turn around and imply that *IF*
On 9/22/19 12:48 AM, Samuel Sieb wrote:
On 9/21/19 6:31 PM, Ty Young wrote:
Really? It's Nvidia's fault that noone can agree on anything and keep
fragmenting the ecosystem in incredibly stupid ways?
No, it's NVidia's fault because they refuse to open-source their
driver. That means that
43 matches
Mail list logo