Re: F30: System-Wide Change proposal: DNF UUID

> > Since there is no personal information attached, I don't see how on the > > face of it this is a privacy violation. I want to take this concern > > seriously, but I need more to go on than "this is inherent". Can you > > elaborate? > > I detailed it further down my message: my concern is that

Re: F30: System-Wide Change proposal: DNF UUID

> Dne 08. 01. 19 v 10:10 Zbigniew Jędrzejewski-Szmek napsal(a): > > I an IP address qualifies as "personal data", then an installation UUID > > does too. > > IANAL but I disagree. With IP address, I can very easily guess your > town/village. With more effort I can track you to > individual house

Re: F30: System-Wide Change proposal: DNF UUID

> > Not if we don't keep them for long. One idea is to rotate them fairly > > frequently. But this is mostly a statement of intent and might be more about > > how we build the backend than about what we force in the client. > > My understanding is that the Fedora project does not control how much

Re: Is dnf update --releasever=30 supposed to work with modules?

On Mon, Mar 4, 2019 at 6:31 AM Richard W.M. Jones wrote: > > On my Fedora 29-ish machine, I just tried: > > # dnf update --best --releasever=30 You're better off doing: dnf --releasever=30 --setopt=deltarpm=false distro-sync But it does have issues with modules atm so a work around is: dnf

Re: doxygen crash on aarch64

Hi, > For one of my packages, doxygen is crashing on aarch64 (and not on any > other arch). Any ideas/tips on how to fix this? Is the package name secret? More details are always good here. There's generally no issues with doxygen in general on aarch64. > ... > Patching output file 570/631 >

Re: F30 Self-Contained Change proposal: Retire YUM 3

> > I have an update on the koji end. The 1.17 release will not only drop the > > yum dependency, it will also have full python 3 support (except for image > > building that uses oz / imagefactory). Unfortunately, there is only medium > > confidence that the 1.17 release will be ready by the

Re: F30 Self-Contained Change proposal: Retire YUM 3

On Fri, Mar 1, 2019 at 1:23 AM Dennis Gregorovic wrote: > > I have an update on the koji end. The 1.17 release will not only drop the > yum dependency, it will also have full python 3 support (except for image > building that uses oz / imagefactory). Unfortunately, there is only medium >

Re: frozen approved review

On Sun, Mar 17, 2019 at 6:53 PM Didier Fabert wrote: > > Hi all, > > My package was reviewed and accepted[1], but the ticket is frozen since > a week now. What is the next step ? > I find nothing about this in package review process[2], or > packaging-guidelines[3]. Have you done a "fedpkg

Re: /dev/net/tun no longer exists in F31 rawhide ?

On Mon, Mar 18, 2019 at 2:23 PM Adam Williamson wrote: > > On Mon, 2019-03-18 at 14:07 +, Daniel P. Berrangé wrote: > > Historically in Fedora the /dev/net/tun device always existed, even if > > there is no 'tun' module currently loaded. Opening it then cause the > > 'tun' kernel module to

Re: Non-responsive maintainer Chris Lalancette (clalance)

On Tue, Mar 12, 2019 at 10:12 AM Miro Hrončok wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=1659737 > > Anyone knows how to contact the maintainer? He is occasionally active, he still has an active github account, you can probably get hold of him via contact details there.

Re: Packaging Question - Open Liberty

On Thu, 21 Mar 2019, 18:50 Adam Williamson, wrote: > On Thu, 2019-03-21 at 17:25 +, Michael Zhang wrote: > > Hi > > > > From the previous email, it was stated that it's mandatory to include > > the building of the Open Liberty binaries into the rpmbuild. We are > > planning on doing that and

Re: F30 change, bootloaderspec by default

On Thu, Feb 14, 2019 at 10:34 AM Javier Martinez Canillas wrote: > > Hello Chris, > > On Wed, Feb 13, 2019 at 7:49 PM Chris Murphy wrote: > > > > I glossed over the fact upgrades to Fedora 30 will be converted to the > > "bls way" of things. So I want to be sure I understand feature scope: > > >

Re: signing status

On Tue, Feb 12, 2019 at 8:49 AM Jan Pazdziora wrote: > > On Mon, Feb 11, 2019 at 10:35:55AM -0800, Kevin Fenzi wrote: > > >> > > >> * The mass rebuild happened and finished. > > > > > > Is there anywhere some summary stats about mass update? > > > How many packages has been sent to rebuild vs

