Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread David Tardon
Hello, On Sat, 2018-11-17 at 08:10 +, Leigh Scott wrote: > > On Tue, Nov 13, 2018 at 5:36 PM, Matthew Miller > > > > > "Canonical Extends Ubuntu 18.04 LTS Linux Support to 10 Years" > > > > https://www.serverwatch.com/server-news/canonical-extends-ubuntu-18.04-lt... > > > > I just don't s

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Leigh Scott
I'm hoping the Fedora LTS idea will die as quickly as it started. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.htm

Re: Automating package maintainers responsivity check

2018-11-18 Thread Mattia Verga
Il 11/17/18 10:59 PM, Philip Kovacs ha scritto: > You want to attract packagers, not irritate them. In my opinion, "irritating" is when a maintainer doesn't reply to bugs that users fill in Bugzilla. If they can't found enough time to reply or change state of any bug in a six months period, t

Re: Automating package maintainers responsivity check

2018-11-18 Thread Richard Shaw
On Sat, Nov 17, 2018 at 11:47 AM Mattia Verga wrote: > > > - after three emails without response, orphan their packages and inform > devel list > I'm not sure I'm in favor of automatically orphaning packages. I think it could "tell" of them to the devel list that way anyone who knows them can tr

How to get a list of C-only packages to review ?

2018-11-18 Thread Alain Vigne
As a new packager, I understand peer-reviewing packages is very important, but it takes me (a lot of) time, and I do not have the necessary skills to review any kind of packages (Go, Python, Rust, Java, Javascript, Ruby, ... you name it) That is why I can offer to review packages of C libs, apps,

Re: How to get a list of C-only packages to review ?

2018-11-18 Thread Rex Dieter
Alain Vigne wrote: > As a new packager, I understand peer-reviewing packages is very important, > but it takes me (a lot of) time, and I do not have the necessary skills to > review any kind of packages (Go, Python, Rust, Java, Javascript, Ruby, ... > you name it) > > That is why I can offer to r

Re: Proposal: Faster composes by eliminating deltarpms and using zchunked rpms instead

2018-11-18 Thread Jonathan Dieter
On Sat, 2018-11-17 at 22:30 +0100, Kevin Kofler wrote: > Jonathan Dieter wrote: > > My proposal would be to make zchunk the rpm compression format for > > Fedora. > > Given that: > 1. zchunk is based on zstd, which is typically less efficient in terms of >compression ratio than xz, depending o

Re: How to get a list of C-only packages to review ?

2018-11-18 Thread Alain Vigne
Agree, once the .spec file is opened, it is obvious. But the list such as : https://fedoraproject.org/PackageReviewStatus/NEW.html doesn't give you easy access to the info: you have to open the BZ, then look for the file (if you are lucky). Worst case is when .spec file needs to be extracted (take

Re: Proposal: Faster composes by eliminating deltarpms and using zchunked rpms instead

2018-11-18 Thread Neal Gompa
On Sun, Nov 18, 2018 at 11:54 AM Jonathan Dieter wrote: > > On Sat, 2018-11-17 at 22:30 +0100, Kevin Kofler wrote: > > Jonathan Dieter wrote: > > > My proposal would be to make zchunk the rpm compression format for > > > Fedora. > > > > Given that: > > 1. zchunk is based on zstd, which is typicall

Re: How to get a list of C-only packages to review ?

2018-11-18 Thread Fabio Valentini
On Sun, Nov 18, 2018, 18:15 Alain Vigne Agree, once the .spec file is opened, it is obvious. > > But the list such as : > https://fedoraproject.org/PackageReviewStatus/NEW.html > doesn't give you easy access to the info: you have to open the BZ, then > look for the file (if you are lucky). Worst c

Re: Proposal: Faster composes by eliminating deltarpms and using zchunked rpms instead

2018-11-18 Thread Stephen John Smoogen
On Sun, 18 Nov 2018 at 12:49, Neal Gompa wrote: > > On Sun, Nov 18, 2018 at 11:54 AM Jonathan Dieter wrote: > > > > On Sat, 2018-11-17 at 22:30 +0100, Kevin Kofler wrote: > > > Jonathan Dieter wrote: > > > > My proposal would be to make zchunk the rpm compression format for > > > > Fedora. > > >

Re: How do I "release" a spin/lab?

2018-11-18 Thread Kevin Fenzi
On 11/16/18 10:22 AM, Miro Hrončok wrote: > When Fedora 29 was released, the Python Classroom Lab wasn't built. > > The problem is now fixed: > > https://koji.fedoraproject.org/koji/packageinfo?packageID=23847 > > However how do i build and release it, so it is listed on: > > https://labs.fedor

Re: Automating package maintainers responsivity check

2018-11-18 Thread Kevin Fenzi
On 11/18/18 1:44 AM, Mattia Verga wrote: > Il 11/17/18 10:59 PM, Philip Kovacs ha scritto: > >> You want to attract packagers, not irritate them. > > In my opinion, "irritating" is when a maintainer doesn't reply to bugs that > users fill in Bugzilla. If they can't found enough time to reply o

Re: Automating package maintainers responsivity check

2018-11-18 Thread Philip Kovacs
> Being a volunteer doesn't mean to not have any responsibility. It's grossly unfair to insinuate that being a volunteer is associated with laziness or a lack of responsibility. There are a myriad of things that we as packagers do that are completely silent to the surrounding automation and for

Re: How do I "release" a spin/lab?

