Re: efivar and mokutil long standing FTBFS

> On Tue, Sep 10, 2019 at 01:38:03PM +0200, Miro Hrončok wrote: > > We're in final freeze now. Any progress? > > Zbyszek I poked mokutil with a couple of upstream fixes, now it fails only on i686. https://koji.fedoraproject.org/koji/taskinfo?taskID=38515227 _

Re: efivar and mokutil long standing FTBFS

On Thu, Oct 24, 2019 at 07:45:03AM -, Leigh Scott wrote: > > On Tue, Sep 10, 2019 at 01:38:03PM +0200, Miro Hrončok wrote: > > > > We're in final freeze now. Any progress? > > > > Zbyszek > > I poked mokutil with a couple of upstream fixes, now it fails only on i686. > > https://koji.fedora

Re: Modularity and the system-upgrade path

This is a policy choice, not a technical matter. If modules became more > popular, and the dependencies between modules grew, we'd need > to settle on similar rules, where bigger changes are done with a certain > cadence. This is why I think that the "independent lifecycles for modules" > are illus

Re: Modularity and all the things

Hey Petr, First of all, thanks for writing this up, much appreciated. On Wed, Oct 23, 2019 at 2:52 PM Petr Šabata wrote: > > Starting a new thread since the old one is hard to navigate at this point. > > Modularity is a distribution-level change and requires some mindset > shift from packagers a

Re: Modularity and all the things

Are you proposing to _do_ those things, or proposing that someone else > oughta? > This is an unfair statement! I thought Fedora is a community of people. In the community, we have programmers, visionaries, idealists, testers, graphics ... and we also have users, that only know if they like or di

Re: Modularity and all the things

On Wed, Oct 23, 2019 at 7:07 PM Matthew Miller wrote: > > On Wed, Oct 23, 2019 at 12:44:06PM -0400, Randy Barlow wrote: > > On Wed, 2019-10-23 at 14:41 +0200, Petr Šabata wrote: > > > We currently don’t have any other proposal that would fulfill the vision > > > of our Objective and the needs of o

Re: Modularity and all the things

On Thu, Oct 24, 2019 at 10:40 AM Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > > This basically makes modularity not useful for many things: > > 1. People will have to have different workflows between "default" > version (standard workflow, as we have today) and "modular" version. >

Re: Modularity and the system-upgrade path

On Thu, Oct 24, 2019 at 4:31 AM Lukas Ruzicka wrote: > > As far as tooling is concerned, I have been seeing complaints about DNF doing > a bad job, but from the perspective of acceptance > testing, it's the DNF operations that usually work fine with installing, > enabling, disabling, removing, r

Re: efivar and mokutil long standing FTBFS