Re: F30 Self-Contained Change proposal: Retire YUM 3

On Wed, Jan 30, 2019 at 9:41 AM Florian Weimer wrote: > > * Miro Hrončok: > > > On 29. 01. 19 19:04, John Harris wrote: > >> On Monday, January 28, 2019 12:27:19 PM EST Ben Cotton wrote: > >>> Remove packages from the distribution: > >>> * createrepo > >>> * yum > >>> * yum-langpacks > >>> *

Re: Fedora 30 Mass Rebuild

> There seems to be an issue with moving builds over. Everything seems to be > stuck in f30-pending and not getting tagged with f30. That'll be the signing queue > I'm also concerned that once the signing queue starts moving, it's going to > tag older packages over the new builds that have

Re: /etc/yum.repos.d -> /etc/distro.repos.d

> Hi, > I am curious whether we can move our repo files from > /etc/yum.repos.d > to > /etc/distro.repos.d > > In Fedora 31 we are going to wipe away last left overs of YUM, so it really > does not have sense to keep `yum.repos.d`. > > DNF for ages parse config files from: >

Re: I cannot reach Kushal Das

On Mon, Jun 3, 2019 at 11:15 AM Miro Hrončok wrote: > > Hey, I am trying to get a response from Kushal since March. > > I was briefly in e-mail contact with him, but he has stopped responding > altogether. > > Anyone who can help me contact him? > >

Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

> Dne 30. 05. 19 v 8:39 Igor Gnatenko napsal(a): > > Last time I was about to propose this in F29, I did mass-rebuild myself > > and while decompressing was faster in most of the cases, the size was > > definitely worse. So definitely "Lower bandwidth on mirrors if we choose > > the highest

Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

On Thu, May 30, 2019 at 4:16 PM Ben Cotton wrote: > > Daniel added more contingency details to the proposal[1], but I want > to call out the contingency date. Right now it is listed as a week > before the final freeze, which is way too late. I would suggest that > the end of the mass rebuild is

Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

> Dne 30. 05. 19 v 14:57 Kevin Kofler napsal(a): > > Jason L Tibbitts III wrote: > > > >>> "BC" == Ben Cotton writes: > >> BC> * The recommended compression level is 19. The builds will take > >> BC> longer, but the additional compression time is negligible in the > >> BC> total build time

Re: Fedora 31 System-Wide Change proposal: No More i686 Kernels

On Mon, Jun 24, 2019 at 9:32 PM Chris Adams wrote: > > Once upon a time, Kevin Fenzi said: > > On 6/24/19 10:00 AM, Justin Forbes wrote: > > > On Mon, Jun 24, 2019 at 11:41 AM Zbigniew Jędrzejewski-Szmek > > > wrote: > > > > ...snip... > > > > >> Maybe the Change could be renamed to reflect the

Re: Non Intel sound cards' drivers issue

> For most of non Intel sound cards drivers are not installed automatically and > hard to find, install from software app and need to manually configure. > AlsaMixer and alsa utils (https://www.alsa-project.org) or like (if any) must > be built in and integrated to system's sound control panel

Re: Packages BuildRequiring python2-sphinx AND python3-devel

> There are 2 Python related changes in Fedora 31 that unfortunately interact > with > each other. > > https://fedoraproject.org/wiki/Changes/Python3.8 > https://fedoraproject.org/wiki/Changes/Sphinx2 > > The following packages (owners bcc'ed) BuildRequire both python2-sphinx AND > python3-devel.

Re: Firefox certificate

> > I think I've been hit by this Firefox mess: > > > >https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 > > > > or at least all the extensions in Firefox were just now disabled by an > > incredible coincidence. I know it's a Saturday and a public holiday > > weekend in a few countries,

Re: glibc-headers troubles with rawhide on ARM

On Wed, Jul 3, 2019 at 9:44 AM Nicolas Chauvet wrote: > > Le mer. 3 juil. 2019 à 04:35, David Airlie a écrit : > > > > On Tue, Jul 2, 2019 at 10:57 PM Olivier Fourdan wrote: > > > > > > Hi, > > > > > > On Tue, Jul 2, 2019 at 2:22 PM Pet

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Thu, Jun 27, 2019 at 5:20 PM Miro Hrončok wrote: > > On 27. 06. 19 17:15, Adam Williamson wrote: > > On Thu, 2019-06-27 at 12:32 +0200, Miro Hrončok wrote: > >> On 26. 06. 19 20:07, Adam Williamson wrote: > >>> On Wed, 2019-06-26 at 13:57 -0400, Ben Cotton wrote: >

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Fri, Jun 28, 2019 at 2:34 AM Miro Hrončok wrote: > > On 28. 06. 19 0:51, Stephen John Smoogen wrote: > > > > > > On Thu, 27 Jun 2019 at 18:49, Neal Gompa > > wrote: > > > > > > > What about postponing this change to F32? I'd prefer python2 to be > > >

Re: [Fedora-spins] roundup of failing images for 2019-07-07

On Mon, Jul 8, 2019 at 1:44 AM Kevin Fenzi wrote: > > So, what better way to relax on a sunday than to look at image compose > failures? :) > > 1. The armv7 workstation compose: > https://koji.fedoraproject.org/koji/taskinfo?taskID=36106518 > > This is failing because it cannot find 'epiphany'. >

