https://bugzilla.redhat.com/show_bug.cgi?id=1836456
--- Comment #7 from Fedora Update System ---
FEDORA-2020-fb4f473b3f has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade
On 5/18/20 5:54 PM, Ty Young wrote:
I'm not advocating for in-kernel drivers. AMD with their drivers has
proven proven what a bad idea that is. I, for the most part, like where
I'm at and the way Nvidia does things. If I'm against it, I don't see
why I would be the one to do it.
This comment
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
--- Comment #6 from Fedora Update System ---
FEDORA-2020-747f380e37 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #5 from
On 5/17/20 6:34 AM, Paul Howarth wrote:
I'm trying to do a local build of gtkwave for EPEL-8.
A koji scratch build somehow works:
http://koji.fedoraproject.org/koji/taskinfo?taskID=44609837
But a local build does not:
$ mock -r epel-8-x86_64 gtkwave-3.3.104-2.fc31.src.rpm
...
Error:
https://bugzilla.redhat.com/show_bug.cgi?id=1742913
--- Comment #12 from Orion Poplawski ---
Yeah, that's at least one of the things hopefully fixed in the latest build.
We are still seeing very strange things in koji though that we have so far been
unable to diagnose.
--
You are receiving
On Mon, May 18, 2020 at 07:54:42PM -0500, Ty Young wrote:
> Surely it is the responsibility of those who want such a change to
> make sure that everything that existed before can continue to exist? I
> realize this requires that such arguments are being made in good faith
> and consider the
https://fedorapeople.org/groups/389ds/ci/nightly/2020/05/19/report-389-ds-base-1.4.4.2-20200518git3516495.fc32.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
We're trying to track down a problem that only appears in koji and
copr, but I can't reproduce locally in mock on my rawhide VM. It's
related to file triggers and we're trying to debug with something this:
%transfiletriggerin -n texlive-kpathsea -- /usr/share/texlive
# %{_bindir}/texhash 2>
On Mon, May 18, 2020 at 10:18 PM Ty Young wrote:
>
>
> On 5/18/20 8:24 PM, Michael Catanzaro wrote:
> >
> > Dude, chill out. We're not going to go back to running X as root. The
> > Nvidia overclocking tool is just not important at all (seriously, who
> > cares?). If you're upset their
On 5/18/20 8:24 PM, Michael Catanzaro wrote:
Dude, chill out. We're not going to go back to running X as root. The
Nvidia overclocking tool is just not important at all (seriously, who
cares?). If you're upset their proprietary software doesn't work
anymore, you can ask them nicely to fix
On Monday, May 18, 2020 4:03:16 PM MST Ty Young wrote:
> On 5/18/20 2:51 PM, Samuel Sieb wrote:
>
> > On 5/18/20 7:27 AM, Ty Young wrote:
> >
> >> The application was an Nvidia GPU overclocking utility written in
> >> Java. When Fedora decided to disable running X. Org as root, it
> >>
On Mon, May 18, 2020 at 8:24 pm, Michael Catanzaro
wrote:
Dude, chill out. We're not going to go back to running X as root.
Ugh, I just noticed the subject of this thread is Java SIG. Amazing how
thoroughly this conversation has been derailed
Dude, chill out. We're not going to go back to running X as root. The
Nvidia overclocking tool is just not important at all (seriously, who
cares?). If you're upset their proprietary software doesn't work
anymore, you can ask them nicely to fix it please... or ask for the
source code, and
On 5/18/20 7:08 PM, Solomon Peachy wrote:
On Mon, May 18, 2020 at 06:03:16PM -0500, Ty Young wrote:
Willing to bet you or anyone else here won't.
FYI, this applies to you as well.
You just proved my point:
>If it was Open Source and we were having this discussion, people like
yourself
On Mon, 18 May 2020 18:03:16 -0500, you wrote:
>X. Org as root is **STILL** the standard and Fedora broke it. This is
>why no one wants to support Linux: you constantly break your own
>platform and then cry wolf when people who don't care about your
>ideological nonsense refuse to fix their
On Mon, May 18, 2020 at 06:03:16PM -0500, Ty Young wrote:
> Willing to bet you or anyone else here won't.
FYI, this applies to you as well.
- Solomon
--
Solomon Peachypizza at shaftnet dot org (email)
@pizza:shaftnet dot org
On Mon, May 18, 2020 at 9:34 AM Ty Young wrote:
> The "toolchain" isn't broken, other than Gradle developers not caring
> about backwards compatibility but... It works for them, just as
A toolchain with broken links scattered through it is not toolchain.
Building up the .jar files as a
On 5/18/20 2:51 PM, Samuel Sieb wrote:
On 5/18/20 7:27 AM, Ty Young wrote:
The application was an Nvidia GPU overclocking utility written in
Java. When Fedora decided to disable running X. Org as root, it
resulted in the application no longer being able to adjust GPU/Memory
clocks, among
On 5/17/20 5:07 PM, Globe Trotter via devel wrote:
Thanks! Adding "--releasever=32" to the command addresses that problem.
Btw, how do I get around a disk requirement? What causes an error like this?
Error Summary
-
Disk Requirements:
At least 137MB more space needed on the /
Hello everyone!
Introduction:
After reading the Fedora docs on packaging, I decided I would like to join
the Fedora project initially as a package maintainer/reviewer and perhaps
later as a source code committer. Here's the bug report for the package I'd
like to revive/unorphan:
https://pagure.io/389-ds-base/pull-request/51096
--
389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On 5/18/20 7:27 AM, Ty Young wrote:
The application was an Nvidia GPU overclocking utility written in Java.
When Fedora decided to disable running X. Org as root, it resulted in
the application no longer being able to adjust GPU/Memory clocks, among
possible other things. The software worked
https://fedoraproject.org/wiki/Changes/Aarch64_PointerAuthentication
== Summary ==
Arm Pointer Authentication (PAC) is a method of hardening code from
Return Oriented Programming (ROP) attacks. It uses a tag in a pointer
to sign and verify pointers. Branch Target Identification (BTI) is
another
https://fedoraproject.org/wiki/Changes/Aarch64_PointerAuthentication
== Summary ==
Arm Pointer Authentication (PAC) is a method of hardening code from
Return Oriented Programming (ROP) attacks. It uses a tag in a pointer
to sign and verify pointers. Branch Target Identification (BTI) is
another
On Monday, 18 May 2020 17.38.10 WEST Miro Hrončok wrote:
> And I change it to:
>
> %python3_pkgversion 36
> %python3_other_pkgversion 34
>
> When needed. It is tedious
I think that we need some kind of rpmenv (mostly in terms of the configuration
files but you get the idea). :-)
I am only
On Mon, May 18, 2020 at 7:45 PM Arun Sukumaran Latha
wrote:
>
> Yes please, do let me know if we can build thos one.
>
I will let you know.
I found some dependencies misaligned due to some packages failing to
build or failing to pass tests.
I am slowly rebuilding/checking those, but that will
Petr Pisar writes:
> On Sat, May 16, 2020 at 12:56:06PM +0200, Dominique Martinet wrote:
>
>> How should I go about with that? Open bz bugs to all the packages I
>> listed? strongly suggesting to get things to move to /usr/share (17)
>> and flatpak (suggest some kind of cache? not sure they'll
On Mon, 18 May 2020, Miro Hrončok wrote:
On 18. 05. 20 18:23, Scott Talbert wrote:
Any good workarounds for working with epel7 Python packages on Fedora?
Mainly dealing with the fact that python3_pkgversion differs from Fedora to
EPEL7. Ie, when doing 'fedpkg mockbuild' the SRPM will be
https://bugzilla.redhat.com/show_bug.cgi?id=1837021
Bug ID: 1837021
Summary: perl-Crypt-ECB-2.22 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Crypt-ECB
Keywords: FutureFeature, Triaged
https://bugzilla.redhat.com/show_bug.cgi?id=1837021
--- Comment #1 from Upstream Release Monitoring
---
An HTTP error occurred downloading the package's new Source URLs: Getting
https://cpan.metacpan.org/modules/by-module/Crypt/Crypt-ECB-2.22.tar.gz to
./Crypt-ECB-2.22.tar.gz
--
You are
Yes please, do let me know if we can build thos one.
Regards,
Arun SL
On Sun, May 17, 2020, 17:25 David Abdurachmanov <
david.abdurachma...@gmail.com> wrote:
> On Sun, May 17, 2020 at 1:52 PM Arun Sukumaran Latha
> wrote:
> >
> > Thanks David,
> >
> > That helped a lot.
> >
> > But
On 18. 05. 20 18:23, Scott Talbert wrote:
Any good workarounds for working with epel7 Python packages on Fedora? Mainly
dealing with the fact that python3_pkgversion differs from Fedora to EPEL7. Ie,
when doing 'fedpkg mockbuild' the SRPM will be generated with the wrong
python3_pkgversion.
Any good workarounds for working with epel7 Python packages on Fedora?
Mainly dealing with the fact that python3_pkgversion differs from Fedora
to EPEL7. Ie, when doing 'fedpkg mockbuild' the SRPM will be generated
with the wrong python3_pkgversion.
I tried this, but it didn't seem to work:
+1 makes sense to me; also side-note, in my testing jq seems to work just fine
built against oniguruma 6.9.4
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
=
#fedora-meeting-1: FESCO (2020-05-18)
=
Meeting started by sgallagh at 14:59:49 UTC. The full logs are available
at
- Original Message -
> From: "Charalampos Stratakis"
> To: "Development discussions related to Fedora"
>
> Sent: Friday, May 15, 2020 8:12:00 PM
> Subject: Many packages unnecessarily link to libpython
>
> pyotherside m4rtink
I can report this is expected and correct.
- Original Message -
> From: "Kushal Das"
> To: devel@lists.fedoraproject.org
> Sent: Friday, May 15, 2020 10:08:34 AM
> Subject: Re: Why we package Rust crates
>
> On 5/15/20 1:05 AM, Igor Raits wrote:
> > Hello,
> >
> > This email attempts to answer some frequently asked questions
On Mon, May 18, 2020 at 3:43 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Wed, May 13, 2020 at 02:38:58PM +0200, Kalev Lember wrote:
> > On 5/12/20 20:42, Gwyn Ciesla via devel wrote:
> > >Everything is now rebuild, except for elementary-photos and shotwell,
> which are failing
On 5/18/20 9:14 AM, Fabio Valentini wrote:
On Mon, May 18, 2020 at 3:34 PM Ty Young wrote:
On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote:
My software didn't magically break just for Fedora because of some bug
in my software. It broke because Fedora decided they wanted to do
something
On Mon, May 18, 2020 at 3:34 PM Ty Young wrote:
> On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote:
> My software didn't magically break just for Fedora because of some bug
> in my software. It broke because Fedora decided they wanted to do
> something nearly no Linux distro does... something
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Good $LOCAL_TIME_OF_DAY,
I've been working on experimental support for automatically generating
BuildRequires for maven-based Java projects, and it's now available
for testing in rawhide (and in fedora 32, for local testing).
There's no "macro support" for this yet, because it's still
Le lundi 18 mai 2020 à 08:34 -0500, Ty Young a écrit :
>
> The "toolchain" isn't broken, other than Gradle developers not
> caring about backwards compatibility but... It works for them, just
> as constantly breaking internal kernel APIs works for the Linux
> kernel
The difference, is that you
On 5/18/20 8:34 AM, Ty Young wrote:
...and there are plenty of Open Source projects that don't have
packages yet people contribute to them. This isn't the early 2000 when
barely anyone has internet and sites like Github didn't exist. Sure, a
distro package increases visibility still, but
On Wed, May 13, 2020 at 02:38:58PM +0200, Kalev Lember wrote:
> On 5/12/20 20:42, Gwyn Ciesla via devel wrote:
> >Everything is now rebuild, except for elementary-photos and shotwell, which
> >are failing for a reason I don't totally understand yet; they build on local
> >rawhide and in mock but
Il 11/05/20 22:33, Gwyn Ciesla via devel ha scritto:
> I'm building LibRaw 0.20 Beta 1 for rawhide, along with all direct
> consumers, in a multi-stage chain build, today, including the following:
>
> ...
>
>
FYI Also kstars has BR on LibRaw.
I've triggered a rebuild just now.
Mattia
On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote:
Le lundi 18 mai 2020 à 14:12 +0200, Michal Srb a écrit :
Hello,
On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel <
devel@lists.fedoraproject.org> wrote:
Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit :
On Fri, 15
install the fedora-kickstarts rpm
edit the fedora-repo.ks to use fedora-repo-not-rawhide.ks
ksflatten your kickstart and it will use the normal fedora repos
(when all else fails talk to the Fedora Respin SiG in #fedora-respins)
___
devel mailing list
Richard Shaw wrote on Mon, May 18, 2020:
> > Seems to work for me:
>
> Don't know what's wrong then...
I went back and re-read your first mail, it is possible it doesn't work
on one of your own projects?
I'm not sure how much sense there is in forking your own repo...
> Ok, so this is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d
On Mon, May 18, 2020 at 7:25 AM Dominique Martinet
wrote:
> Richard Shaw wrote on Mon, May 18, 2020:
> > I checked src.fp.o/settings and even though my key was still valid, it
> was
> > going to expire this month so I went ahead and generated a new api token
> > and saved it in the specified
Le lundi 18 mai 2020 à 14:12 +0200, Michal Srb a écrit :
> Hello,
>
> On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel <
> devel@lists.fedoraproject.org> wrote:
> > Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit :
> > > On Fri, 15 May 2020 08:02:34 +0200
> > > Michal Srb
Thanks! How do I get around this issue?
I have setenforce set at 0.
Also, why does the issue go away when I reduce the packages to be packed in the
remix/spin?
On Monday, May 18, 2020, 5:26:35 AM CDT, Petr Pisar
wrote:
On Mon, May 18, 2020 at 12:07:38AM +, Globe Trotter via
Richard Shaw wrote on Mon, May 18, 2020:
> I checked src.fp.o/settings and even though my key was still valid, it was
> going to expire this month so I went ahead and generated a new api token
> and saved it in the specified location:
> ~/.config/rpkg/fedpkg.conf
I actually hadn't used it yet, so
I'm trying this for the first time (hadn't even noticed it was there!).
I've been using the src.fp.o github style forking from the web.
I cloned a random project of mine and then tried:
$ fedpkg fork
Could not execute do_distgit_fork: The following error occurred while
creating a new fork:
Hello,
On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel <
devel@lists.fedoraproject.org> wrote:
> Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit :
> > On Fri, 15 May 2020 08:02:34 +0200
> > Michal Srb wrote:
> >
> > An aside, just to clarify for myself. That means that
On Mon, May 18, 2020 at 6:29 AM Dominique Martinet
wrote:
>
> On the pagure side, I assume the process is something along the lines of:
> - fedpkg clone pkg && cd pkg
> - modify things
> - fedpkg fork
> - push in fork
> - got create PR in the web interface?
>
I would think you should fork
https://bugzilla.redhat.com/show_bug.cgi?id=1836658
Jitka Plesnikova changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Fixed In Version|
Zbigniew Jędrzejewski-Szmek wrote on Mon, May 18, 2020:
> > > How should I go about with that? Open bz bugs to all the packages I
> > > listed?
> >
> > I would suggest to directly create pull requests on pagure (with a
> > reference to this thread), as that will make it more likely that this
> >
On Sat, May 16, 2020 at 01:35:52PM +0200, Dan Čermák wrote:
> Hi Dominique,
>
> Dominique Martinet writes:
>
> > *snip*
> >
> > 341 to 130ms is a good start I guess, the rest of the waiting time
> > probably now outweights bash and will get some looking at at a later
> > point, but might as
On Mon, May 18, 2020 at 12:07:38AM +, Globe Trotter via devel wrote:
> Thanks! Adding "--releasever=32" to the command addresses that problem.
> Btw, how do I get around a disk requirement? What causes an error like this?
>
> Error Summary-
> Disk Requirements:
> At least
https://bugzilla.redhat.com/show_bug.cgi?id=1836658
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |ASSIGNED
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Il giorno dom, 17/05/2020 alle 16.08 +0200, Dario Lesca ha scritto:
> Done: https://bugzilla.redhat.com/show_bug.cgi?id=1836630
I must fill a bug also on samba's bugzilla?
--
Dario Lesca
(inviato dal mio Linux Fedora 32 Workstation)
___
devel mailing
On Sat, May 16, 2020 at 12:56:06PM +0200, Dominique Martinet wrote:
> How should I go about with that? Open bz bugs to all the packages I
> listed? strongly suggesting to get things to move to /usr/share (17) and
> flatpak (suggest some kind of cache? not sure they'll be interested...)
> and
On Sat, May 16, 2020 at 11:43:00AM +0200, Antonio Trande wrote:
> On 15/05/20 14:57, Stephen Gallagher wrote:
> > On Fri, May 15, 2020 at 7:57 AM Petr Pisar wrote:
> >>
> >> On Fri, May 15, 2020 at 06:30:04AM -0500, Richard Shaw wrote:
> >>> On Fri, May 15, 2020 at 6:15 AM Petr Pisar wrote:
>
On Sat, May 16, 2020 at 11:43:00AM +0200, Antonio Trande wrote:
> On 15/05/20 14:57, Stephen Gallagher wrote:
> > On Fri, May 15, 2020 at 7:57 AM Petr Pisar wrote:
> >>
> >> On Fri, May 15, 2020 at 06:30:04AM -0500, Richard Shaw wrote:
> >>> On Fri, May 15, 2020 at 6:15 AM Petr Pisar wrote:
>
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
--- Comment #3 from Fedora Update System ---
FEDORA-2020-fb4f473b3f has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-fb4f473b3f
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
--- Comment #4 from Fedora Update System ---
FEDORA-2020-c446a7263b has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c446a7263b
--
You are receiving this mail because:
You are on the CC list
Hi,
I maintain GNOME Boxes (which is part of the default workstation
installation) and GNOME Connections. Both written in Vala. Therefore
the maintenance of Vala in Fedora is important to me.
I can take ownership of it, and I will be happy to collaborate with
others that might be also
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
--- Comment #2 from Fedora Update System ---
FEDORA-2020-747f380e37 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-747f380e37
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1836456
Petr Pisar changed:
What|Removed |Added
Status|NEW |ASSIGNED
Dne 17. 05. 20 v 1:25 Benjamin Lowry napsal(a):
> I recently adopted flatbuffers, which was orphaned due to an open FTBFS
> in F32 [1]. I've fixed the spec, rebuilt, and made an update in bodhi,
> but I'm unable to close the FTBFS bug because it hasn't been reassigned
> to me. What should I do?
No missing expected images.
Soft failed openQA tests: 1/1 (x86_64)
(Tests completed, but using a workaround for a known bug)
ID: 600166 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/600166
--
Mail generated by check-compose:
OLD: Fedora-Rawhide-20200516.n.0
NEW: Fedora-Rawhide-20200517.n.1
= SUMMARY =
Added images:0
Dropped images: 2
Added packages: 7
Dropped packages:0
Upgraded packages: 113
Downgraded packages: 0
Size of added packages: 2.51 MiB
Size of dropped packages:0 B
On Sun, May 17, 2020 at 9:45 AM Joseph Wagner
wrote:
> I've tried relabeling, and the problem still persists. Should I report
> this as a bug, or this a config problem on my end?
>
Hi Joseph,
This bug has already been reported:
https://bugzilla.redhat.com/show_bug.cgi?id=1827972
It is a
On Friday, May 15, 2020 8:12:00 PM CEST Charalampos Stratakis wrote:
> [...]
> On Fedora Rawhide, there are at this point 144 packages linking to libpython,
> many of those possibly without any need for it.
> [...]
> postgresql hhorak jstanek panovotn pkajaba pkubat praiskup tgl
> [...]
79 matches
Mail list logo