2018-11-18 Thread Miro Hrončok
On 18. 11. 18 19:37, Kevin Fenzi wrote: On 11/16/18 10:22 AM, Miro Hrončok wrote: When Fedora 29 was released, the Python Classroom Lab wasn't built. The problem is now fixed: https://koji.fedoraproject.org/koji/packageinfo?packageID=23847 However how do i build and release it, so it is liste

Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Frantisek Zatloukal
We have encountered a bug[0] which seemingly “broke” offline updates after systems were upgraded from an older Fedora to Fedora 29 and had some multilib packages installed. After the discussion at last week's Release Retrospective meeting, I am proposing some changes to our blocking criterions in o

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Richard W.M. Jones
I'm not for or against a longer Fedora lifecycle, but I think we need a stronger statement of what the problem is we're trying to address. From your email: On Tue, Nov 13, 2018 at 06:36:38PM -0500, Matthew Miller wrote: > But there are some good cases for a longer lifecycle. For one thing, > this

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Orion Poplawski
On 11/18/18 2:29 PM, Richard W.M. Jones wrote: I'm not for or against a longer Fedora lifecycle, but I think we need a stronger statement of what the problem is we're trying to address. From your email: On Tue, Nov 13, 2018 at 06:36:38PM -0500, Matthew Miller wrote: But there are some good ca

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Tony Nelson
On 18-11-18 16:29:45, Richard W.M. Jones wrote: I'm not for or against a longer Fedora lifecycle, but I think we need a stronger statement of what the problem is we're trying to address. From your email: On Tue, Nov 13, 2018 at 06:36:38PM -0500, Matthew Miller wrote: > But there are some good c

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Neal Gompa
On Sun, Nov 18, 2018 at 5:08 PM Orion Poplawski wrote: > > On 11/18/18 2:29 PM, Richard W.M. Jones wrote: > > I'm not for or against a longer Fedora lifecycle, but I think we need > > a stronger statement of what the problem is we're trying to address. > > > > From your email: > > > > On Tue, Nov

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Neal Gompa
On Sun, Nov 18, 2018 at 5:30 PM Reindl Harald wrote: > > Am 18.11.18 um 23:19 schrieb Neal Gompa: > > I think it's quite obvious why. No one can really influence what's in > > CentOS. Red Hat Enterprise Linux itself is developed mostly behind > > closed doors, after forking a Fedora release. > > t

Re: Fedora Lifecycles: imagine longer-term possibilities

2018-11-18 Thread Gerald Henriksen
On Sun, 18 Nov 2018 17:19:37 -0500, you wrote: >But I don't think we should extend the lifecycle on a general basis. >That's asking for trouble, since it cedes our leadership in the Linux >platform and destroys our ability to meet our own values. What leadership would Fedora be ceding by extendin

Re: Fedora Server 29: when stop and start my qemu/kvm server, some service they do not start

2018-11-18 Thread Dario Lesca
Il giorno ven, 16/11/2018 alle 18.26 +0100, Dario Lesca ha scritto: > I have fill this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1650289 in which there > are some useful logs files > > If someone have some suggest to resolve this issue without modify the > .service file of this service l

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Adam Williamson
On Sun, 2018-11-18 at 21:48 +0100, Frantisek Zatloukal wrote: > We have encountered a bug[0] which seemingly “broke” offline updates after > systems were upgraded from an older Fedora to Fedora 29 and had some > multilib packages installed. After the discussion at last week's Release > Retrospectiv

Re: NSS package consolidation

2018-11-18 Thread Robert-André Mauchin
On lundi 12 novembre 2018 18:10:47 CET Daiki Ueno wrote: > Tom Hughes writes: > > > > If it's going to one source rpm producing the same three binary > > rpms then you are indeed correct. > > > Thank you for the suggestions. Then I will go ahead and retire nss-util > and nss-softokn source pa

Re: How to get a list of C-only packages to review ?

2018-11-18 Thread Rex Dieter
Alain Vigne wrote: > Agree, once the .spec file is opened, it is obvious. > > But the list such as : > https://fedoraproject.org/PackageReviewStatus/NEW.html > doesn't give you easy access to the info: you have to open the BZ, then > look for the file (if you are lucky). Worst case is when .spec

[EPEL-devel] Fedora EPEL 7 updates-testing report

2018-11-18 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 162 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3835d39d1a unrtf-0.21.9-8.el7 113 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7 pandoc-c

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Kevin Kofler
Frantisek Zatloukal wrote: >Install Fedora n-1 >Upgrade to Fedora n (updates-testing disabled) >Enable updates-testing >Update to latest packages >Verify that upgrade and update went fine and that the multilib packages >installed before are still present If you follow exact

Re: Fedora Upgrade - release criteria update proposal

2018-11-18 Thread Frantisek Zatloukal
On Mon, Nov 19, 2018 at 6:43 AM Kevin Kofler wrote: > If you follow exactly this procedure, the set of "the multilib packages > installed before" will be empty and you will not reproduce the issue at > hand. Multilib cruft has not been installed by default for years now! (And > that is a good thi

Fedora rawhide compose report: 20181118.n.0 changes

2018-11-18 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20181117.n.0 NEW: Fedora-Rawhide-20181118.n.0 = SUMMARY = Added images:4 Dropped images: 0 Added packages: 5 Dropped packages:0 Upgraded packages: 66 Downgraded packages: 0 Size of added packages: 1.67 MiB Size of dropped packages:0 B

[Bug 1612860] perl-Net-Pcap-0.18-9.fc29 FTBFS: stubs.inc:357:8: error: redefinition of 'struct pcap_rmtauth'

2018-11-18 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1612860 Petr Pisar changed: What|Removed |Added External Bug ID||CPAN 127685 Version|29