Re: glibc-headers troubles with rawhide on ARM

On Mon, Jul 1, 2019 at 12:02 PM Florian Weimer wrote: > > * Olivier Fourdan: > > > Last Friday, I tried to update the xorg-x11-server package, everything > > went well on F30 but the compilation failed on ARM because of a > > missing header `sys/io.h`: > > > >

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Mon, Jul 1, 2019 at 9:02 PM Miro Hrončok wrote: > > On 01. 07. 19 16:21, Peter Robinson wrote: > > On Fri, Jun 28, 2019 at 2:34 AM Miro Hrončok wrote: > >> > >> On 28. 06. 19 0:51, Stephen John Smoogen wrote: > >>> > >>> > >&g

Re: Fedora 32: Deprecating WEXT

> We're considering removing support for Wireless Extensions from > NetworkManager in Fedora 32 time frame. > > A more modern Wi-Fi configuration API, cfg802111/nl80211, has been > available since 2007 and maybe there's no point in carrying the > maintenance burden anymore. It seems reasonable to

Re: efivar and mokutil long standing FTBFS

Firstly they're just FTBFS in F-30 This isn't exactly long standing, if it was F-26 like some that were retired I could completely understand that statement but F-30 is pushing the rhetoric a bit here. > efivar and mokutil fail to build from source. They have been retired, then > unretired

Re: Join the new Minimization Team

>> On Sat, 3 Aug 2019 at 20:34, Zbigniew Jędrzejewski-Szmek >> wrote: >> > >> > On Thu, Aug 01, 2019 at 10:25:55AM +0200, Adam Samalik wrote: >> > > I've already done some experiments with that. I used multi-stage builds >> > > with podman, but it's the same in principle. And yes, the sizes are

Re: efivar and mokutil long standing FTBFS

> On 13. 08. 19 19:43, Peter Robinson wrote: > > Firstly they're just FTBFS in F-30 This isn't exactly long > > standing, if it was F-26 like some that were retired I could > > completely understand that statement but F-30 is pushing the rhetoric > > a bit here.

Re: Why retire Python 2 packages and games that still work to end user ?

On Sun, Aug 11, 2019 at 9:33 AM Miro Hrončok wrote: > > On 11. 08. 19 3:45, Kevin Kofler wrote: > > Nico Kadel-Garcia wrote: > >> Maintaining python 2 requires maintaining a*lot* of infrastructure. > > What kind of infrastructure do you need to maintain a package that is (will > > be) no longer

Re: fedora-gpg-keys not updated yet again

On Mon, Aug 19, 2019 at 10:48 PM Kevin Fenzi wrote: > > So, a few things to note: > > * fedora-repos was updated for rawhide, however, unfortunately, It had > two extra spaces on the first line... " " which made gpg consider it > invalid. This is likely the cause of any breakage with rawhide

Re: Please fix the aarch64 g++ pic problems in f32 rawhide

On Thu, Aug 29, 2019 at 10:21 PM Philip Kovacs via devel wrote: > > Several of us are getting errors in our c++ packages related to missing PIC > flags in aarch64. > > Something is amiss there. A small snippet from openmpi: You're much better off including a couple of koji tasks/packages

Re: aarch64 toolchain regression?

> > On Tue, Sep 3, 2019 at 8:27 AM Rex Dieter wrote: > >> Builds that were previously succeeding (e.g. pulseaudio) are now failing > >> on aarch64 with errors like: > >> BUILDSTDERR: annobin: modules/module-loopback.c: ICE: Should be 64-bit > >> target > > > > See also: > > >

