Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

On Mon, 14 Jan 2019 08:34:14 +0100 Miro Hrončok wrote: > On 07. 12. 18 20:51, Stephen John Smoogen wrote: > > The facility that houses the Fedora s390 server will have a major > > power outage starting 2019-01-11 22:00 UTC and ending 2019-01-14 > > 22:00 UTC. During this time the s390 builders wi

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

On Mon, 14 Jan 2019 10:48:59 +0300 Vascom wrote: > How about switch build rpms for exotic and slow arches (arm, s390...) arm is slow, but not exotic s390 is exotic, but not slow > from hardware to cross-compile on x86_64? > mock can do it via qemu-user-static emulation has functional deficienc

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

It must produce the same results as real hw. Or mock parameter --forcearch must be removed. пн, 14 янв. 2019 г. в 12:02, Dan Horák : > > On Mon, 14 Jan 2019 10:48:59 +0300 > Vascom wrote: > > > How about switch build rpms for exotic and slow arches (arm, s390...) > > arm is slow, but not exotic >

[Test-Announce] Fedora 30 Rawhide 20190114.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 30 Rawhide 20190114.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Fedora Rawhide-20190114.n.0 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 15 of 47 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 63/131 (x86_64), 17/24 (i386), 1/2 (arm) New failures (same test not

Orphaned packages to be retired

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, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life I plan to

System freezes randomly - need to reboot

Hello everyone, ## $ cat /etc/os-release NAME=Fedora VERSION="29.20181230.0 (Workstation Edition)" ID=fedora VERSION_ID=29 VERSION_CODENAME="" PLATFORM_ID="platform:f29" PRETTY_NAME="Fedora 29.20181230.0 (Workstation Edition)" VARIANT="Workstation Edition" VARIANT_ID=workstati

RE: System freezes randomly - need to reboot

Do you have a nvidia card? Joseph D. Wagner From: arnaud gaboury Sent: Monday, January 14, 2019 4:31 AM To: Development discussions related to Fedora Subject: System freezes randomly - need to reboot Hello everyone, ## $ cat /etc/os-release NAME=Fedora VERSION="

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

On Sun, Jan 13, 2019 at 04:38:37PM -0800, Kevin Fenzi wrote: > On 1/13/19 4:11 PM, Kevin Kofler wrote: > > On Fri, 7 Dec 2018 at 14:51, Stephen John Smoogen wrote: > >> During this time the s390 builders will not be available and all > >> builds will be queued up until they are available and will n

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

Dne 14. 01. 19 v 13:59 Daniel P. Berrangé napsal(a): > On Sun, Jan 13, 2019 at 04:38:37PM -0800, Kevin Fenzi wrote: >> On 1/13/19 4:11 PM, Kevin Kofler wrote: >>> On Fri, 7 Dec 2018 at 14:51, Stephen John Smoogen wrote: During this time the s390 builders will not be available and all bui

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

On Mon, Jan 14, 2019 at 02:11:38PM +0100, Vít Ondruch wrote: > > Dne 14. 01. 19 v 13:59 Daniel P. Berrangé napsal(a): > > On Sun, Jan 13, 2019 at 04:38:37PM -0800, Kevin Fenzi wrote: > >> On 1/13/19 4:11 PM, Kevin Kofler wrote: > >>> On Fri, 7 Dec 2018 at 14:51, Stephen John Smoogen wrote: >

Re: F30 Self-Contained Change proposal: krb5 crypto modernization

On Tue, Jan 08, 2019 at 04:45:53PM -0600, Jason L Tibbitts III wrote: > > "RH" == Robbie Harwood writes: > > RH> Ah, I see, you're talking about the case when the enctype is already > RH> not permitted. That all makes sense then. Hi, after re-reading this thread, I'm still unclear on some

Schedule for Monday's FESCo Meeting (2019-01-14)

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 '2019-01-14 15:00 UTC' Links to all issues to be

responding to CVEs

Is there any specific requirement to change packages in response to CVEs, specifically if they appear to be bogus? I can't find anything specifying that. I ask because three CVEs have triggered automated bug reports against libxsmm . I don't

Re: responding to CVEs

On Mon, Jan 14, 2019 at 01:35:10PM +, Dave Love wrote: > Is there any specific requirement to change packages in response to > CVEs, specifically if they appear to be bogus? I can't find anything > specifying that. > > I ask because three CVEs have triggered automated bug reports against > li

Re: Is Bodhi's fedmsg integration in the UI useful?

On Wed, Jan 9, 2019 at 7:01 PM Randy Barlow wrote: > Greetings again! > > In my quest to kill Bodhi features so I can have a smaller codebase to > maintain, I am considering getting rid of the fedmsg integration in the > web interface: > > https://github.com/fedora-infra/bodhi/issues/2913 > > I d

Re: System freezes randomly - need to reboot

On 1/14/19 1:31 PM, arnaud gaboury wrote: > Hello everyone, > > ## > $ cat /etc/os-release > NAME=Fedora > VERSION="29.20181230.0 (Workstation Edition)" > ID=fedora > VERSION_ID=29 > VERSION_CODENAME="" > PLATFORM_ID="platform:f29" > PRETTY_NAME="Fedora 29.20181230.0 (Workstation E

Re: responding to CVEs

On Mon, Jan 14, 2019 at 7:35 AM, Dave Love wrote: I ask because three CVEs have triggered automated bug reports against libxsmm . I don't understand why the CVEs were issued, since a problem with unrealistic input to a (rather rarely used)

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

Neal Gompa wrote: > Sorry, I was referring to systems like the OverDrive 1000[1], which > are PC form-factor ARM systems. > > I have one of these myself, and they're very handy for doing > reasonable development of software on ARM. > > [1]: https://softiron.com/development-tools/overdrive-1000/

Re: Orphaned packages to be retired

I'll take python-txsocksx. https://pagure.io/releng/issue/8056 -Gwyn On 1/14/19 6:18 AM, 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, p

Re: System freezes randomly - need to reboot

On Mon, Jan 14, 2019 at 1:34 PM Joseph D. Wagner wrote: > Do you have a nvidia card? > No. Lenovo yoga with Intel > > > Joseph D. Wagner > > > > *From:* arnaud gaboury > *Sent:* Monday, January 14, 2019 4:31 AM > *To:* Development discussions related to Fedora < > devel@lists.fedoraproject.org

Re: Fedora rawhide compose report: 20190114.n.0 changes

On Mon, 14 Jan 2019 13:54:02 + Fedora Rawhide Report wrote: > OLD: Fedora-Rawhide-20190108.n.0 > NEW: Fedora-Rawhide-20190114.n.0 > > = SUMMARY = > Added images:3 > Dropped images: 1 > Added packages: 12 > Dropped packages:3 &g

[modularity] Querying modular content — workaround

I've just published a blog post about querying modular content [1] which might be useful if you maintain modules. It should help you, at least partly, in the following example scenarios: Rebuilding dependencies after major changes * A new version of an interpreted language lands in Fedora as a se

Re: System freezes randomly - need to reboot

On Mon, Jan 14, 2019 at 3:14 PM Michal Schmidt wrote: > On 1/14/19 1:31 PM, arnaud gaboury wrote: > > Hello everyone, > > > > ## > > $ cat /etc/os-release > > NAME=Fedora > > VERSION="29.20181230.0 (Workstation Edition)" > > ID=fedora > > VERSION_ID=29 > > VERSION_CODENAME="" > >

Re: langpacks (Re: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks)

Le 2019-01-11 19:33, Tomasz Kłoczko a écrit : On Fri, 11 Jan 2019 at 13:37, Jakub Jelinek wrote: So in 107 current Fedora specs are used %lang() macros. Probably some of them can be removed by proper use %find_lang. The problem with _install_langs is that there is no easy way to change it af

Re: Fedora rawhide compose report: 20190114.n.0 changes

On Mon, Jan 14, 2019 at 2:52 PM Dan Horák wrote: > > On Mon, 14 Jan 2019 13:54:02 + > Fedora Rawhide Report wrote: > > > OLD: Fedora-Rawhide-20190108.n.0 > > NEW: Fedora-Rawhide-20190114.n.0 > > > > = SUMMARY = > > Added images:3 >

Re: Fw: Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14

Neal Gompa writes: > > * Buildbot (Python 3) > * Jenkins (Java) > * Vespene (Python 3) Just FYI: vespene has been recently discontinued: https://medium.com/@michaeldehaan/discontinuing-vespene-17fd9c0f3079 (also iirc it was licensed under Apache license + commons clause, which would make inclus

Re: responding to CVEs

On Mon, 14 Jan 2019 13:35:10 +, you wrote: >Is there any specific requirement to change packages in response to >CVEs, specifically if they appear to be bogus? I can't find anything >specifying that. > >I ask because three CVEs have triggered automated bug reports against >libxsmm

Agenda for Tuesday's Modularity Working Group Meeting (2019-01-15)

Find below a list of topics which are planned to be discussed in the Fedora Modularity Working Group meeting on Tuesday at 15:00 UTC in #fedora-meeting-3 on irc.freenode.net. To find out when this is in your local time zone, check the Fedora Calendar (if you've set it and are logged in): https:/

Re: responding to CVEs

Dave Love wrote: > I ask because three CVEs have triggered automated bug reports against > libxsmm . I don't > understand why the CVEs were issued, since a problem with unrealistic > input to a (rather rarely used) development tool doesn't stri

Re: Fedora rawhide compose report: 20190114.n.0 changes

On Mon, 14 Jan 2019 15:11:52 + Peter Robinson wrote: > On Mon, Jan 14, 2019 at 2:52 PM Dan Horák wrote: > > > > On Mon, 14 Jan 2019 13:54:02 + > > Fedora Rawhide Report wrote: > > > > > OLD: Fedora-Rawhide-20190108.n.0 > > > NEW: Fedora-R

Re: responding to CVEs

Dave Love wrote: > I don't > understand why the CVEs were issued, since a problem with unrealistic > input to a (rather rarely used) development tool doesn't strike me as a > security problem. Your "surely nobody would do that" attitude is one of the major causes why security holes are so abundan

Summary/Minutes from today's FESCo Meeting (2019-01-14)

= #fedora-meeting-1: FESCO (2019-01-14) = Meeting started by sgallagh at 15:01:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2019-01-14/fesco.2019-01-14-15.01.log.html . Meeting

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Sat, Jan 12, 2019 at 07:51:34PM +0100, Kevin Kofler wrote: > I think John's statement was pretty clear: The artificial distinction > between "Editions" and "Spins" needs to go away. It's not an artificial distinction. Editions are particular solutions targeting particular key use cases identif

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

On Sun, Jan 13, 2019 at 02:15:19PM -0500, Stephen John Smoogen wrote: > > Then can we change the title of the thread? > Nico, you know this better than me. This is email not a forum. People can > rename threads but depending on the email software it will just look like a > completely different thre

Re: responding to CVEs

On Monday, January 14, 2019 8:35:10 AM EST Dave Love wrote: > On that basis I didn't bother including the upstream patch with the > latest version, and I'm inclined to close the issues as wontfix. If these vulnerabilities are already fixed, surely it's best to just apply the patch that fixes it a

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Monday, January 14, 2019 12:56:30 PM EST Matthew Miller wrote: > I think it's better to not focus so much on the central page or on the > "getfedora" brochure site, and to instead make the page for each particular > solution more useful and more discoverable. The easiest way to make any of the

Re: F30 Self-Contained Change proposal: krb5 crypto modernization

Tomasz Torcz writes: > On Mon, Jan 07, 2019 at 04:12:47PM -0500, Robbie Harwood wrote: >> Adam Williamson writes: >> >> > On Thu, 2019-01-03 at 22:40 -0600, Jason L Tibbitts III wrote: >> > >> >> But to be fair, MIT krb5 is not known for having great error output. >> >> Not being able to start

Re: Editions vs. Spins

On 1/13/2019 10:19 AM, Zbigniew Jędrzejewski-Szmek wrote: On Sat, Jan 12, 2019 at 07:51:34PM +0100, Kevin Kofler wrote: Stephen John Smoogen wrote: Side note, I was at a loss of what you were getting at. There were several ways it could be interpreted and has been used by people in the past to

Re: Editions vs. Spins

On Mon, Jan 14, 2019 at 1:48 PM Japheth Cleaver wrote: > On 1/13/2019 10:19 AM, Zbigniew Jędrzejewski-Szmek wrote: > > On Sat, Jan 12, 2019 at 07:51:34PM +0100, Kevin Kofler wrote: > >> Stephen John Smoogen wrote: > >>> Side note, I was at a loss of what you were getting at. There were > several

Re: F30 Self-Contained Change proposal: krb5 crypto modernization

On ma, 14 tammi 2019, Robbie Harwood wrote: Tomasz Torcz writes: On Mon, Jan 07, 2019 at 04:12:47PM -0500, Robbie Harwood wrote: Adam Williamson writes: > On Thu, 2019-01-03 at 22:40 -0600, Jason L Tibbitts III wrote: > >> But to be fair, MIT krb5 is not known for having great error output.

Re: Organizing a "packager experience" objective and working group

On Fri, Jan 11, 2019 at 8:11 AM Igor Gnatenko wrote: > > I'm definitely interested to help (I have 6+ years experience as a packager)! > > Can we have a topic on discussion.fp.o? I think it is much easier to discuss > such things there. Thanks! Also thanks to everyone who's expressed interest in

Re: F30 Self-Contained Change proposal: krb5 crypto modernization

Zbigniew Jędrzejewski-Szmek writes: > On Tue, Jan 08, 2019 at 04:45:53PM -0600, Jason L Tibbitts III wrote: >> > "RH" == Robbie Harwood writes: >> >> RH> Ah, I see, you're talking about the case when the enctype is already >> RH> not permitted. That all makes sense then. > > Hi, > > after

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

Matthew Miller wrote: > It's not an artificial distinction. Editions are particular solutions > targeting particular key use cases identified by the Fedora Board (and now > Council). This is different from a desktop Spin, which is focused on > delivering that particular technology, or from Labs, wh

Re: Organizing a "packager experience" objective and working group

On Fri, Jan 11, 2019 at 12:37 PM Michael Cronenworth wrote: > > On 1/11/19 9:18 AM, Matthew Miller wrote: > > Can we apply the same "flag and remove" approach as currently used in Copr? > > I'd rather have a licensing sign-off step. Allow fedora-review to automate > the spec > review and build te

Re: Organizing a "packager experience" objective and working group

On Mon, Jan 14, 2019 at 3:19 PM Ben Rosser wrote: > > On Fri, Jan 11, 2019 at 12:37 PM Michael Cronenworth wrote: > > > > On 1/11/19 9:18 AM, Matthew Miller wrote: > > > Can we apply the same "flag and remove" approach as currently used in > > > Copr? > > > > I'd rather have a licensing sign-off

F30 System-Wide Change proposal (update): DNF Better Counting (was: DNF UUID)

This is an updated version of the DNF UUID proposal based on feedback received on the mailing list. https://fedoraproject.org/wiki/Changes/DNF_Better_Counting == Summary == Right now, we estimate installed Fedora systems by counting unique IP addresses which show up in our updates mirror statisti

F30 Self-Contained Change proposal: libcrypt.so.1 (compatibility library for POSIX): Let encrypt, encrypt_r, setkey, setkey_r, and fcrypt return ENOSYS instead of performing any real operation

Remove real functionality from encrypt, encrypt_r, setkey, setkey_r, and fcrypt from the libxcrypt.so.1 compatibility library and let those functions set "errno" to "ENOSYS" when invoked. == Owner == * Name: [[User:besser82 | Björn Esser]] == Detailed Description == In [[Changes/FullyRemoveDepr

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Mon, Jan 14, 2019 at 12:05 PM, John Harris wrote: The easiest way to make any of the Spins more accessible, for them to have any chance comparable to the prominent advertising of Workstation and similar options, would be to make them more prominent on the "getfedora" index. This also have

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Mon, Jan 14, 2019 at 6:20 PM wrote: > On Mon, Jan 14, 2019 at 12:05 PM, John Harris > wrote: > > The easiest way to make any of the Spins more accessible, for them to > > have any > > chance comparable to the prominent advertising of Workstation and > > similar > > options, would be to make t

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Mon, Jan 14, 2019 at 09:12:51PM +0100, Kevin Kofler wrote: > > It's not an artificial distinction. Editions are particular solutions > > targeting particular key use cases identified by the Fedora Board (and now > > Council). This is different from a desktop Spin, which is focused on > > deliver

I will be giving a Fedora Classroom on Tuesday at 11:00 EST on Buildah

Building Container Images with Buildah. https://fedoramagazine.org/fedora-classroom-building-container-images-with-buildah/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedor

Re: Unannounced soname bump: libcapstone.so.3 -> libcapstone.so.4

Thank you. Michal Ambroz -- Původní e-mail -- Od: Richard W.M. Jones Komu: Björn'besser82' Esser Datum: 12. 1. 2019 8:35:45 Předmět: Re: Unannounced soname bump: libcapstone.so.3 -> libcapstone.so.4 " This was fixed upstream in capstone. I'm rebuilding capstone & qemu (again)

Re: Editions vs. Spins (was: Re: F30: System-Wide Change proposal: DNF UUID)

On Monday, January 14, 2019 6:48:47 PM EST Matthew Miller wrote: > Merging Core and Extras into one thing was absolutely the > right thing to do for the project, but not having a unique name for the > resulting OS was a mistake and leads to this. Ah well. In your opinion, is the purpose of the Fed

Fedora testing-20190115.0 compose check report

No missing expected images. Failed openQA tests: 2/2 (x86_64) New failures (same test not failed in updates-20190114.0): ID: 344970 Test: x86_64 AtomicHost-dvd_ostree-iso install_default URL: https://openqa.fedoraproject.org/tests/344970 ID: 344971 Test: x86_64 AtomicHost-dvd_ostree-is

Fedora updates-20190115.0 compose check report

No missing expected images. Failed openQA tests: 2/2 (x86_64) ID: 344972 Test: x86_64 AtomicHost-dvd_ostree-iso install_default URL: https://openqa.fedoraproject.org/tests/344972 ID: 344973 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org

Re: Editions vs. Spins

On 1/14/2019 4:58 PM, John Harris wrote: On Monday, January 14, 2019 6:48:47 PM EST Matthew Miller wrote: Merging Core and Extras into one thing was absolutely the right thing to do for the project, but not having a unique name for the resulting OS was a mistake and leads to this. Ah well. In y

[Fedocal] Reminder meeting : Modularity WG (weekly)

Dear all, You are kindly invited to the meeting: Modularity WG (weekly) on 2019-01-15 from 15:00:00 to 16:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Meeting of the Modularity Working Group. More information available at: [Modularity Working Group wiki page](

Re: responding to CVEs

On 01/14/2019 09:38 PM, Kevin Kofler wrote: > Dave Love wrote: >> I ask because three CVEs have triggered automated bug reports against >> libxsmm . I don't >> understand why the CVEs were issued, since a problem with unrealistic >> input to a

Re: F30 Self-Contained Change proposal: krb5 crypto modernization

> > after re-reading this thread, I'm still unclear on some issues. Please > > correct me if I'm wrong. > > > > - The plan is to patch the Fedora package to remove support for some > > algorithms above and beyond what upstream is removing right now. > > Upstream has never removed an algorithm. H