> On Thu, Oct 24, 2019 at 07:45:03AM -, Leigh Scott wrote: > > > mokutil.c:1977:16: error: comparison of integer expressions of different > signedness: > 'unsigned int' and 'int' [-Werror=sign-compare] > 1977 | if (salt_size > settings_len - (next - settings)) { > |^

Re: Orphaned packages looking for new maintainers

On 24. 10. 19 4:21, Michal Ambroz wrote: > Why I'm not listed as the original owner? Pagure doesn't know any concept of "original owner". When a package is orphaned by releng, the owner is replaced by orphan user. Sometimes, there are co-maintainers and they stay as co-miantainers. I've opene

Re: A new workflow for newcomers

On Wed, 2019-10-23 at 13:00 -0400, Matthew Miller wrote: > On Tue, Oct 22, 2019 at 12:17:26AM +0200, alcir...@gmail.com wrote: > > [2] https://fedoraproject.org/wiki/Welcome > > can we get this onto the docs site? I forgot that. There is already a PR https://pagure.io/Fedora-Council/council-docs/

Re: Modularity and the system-upgrade path

Neal Gompa wrote: > On Thu, Oct 24, 2019 at 4:31 AM Lukas Ruzicka wrote: >> I believe, that if modularity was opt-in, we would be able to use it just >> fine, as it is designed now with some little tweakings, such as DNF >> providing enough info on retired or discontinued streams, offering a >> p

How to figure out why is Python 2 in critpath

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 attack. I've checked in PDC and indeed it is 😱 Reading https://fedora

Non-responsive maintainer wzzrd

Hi, I'm sending this e-mail according to non-responsive maintainer policy with link to created issue in bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1765093 This maintainer has also two other issues on him: https://bugzilla.redhat.com/show_bug.cgi?id=1605696 https://bugzilla.redhat.c

Re: Modularity and all the things

IMHO: Igor Gnatenko wrote: > * Do we want to support "buildroot-only" packages? No, because this contradicts both the transparency expected from a community-developed project and the self-hosting expectations. > * Do we want to build streams against all combinations (aka > py{2,3}+nodejs{8,9,10

Re: Modularity and all the things

Igor Gnatenko wrote: > On Wed, Oct 23, 2019 at 2:52 PM Petr Šabata wrote: >> While these issues are being resolved, we are considering temporarily >> disallowing default streams in Fedora. I don’t want to abandon the >> idea completely, as doing so reduces the motivation to actually build >> modu

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 attack

[Bug 1765097] [RFE] EPEL8 branch of perl-Browser-Open

https://bugzilla.redhat.com/show_bug.cgi?id=1765097 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[feedback needed] VirtIO Windows Drivers - new installer

Hi, as part of the work on oVirt 4.4, the team rewrote the VirtiIO Windows Drivers installer using the open source framework WiX. Thanks to the virtio-win maintainer, the new installer is not shipped anymore within oVirt Guest Tools ISO: it's shipped now directly into VirtIO Windows ISO[1] Please

Re: utf8cpp major update

On Wednesday, 23 October 2019 at 16:27, Dominik 'Rathann' Mierzejewski wrote: [...] > Only one (ledger) requires some porting as it's using a deprecated > method which got dropped in utf8cpp-3.0. So, the good news is that this is already fixed upstream and I've just mentioned that in the bug repor

Re: Modularity and all the things

On Thu, Oct 24, 2019 at 6:56 AM Kevin Kofler wrote: > > IMHO: > > Igor Gnatenko wrote: > > * Do we want to support "buildroot-only" packages? > > No, because this contradicts both the transparency expected from a > community-developed project and the self-hosting expectations. > I think there's s

Re: Modularity and all the things

On Thu, Oct 24, 2019 at 4:45 AM Lukas Ruzicka wrote: > > > Are you proposing to _do_ those things, or proposing that someone else >> oughta? >> > > This is an unfair statement! > > I thought Fedora is a community of people. In the community, we have > programmers, visionaries, idealists, testers,

Re: Modularity and all the things

On Thu, 24 Oct 2019 at 06:55, Kevin Kofler wrote: > > IMHO: > > Igor Gnatenko wrote: > > * Do we want to support "buildroot-only" packages? > > No, because this contradicts both the transparency expected from a > community-developed project and the self-hosting expectations. > I am in agreement w

Fedora rawhide compose report: 20191024.n.0 changes

OLD: Fedora-Rawhide-20191023.n.0 NEW: Fedora-Rawhide-20191024.n.0 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 1 Dropped packages:23 Upgraded packages: 111 Downgraded packages: 0 Size of added packages: 12.27 MiB Size of dropped packages

Re: Modularity and all the things

On Thu, 24 Oct 2019 at 08:10, Stephen Gallagher wrote: > > > > On Thu, Oct 24, 2019 at 4:45 AM Lukas Ruzicka wrote: >> >> >> >>> Are you proposing to _do_ those things, or proposing that someone else >>> oughta? >> >> >> This is an unfair statement! >> >> I thought Fedora is a community of people

Re: Modularity and the system-upgrade path

On Thu, Oct 24, 2019 at 12:42:27PM +0200, Kevin Kofler wrote: > Neal Gompa wrote: > > > On Thu, Oct 24, 2019 at 4:31 AM Lukas Ruzicka wrote: > >> I believe, that if modularity was opt-in, we would be able to use it just > >> fine, as it is designed now with some little tweakings, such as DNF > >>

Fedora-Rawhide-20191024.n.0 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 4 of 45 required tests failed, 2 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.clo

Re: Modularity and all the things

*There's a very large difference between feedback like "I think the user experience is suboptimal here, for this reason" and "I don't like the entire design, you should scrap it and start over".* Well, I can agree with that. > > In the first case, it's possible to incorporate that into an existi

Fedora 31 compose report: 20191024.n.0 changes

OLD: Fedora-31-20191023.n.0 NEW: Fedora-31-20191024.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:3 Upgraded packages: 2 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:7.47 MiB Size of

Fedora-31-20191024.n.0 compose check report

No missing expected images. Failed openQA tests: 5/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-31-20191023.n.0): ID: 475942 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/475942 ID: 476012 Test: x86_64 universal support_ser

Re: Modularity and all the things

On Wed, 2019-10-23 at 12:58 -0400, Matthew Miller wrote: > Are you proposing to _do_ those things, or proposing that someone > else > oughta? This feels like an attempt to suggest that I have made a demand when I have not. I'm willing to give you the benefit of the doubt, but I suggest avoiding la

Re: [feedback needed] VirtIO Windows Drivers - new installer

On 24.10.19 13:35, Sandro Bonazzola wrote: > Please give it a run on your testing environment / testing VMs and let > us know about your experience at de...@ovirt.org . Works great in Windows 10 on GNOME Boxes (Fedora 30)! Until now I wasn't able to get automatic display re

Re: Modularity and all the things

On Thu, 2019-10-24 at 08:09 -0400, Stephen Gallagher wrote: > There's a very large difference between feedback like "I think the > user experience is suboptimal here, for this reason" and "I don't > like the entire design, you should scrap it and start over". > > In the first case, it's possible t

No NeuroFedora meeting today (Was: Re: New meeting time: whenisgood)

Hello! We won't have a meeting today. If you've not filled the whenisgood yet, please do so. We will continue meetings next week at the new time. http://whenisgood.net/ips5zm2 I will close the whenisgood at 2359 UTC later today (in about 9 hours) so that I can announce the new time tomorrow. Ple

[Test-Announce] Fedora 31 Final is GO

The Fedora 31 Final RC1.9 compose [1] is GO and will be shipped live on Tuesday, 29 October 2019. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. Thank you to everyone who has worked on this release and getting it out on time. [1] https://dl.fedoraproject.org/pub/

Re: Fedora 31 Final is GO

On Thu, Oct 24, 2019 at 11:40:22AM -0400, Ben Cotton wrote: > For more information please check the Go/No-Go meeting minutes [2] or logs > [3]. > Thank you to everyone who has worked on this release and getting it out on > time. Yes! Special thinks to everyone who worked extra hard to make sure

[Test-Announce] Fedora 31 testing required: F29 and F30 libdnf / gnome-software updates

Hi folks! While F31 is signed off, there's still some testing required. There are two updates, one each for F29 and F30, which must be pushed stable before the release date: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2fb39de3ce (F29) https://bodhi.fedoraproject.org/updates/FEDORA-2019-236

review swap for wdune (white_dune)

Hi, Cause the last review is too old, i need a fresh review for wdune (white_dune): https://bugzilla.redhat.com/show_bug.cgi?id=1658153 This package requires vcglib: https://bugzilla.redhat.com/show_bug.cgi?id=1677989 I'm available for any review in exchange. so long MUFTI ___

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

On 08. 10. 19 14:26, Miro Hrončok wrote: On 08. 10. 19 14:04, Miro Hrončok wrote: On 08. 10. 19 13:53, Peter Robinson wrote: 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 no

Fedora-31-20191024.n.2 compose check report

No missing expected images. Failed openQA tests: 3/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-31-20191024.n.0): ID: 476418 Test: x86_64 KDE-live-iso base_update_cli URL: https://openqa.fedoraproject.org/tests/476418 ID: 476497 Test: x86_64 universal

Fedora 31 compose report: 20191024.n.2 changes

OLD: Fedora-31-20191024.n.0 NEW: Fedora-31-20191024.n.2 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 6 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

Re: [ovirt-users] [feedback needed] VirtIO Windows Drivers - new installer

Il giorno gio 24 ott 2019 alle ore 19:28 Strahil ha scritto: > Hi Sandro,All, > > Can I upgrade the tools on existing VM , or it requires a fresh one? Best > Regards > If you have oVirt windows guest tools already installed suggestion is to uninstall it before installing this new installer. >