Re: Fedora 31: Noninstallable Python 2 packages to be retired just before the beta freeze

On Mon, Aug 26, 2019 at 10:25 AM Miro Hrončok wrote: > > In line with the approved Fedora 31 change, packages that fail to install due > to > missing Python 2 dependencies are to be removed. I plan to retire the > following > packages (or just drop their python2 subpackages) one day before the

Re: Fedora 31: Noninstallable Python 2 packages to be retired just before the beta freeze

On Mon, Aug 26, 2019 at 12:30 PM Miro Hrončok wrote: > > On 26. 08. 19 13:18, Peter Robinson wrote: > > On Mon, Aug 26, 2019 at 10:25 AM Miro Hrončok wrote: > >> > >> In line with the approved Fedora 31 change, packages that fail to install > >> du

Re: nothing provides pkgconfig(egl) needed by qt5-qtbase-devel

On Thu, Aug 22, 2019 at 6:59 PM Rex Dieter wrote: > > Rex Dieter wrote: > > > Rex Dieter wrote: > > > >> Miro Hrončok wrote: > >> > >>> I'm hit by the above error in rawhide. > >>> > >>> Is this expected or unexpected failure? > >> > >> Since all qtbase really needs is the egl headers (and not

Re: [HEADS UP] Fedora 32 Python 3.8 rebuilds have started in a side tag

On Fri, Aug 23, 2019 at 4:07 PM Kaleb Keithley wrote: > > > > On Wed, Aug 21, 2019 at 1:23 PM Miro Hrončok wrote: >> >> On 15. 08. 19 0:18, Miro Hrončok wrote: >> > Hello, in order to deliver Python 3.8, we are running a coordinated >> > rebuild in a >> > side tag. >> > >> >> The side tag was

Re: efivar and mokutil long standing FTBFS

On Tue, Sep 10, 2019 at 10:48 AM Miro Hrončok wrote: > > On 13. 08. 19 19:10, Miro Hrončok wrote: > > efivar and mokutil fail to build from source. They have been retired, then > > unretired and they still fail to build from source. > > > > Following the policy: > >

Re: Fedora in GNOME Online Accountes

On Wed, 18 Sep 2019, 11:21 Felipe Borges, wrote: > Hi! > > On Wed, Sep 18, 2019 at 11:07 AM wrote: > > > > Hello, I don't know if this is the right place to ask this question. > > Btw, on Fedora 31, in the Online Accounts list there is a "Fedora" > > voice alongside "Google", "Nextcloud" and

Re: Please fix the aarch64 g++ pic problems in f32 rawhide

> >> Several of us are getting errors in our c++ packages related to missing > >> PIC flags in aarch64. > >> > >> Something is amiss there. A small snippet from openmpi: > > >You're much better off including a couple of koji tasks/packages > >showing the issue, it's much easier to get some real

Re: Join the new Minimization Team

On Wed, 7 Aug 2019, 10:51 Adam Samalik, wrote: > > > On Mon, Aug 5, 2019 at 1:30 PM Zbigniew Jędrzejewski-Szmek < > zbys...@in.waw.pl> wrote: > >> On Sun, Aug 04, 2019 at 05:27:21PM +0200, Christian Glombek wrote: >> > Whoop this is great! >> > But I wonder why the scratch build sizes have gone

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

> > I disagree with ANY raised vector instruction requirement, considering that: > > * it would make Fedora incompatible with some hardware out there, > > That's already so for hardware which is at least of similar age to > SSE2-only x86_64, i.e. POWER7; my build logs show -mcpu=power8. For

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On Mon, Aug 5, 2019 at 3:44 PM Kaleb Keithley wrote: > > > There is a proposal[1] in upstream GlusterFS to drop 32-bit arches. > > The original proposal was to drop 32-bit with GlusterFS-7. GlusterFS-7 will > land in Fedora 31/rawhide soon. More than likely though it will not be > official

Re: Nonresponsive maintainers jchaloup, lkundrak, jkaluza

> lkundrak > https://bugzilla.redhat.com/show_bug.cgi?id=1737816 >https://bugzilla.redhat.com/show_bug.cgi?id=1716527 Lubomír is active, he's not always great at replying to emails but he actively updates thing like NetworkManager and I believe he's based in the Red Hat Brno office. Peter

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

> > After preliminary discussions with CPU vendors, we propose AVX2 as the > > new baseline. AVX2 support was introduced into CPUs from 2013 to > > 2015. See > > [https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX2 > > CPUs with AVX2]. > > This is not what I'd call a good

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

On Tue, Jul 23, 2019 at 11:09 AM Kevin Kofler wrote: > > Patrik Mattsson wrote: > > I would take the lowest denominator of features for CPUs of atleast 3 > > years of age considering how long some CPUs are being used in virtualized > > environments and at a lot of different cloud-providers (I've

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

On Tue, Jul 23, 2019 at 11:31 AM Nicolas Mailhot via devel wrote: > > Le 2019-07-23 07:02, drago01 a écrit : > > > Please just take back this change and come back at April first if it > > was supposed to be a joke - if not then submit again in about 10 > > years. > > Fedora used to have the x86

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

On Tue, Jul 23, 2019 at 7:37 PM Adam Williamson wrote: > > On Tue, 2019-07-23 at 13:32 -0400, Josh Boyer wrote: > > On Tue, Jul 23, 2019 at 12:39 PM Kevin Fenzi wrote: > > > On 7/22/19 10:34 PM, Igor Gnatenko wrote: > > > > On Tue, Jul 23, 2019 at 4:31 AM Igor Gnatenko > > > > wrote: > > > >

Re: Rolling out Phase I of rawhide package gating

On Wed, Jul 24, 2019 at 9:10 AM Pierre-Yves Chibon wrote: > > On Tue, Jul 23, 2019 at 10:35:13PM +0100, Tom Hughes wrote: > > On 23/07/2019 21:51, Pierre-Yves Chibon wrote: > > > > > When you run `fedpkg build` on Rawhide, your package will be built in a > > > new koji > > > tag (which will be

Re: Rolling out Phase I of rawhide package gating

> On Wed, Jul 24, 2019 at 09:14:05AM +0100, Peter Robinson wrote: > > On Wed, Jul 24, 2019 at 9:10 AM Pierre-Yves Chibon > > wrote: > > > > > > On Tue, Jul 23, 2019 at 10:35:13PM +0100, Tom Hughes wrote: > > > > On 23/07/2019 21:51, Pierre-Yves

Re: Fedora 31 Self-Contained Change proposal: AArch64 Xfce Desktop image

On Wed, Jul 24, 2019 at 11:24 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Jul 23, 2019 at 03:12:29PM -0400, Ben Cotton wrote: > > We currently offer Workstation, Minimal and Server images for use with > > AArch64 Single Board Computer's (SBC's). We would like to add a > > lighter weight

Re: Discussion around app retirements and categorizations by the CPE team

> > We posted this [1] blog today and want to open a mailing thread to > > garner feedback, field questions and get some thoughts from the > > Community on the approach that we in Community Platform Engineering > > (CPE) are taking. > > Sunsetting Mailman sounds pretty harsh. Will Red Hat do the

Re: Discussion around app retirements and categorizations by the CPE team

On Wed, Jul 17, 2019 at 11:46 AM Pierre-Yves Chibon wrote: > > Good Morning, > > We posted this [1] blog today and want to open a mailing thread to garner > feedback, field questions and get some thoughts from the Community on > the approach that we in Community Platform Engineering (CPE) are

Re: Fedora 31 Self-Contained Change proposal: AArch64 Xfce Desktop image

> On Wed, 2019-07-24 at 15:48 -0400, Matthew Miller wrote: > > On Wed, Jul 24, 2019 at 01:32:29PM +0100, Peter Robinson wrote: > > > In general there's usecases where a low resource desktop is useful, > > > such on devices with only 1Gb of RAM where Workstation d

Re: Orphaned packages looking for new maintainers (75 to be retired)

On Fri, Jul 26, 2019 at 1:14 PM Hans de Goede wrote: > > Hi, > > On 22-07-19 10:47, Miro Hrončok wrote: > > The following packages are orphaned and will be retired when they > > are orphaned for six weeks, unless someone adopts them. If you know for sure > > that the package should be retired,

Re: EPEL-8 builds

On Thu, Nov 7, 2019 at 4:36 PM Miroslav Suchý wrote: > > Dne 07. 11. 19 v 11:12 Peter Robinson napsal(a): > > I'd like to know why people are pushing EPEL-8 builds without engaging > > with the maintainers of the packages. > > Because they can? > Nothing in guideline

EPEL-8 builds

Hi, I'd like to know why people are pushing EPEL-8 builds without engaging with the maintainers of the packages. I've had a few packages where I'm the only maintainer and I've explicitly not built them for EPEL-8 for reasons yet people are now coming without any engagement what so ever and

Re: Issues with the retrace service?

> Dne 26. 10. 19 v 22:16 Frantisek Zatloukal napsal(a): > > > I think retrace service is running on RHEL 7.7 server and since we have > > > zstd rpms in Fedora 31 [0], it won't work. I > > don't know what's the ETA for fix, I can ask on Tuesday, if there is any > > update on this issue. > >

Re: EPEL-8 builds

g. > Dne 07. 11. 19 v 11:12 Peter Robinson napsal(a): > > Hi, > > > > I'd like to know why people are pushing EPEL-8 builds without engaging > > with the maintainers of the packages. I've had a few packages where > > I'm the only maintainer and I've explicitly

Re: No kernel package on Fedora Rawhide ppc64le?

On Sat, 7 Dec 2019, 14:46 Justin Forbes, wrote: > On Sat, Dec 7, 2019 at 5:01 AM Richard W.M. Jones > wrote: > >> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=39456403 >> >> DEBUG util.py:596: No matching package to install: 'kernel' >> >> I can see that ppc64le was temporarily

Re: RFC: Branch requests from non-maintainers

On Mon, Dec 2, 2019 at 2:04 PM Mat Booth wrote: > > On Mon, 2 Dec 2019 at 12:56, Igor Gnatenko > wrote: >> >> Hello, >> >> 3 months ago, Miro opened releng ticket[0] raising question whether >> non-maintainers (of some specific packages) being able to request >> branches. >> >> However, it

Re: [fedora-java] Re: Switching Maven and Ant to OpenJDK 11

> > On 26/10/2019 15:33, Neal Gompa wrote: > > > If anything, we're late to the party of moving to JDK 11 by default. > > > Java 8 has been EOL for a while now. > > Please do not spread misinformation like this. It is very unhelpful. > > > > Okay, sure, paid support continues for two more years,

Re: How to figure out why is Python 2 in critpath

On Thu, Oct 24, 2019 at 11:48 AM Miro Hrončok wrote: > I've recently updated Python 2 to the penultimate release for Python 2.7: > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-0d3fcae639 > > Bodhi tells me that Python 2 is in criptpath in Fedora 31. That almost > gave me a > heart

Re: Introducing Square 1

On Mon, Oct 28, 2019 at 8:00 PM Troy Dawson wrote: > > I would like to introduce a plan I call Square 1 [1][2] > > There are two goals to Square 1. > The first is to get, and keep, the core buildroot[3] packages, > self-hosting[4]. > The second is to get the list of core buildroot packages as

Re: [fedora-java] Re: Switching Maven and Ant to OpenJDK 11

> > However, you can also download releases from the AdoptOpenJDK > > site. Note, those downloads are built by Red Hat's OpenJDK team so you > > can rely on them being up to date with all the latest security patches > > and critical fixes. > > One clarification. Not *all* builds available at

Re: Do F31 updates not obsolete each other during freeze?

On Thu, Oct 17, 2019 at 10:34 AM Miro Hrončok wrote: > > Hey, I've just noticed something that I find a bit odd: > > This python38 update is on it's way to f31 stable: > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-c26f535d3c > > This newer python38 update was submitted yesterday: > >

Issues with the retrace service?

Hi all, It seems with F-31 on x86_64 the retrace service seems to fail every single time I try to submit a crash report, is there known issues with the service? Peter ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email

Re: Issues with the retrace service?

> I think retrace service is running on RHEL 7.7 server and since we have zstd > rpms in Fedora 31 [0], it won't work. I don't know what's the ETA for fix, I > can ask on Tuesday, if there is any update on this issue. It's a problem on RHEL-8 too then. > Until then, you'll probably have to

Re: Intent to replace bzr (bazaar) with brz (breezy)

> bzr (bazaar) FTBFS and is orphaned. > > I have a Python 3 replacement called breezy (brz) ready, but it has some > problems with remote repositories on Python 3.8, so I was not ready to build > it, > obsolete bzr and have a broken alternative. > > However, bzr now also fails to install, so it

Re: koji web interface is very slow

> > Anyone else seeing this? If so, anyone know the reason and plans to fix? > > Thanks! > > You'll have to be more specific than this, there has been some work put > recently > on its database which led to some improvements so if you still find koji slow, > you'll have to provide some more

Re: Old changelog entries removal

On Fri, Oct 4, 2019 at 8:26 PM Przemek Klosowski via devel wrote: > > On 10/3/19 12:19 PM, Matthew Miller wrote: > > On Thu, Oct 03, 2019 at 11:13:32AM -0500, Michael Cronenworth wrote: > >>> Remote changelog URLs might become inaccessible over time, making > >>> tracking down > >>> behavior

Re: Fedora 31 Self-Contained Change proposal: AArch64 Xfce Desktop image

> > The change proposal submitted here lists the Pi 4 among the supported > devices, whereas the wiki page does not. I checked the > SUPPORTED-BOARDS file in the accompanying documentation of > arm-image-installer and there is no rpi4 in the list of target boards. > Will the the Pi 4 be supported

Re: koji web interface is very slow

On Fri, Oct 11, 2019 at 10:13 AM Dominik 'Rathann' Mierzejewski wrote: > > On Friday, 11 October 2019 at 04:36, Orion Poplawski wrote: > > On 10/10/19 4:57 PM, Orion Poplawski wrote: > > > On 10/10/19 9:23 AM, Kevin Fenzi wrote: > [...] > > > > Pretty please can you all indicate approximately

Re: Seeking the maintainer of dbus-python

> > Hi, > > > > This package has been deprecated for a very long time (a decade?). > > Nothing should be using it anymore. Either use GDBus via PyGObject, or > > another D-Bus client library instead. If anybody wants to take this > > package, I'm sure that could be arranged. Working out a

Re: fleet-commander* main admin

On Tue, Feb 4, 2020 at 3:22 PM Miro Hrončok wrote: > > Hello Alberto, Oliver, > > given > > https://siliconislandblog.wordpress.com/2019/11/20/hanging-the-red-hat/ > > Should the three packages still owned by Alberto: > > fleet-commander > fleet-commander-admin > fleet-commander-client > >

Re: [Retired] gstreamer & gstreamer-plugins-base

On Fri, 31 Jan 2020, 14:53 Michael Catanzaro, wrote: > On Fri, Jan 31, 2020 at 2:47 pm, Dominik 'Rathann' Mierzejewski > wrote: > > I'm very well aware of the above, but I'm forced to use some > > proprietary > > software that is linked against gstreamer 0.10, so I need to maintain > > these

Re: Mass rebuild status

> > > Aside from a few stragglers, the mass rebuild is complete. > > > > That's great! Thanks for all of your work making this happen, Kevin. > > I do want to point out that at least one of my packages, GAPDoc, does > > not seem to have had a build started at all. For this package, it > >

Re: [Retired] gstreamer & gstreamer-plugins-base

> > > I'm very well aware of the above, but I'm forced to use some proprietary > > > software that is linked against gstreamer 0.10, so I need to maintain > > > these until the software in question gets ported to gstreamer1. > > > > gstreamer0.10 has not received security updates -- or security

Re: Announcement: EPEL Steering Committee Changes

> > It has been a pleasure for me to be a part of and help lead the > > EPEL steering committee for the last couple of years. It has not > > always been smooth sailing but I have found it an enjoyable experience. > > > > However, as you may know the Fedora project will be moving to a > > different

Re: [Retired] gstreamer & gstreamer-plugins-base

On Mon, 10 Feb 2020, 08:44 John M. Harris Jr, wrote: > On Sunday, February 9, 2020 3:54:51 PM MST Neal Gompa wrote: > > On Sun, Feb 9, 2020 at 5:36 PM John M. Harris Jr > > wrote: > > > > > > > > > On Friday, January 31, 2020 7:58:55 AM MST P

Re: [Retired] gstreamer & gstreamer-plugins-base

> > > > > As long as it builds and functions, why remove it? > > > > > > > > Because it has lots of critical vulnerabilities and endangers end-user > > > > devices. > > > > > > Please name a couple. Nobody has provided a single specific case of an > > > unfixed security vulnerability affecting

Re: [Retired] gstreamer & gstreamer-plugins-base

> On Monday, 10 February 2020 at 10:07, Vitaly Zaitsev via devel wrote: > > On 10.02.2020 09:43, John M. Harris Jr wrote: > > > As long as it builds and functions, why remove it? > > > > Because it has lots of critical vulnerabilities and endangers end-user > > devices. > > Please name a couple.

Re: New Release Freeze Times

> On Friday, February 21, 2020 10:52:27 PM MST Miro Hrončok wrote: > > On 22. 02. 20 1:28, John M. Harris Jr wrote: > > > > > I really must disagree. > > > > > > In my opinion, once you simply disagree with literally everything, your > > feedback no longer gives any significant meaning for the

Re: Self Introduction: Chihurumnaya Ibiam

Welcome! I've been enjoying working with you on the sugar desktop. You're work to help bring it to python3 and updating it is fantastic for both communities. Peter On Wed, Feb 19, 2020 at 11:21 PM Chihurumnaya Ibiam wrote: > > Good day, > > I've been working mostly with python at Sugar Labs

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 4:59 AM Dan Čermák wrote: > > Felix Schwarz writes: > > > Am 21.01.20 um 21:48 schrieb Guido Aulisi: > >> I totally agree with Fabio, I can’t think of a single reason we should > >> dismiss > >> pagure. > > > > Gitlab is used by many free software communities like

Re: gcc 10: Default to -fno-common, multiple definitions of ...

> > On Tuesday, January 21, 2020 7:35:03 AM EST Miro Hrončok wrote: > > > This is a known thing in gcc 10: > > > > > > https://gcc.gnu.org/gcc-10/porting_to.html#common > > > > > > "Default to -fno-common > > > > > > A common mistake in C is omitting extern when declaring a global variable > > >

Re: Git Forge Requirements: Please see the Community Blog

> >> And any discussion of GitHub isn't going to involve self-hosted, it's > >> going to involve GitHub.com, which means we're talking about losing > >> more of our independence as a project. This is one of those things > >> that I'm not sure is a wise move. > > > > Well since we have a request

Re: List of long term FTBFS packages to be retired in February

On Mon, Jan 6, 2020 at 10:35 AM Miro Hrončok wrote: > > Dear maintainers. > > Based on the latest fail to build from source policy, the following packages > will be retired from Fedora 32 approximately one week before branching > (February > 2020). > > Policy: >

Re: List of long term FTBFS packages to be retired in February

On Mon, Jan 6, 2020 at 11:34 AM Miro Hrončok wrote: > > On 06. 01. 20 12:17, Peter Robinson wrote: > > On Mon, Jan 6, 2020 at 10:35 AM Miro Hrončok wrote: > >> > >> Dear maintainers. > >> > >> Based on the latest fail to build from source policy, t

Re: Reducing broken dependencies in fedora (32) repositories

On Wed, Mar 11, 2020 at 12:58 PM Randy Barlow wrote: > > On 3/9/20 11:53 AM, Fabio Valentini wrote: > > Source-only rust packages (those only shipping noarch -devel > > subpackages) have been untagged from f32 on purpose by Igor. For > > reasons I disagree with:) > > I too wish that we kept the

Re: f32-backgrounds available for testing

> > Hello team, > > > > f32-backgrounds is available for testing on > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-ed62604eca > > > > For the Design team, new change is the drop of standard, normalish, tv, > > tv-wider folders in favour of a single wallpapers (aside the time of day > >

Re: Announcing start of DNF 5 development

> > Hello everyone, > > I'm pleased to announce start of DNF 5 development. We are planning to > > deliver a module stream or a COPR repo during Fedora 33 development for > > early adopters and tool developers and we're hoping in getting a stable > > version into Fedora 34. > > > > Can it be: >

Re: Fedora 32 compose report: 20200308.n.0 changes

On Sun, Mar 8, 2020 at 3:09 PM Fedora Branched Report wrote: > > OLD: Fedora-32-20200307.n.0 > NEW: Fedora-32-20200308.n.0 > > = SUMMARY = > Added images:0 > Dropped images: 8 > Added packages: 0 > Dropped packages:9 > Upgraded packages: 0 > Downgraded packages: 0

Re: [Test-Announce] Taskotron Going EOL on 2020-04-30

> > It's not a direct response to your question, but one important fact is that > > our beefy machines in Fedora Infrastructure are out of warranty now (and > > replacing them would cost a lot of money, I assume). That's one of the > > major reasons why they won't be migrated to the new datacenter

Re: libIDL missing on F32

On Tue, Mar 10, 2020 at 6:17 PM Antonio Trande wrote: > > Hi all. > > libIDL missing on F32. Please, fix it. It has been fixed for builds, it will be fixed in the next compose. Out of interest which packages are affected? ___ devel mailing list --

<    7   8   9   10   11   12   13   14   15   16   >