Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Wed, Jan 29, 2020 at 11:04:19PM +0100, Miro Hrončok wrote: > On 29. 01. 20 22:49, Richard W.M. Jones wrote: > >On Wed, Jan 29, 2020 at 10:26:56PM +0100, Miro Hrončok wrote: > >>Here is an initial (albeit randomly generated) proposal of X and Y: > >> > >>severity CRITICAL/HIGH MEDIUM L

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Thank you for looking into this matter. Dne 29. 01. 20 v 22:26 Miro Hrončok napsal(a): > Hello, Fedora has an approved security policy since September 2018 [0]: > >> If a CRITICAL or IMPORTANT security issue is currently open >> against a package, or a security issue of lower severity has been >>

Re: review swap , nodejs packages need some updates

Dne 30. 01. 20 v 5:10 Sérgio Basto napsal(a): > Hi, > > I took js-jquery-file-upload package to save js-query Great and thx. If you want by a chance to maintain also js-jquery{,1,2}, I would not mind to have co-maintainers or even better to hand it over to somebody O:-) Vít > , I updated

Fedora pagure confusion wrt EPEL

I don't do EPEL packaging. I never signed up as an "owner" of EPEL packages. I don't want to be the new default owner of EPEL bugzilla tickets. Where may I be able to stop this mess? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

Re: Fedora pagure confusion wrt EPEL

No way. You can add comaintainer for EPEL builds of your packages. чт, 30 янв. 2020 г. в 12:13, Michael Schwendt : > > I don't do EPEL packaging. I never signed up as an "owner" of EPEL packages. > I don't want to be the new default owner of EPEL bugzilla tickets. > Where may I be able to stop thi

Re: Git Forge Requirements: Please see the Community Blog

Dne 29. 01. 20 v 17:37 Clement Verna napsal(a): > > > On Wed, 29 Jan 2020 at 16:18, Pierre-Yves Chibon > wrote: > > On Wed, Jan 29, 2020 at 03:56:08PM +0100, Clement Verna wrote: > >    On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > >    mailto:jla...@f

Re: Fedora pagure confusion wrt EPEL

On Thu, 30 Jan 2020 12:23:01 +0300, Vascom wrote: > No way. > You can add comaintainer for EPEL builds of your packages. That can't be right. Who has made me the "owner" of claws-mail in EPEL? And why? https://fedoraproject.org/wiki/EPEL/FAQ#I_maintain_a_package_in_Fedora._Do_I_have_to_maintain

Re: Fedora pagure confusion wrt EPEL

On Thu, Jan 30, 2020, 10:13 Michael Schwendt wrote: > I don't do EPEL packaging. I never signed up as an "owner" of EPEL > packages. > I don't want to be the new default owner of EPEL bugzilla tickets. > Where may I be able to stop this mess? > Until this functionality is merged into pagure's di

Re: Git Forge Requirements: Please see the Community Blog

Dne 29. 01. 20 v 23:22 Pierre-Yves Chibon napsal(a): > On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote: >> Julen Landa Alustiza writes: >> >>> (snip) >>> >>> 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: To me that's the all point of this process, let's put dow

Fedora notifications bug: 404 Not Found

No idea where to report these: | Notification time stamped 2020-01-30 09:55:53 UTC | | mschwendt pushed 1 commit to rpms/claws-mail (el6) | https://src.fedoraproject.org/rpms/claws-mail/branch/el6 Not Found The requested URL was not found on the server. If you entered the URL manually p

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Thu, Jan 30, 2020 at 10:05:28AM +0100, Vít Ondruch wrote: > Thank you for looking into this matter. > > > Dne 29. 01. 20 v 22:26 Miro Hrončok napsal(a): > > Hello, Fedora has an approved security policy since September 2018 [0]: > > > >> If a CRITICAL or IMPORTANT security issue is currently o

Re: Fedora notifications bug: 404 Not Found

On 30/01/2020 10:02, Michael Schwendt wrote: No idea where to report these: | Notification time stamped 2020-01-30 09:55:53 UTC | | mschwendt pushed 1 commit to rpms/claws-mail (el6) | https://src.fedoraproject.org/rpms/claws-mail/branch/el6 Not Found The requested URL was not found on

Re: Java Dev Group and Fedora Quality

On 1/29/20 3:15 PM, Alex Scheel wrote: > I lump the Java SE platform into "roughly" what I was calling the JVM > team. You're roughly the group that does what'd be the "core" work in > other languages: maintains the compilers and the stdlib. My terminology > there was incorrect; I suppose "JRE" is

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Dne 30. 01. 20 v 11:09 Zbigniew Jędrzejewski-Szmek napsal(a): > On Thu, Jan 30, 2020 at 10:05:28AM +0100, Vít Ondruch wrote: >> Thank you for looking into this matter. >> >> >> Dne 29. 01. 20 v 22:26 Miro Hrončok napsal(a): >>> Hello, Fedora has an approved security policy since September 2018 [0]

Orphaned ldapvi

If anybody wants it, let me know. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guide

New mingw-nsis package apparent breakage

Hello Sandro, mingw-nsis failed to build in the F32 mass rebuild, so I have updated the package to the latest version and fixed quite a few problems. It now builds, but there are some seemingly serious problems with the resulting package which make me reluctant to want to push anything to Rawhide

epel8: BuildrootError: could not init mock buildroot

Hello, when doing `fedpkg scratch-build --target epel8-candidate --srpm sox-14.4.2.0-29.el8.src.rpm`, I get: [] 100% 00:00:01 1.02 MiB 773.06 KiB/sec Building sox-14.4.2.0-29.el8.src.rpm for epel8-candidate Created task: 41245726 Task info: https://koji.fed

Re: Orphaned ldapvi

* Matěj Cepl [30/01/2020 11:43] : > > If anybody wants it, let me know. I will gladly take it (fas user: eseyman). Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedor

Re: Ideas for better development processes when maintaining hundreds of packages

On Wed, Jan 29, 2020 at 04:45:22PM +0200, Damian Ivanov wrote: > >That is looking for a boogeyman under the bed to blame something that > >has a long long history of not happening. Ever since OBS has been out, > >there has been a yearly 'why isn't Fedora moving to OBS' thread > > It has always bee

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Thu, Jan 30, 2020 at 08:39:05AM +0530, Huzaifa Sidhpurwala wrote: > Do we want to continue the same condition as described here: > https://mivehind.net/2020/01/28/Fedora-has-too-many-security-bugs/ Maybe? The problem with this analysis is we don't know how many of these are actual current secu

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Thu, Jan 30, 2020 at 08:40:57AM +0530, Huzaifa Sidhpurwala wrote: > On 1/30/20 3:19 AM, Richard W.M. Jones wrote: > > On Wed, Jan 29, 2020 at 10:26:56PM +0100, Miro Hrončok wrote: > >> Here is an initial (albeit randomly generated) proposal of X and Y: > >> > >> severity CRITICAL/HIGH MEDI

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 23:23, Leigh Griffin wrote: > > I suspect that a bulk of our users are similar to you. Given that you are > engaged on the thread (thank you!) what is your day to day needs? What > features are part of your usage and interaction? What's missing or what would > you like to

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On 1/30/20 4:11 PM, Vít Ondruch wrote: > > Dne 30. 01. 20 v 11:09 Zbigniew Jędrzejewski-Szmek napsal(a): >> On Thu, Jan 30, 2020 at 10:05:28AM +0100, Vít Ondruch wrote: >>> Thank you for looking into this matter. >>> >>> >>> Dne 29. 01. 20 v 22:26 Miro Hrončok napsal(a): Hello, Fedora has an

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Thu, Jan 30, 2020 at 11:20:48AM +, Richard W.M. Jones wrote: > On Thu, Jan 30, 2020 at 08:39:05AM +0530, Huzaifa Sidhpurwala wrote: > > Do we want to continue the same condition as described here: > > https://mivehind.net/2020/01/28/Fedora-has-too-many-security-bugs/ > > Maybe? > > The pro

Re: epel8: BuildrootError: could not init mock buildroot

On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > Hello, > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > sox-14.4.2.0-29.el8.src.rpm`, I get: > So there seems to be something off in koji and the repo is not getting properly regenerated after the repo gets updated. These

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 6:40 AM Iñaki Ucar wrote: > > On Wed, 29 Jan 2020 at 23:23, Leigh Griffin wrote: > > > > I suspect that a bulk of our users are similar to you. Given that you are > > engaged on the thread (thank you!) what is your day to day needs? What > > features are part of your usa

Re: Git Forge Requirements: Please see the Community Blog

20/1/29 18:19(e)an, Clement Verna igorleak idatzi zuen: > > Things that I would in my opinion improve Pagure PRs : > > * In the PR diff should start from the correct line number, not always > 1. (https://pagure.io/pagure/issue/724) > * Every time a branch is forced pushed you loose the comment

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Daniel P. Berrangé wrote: > Ignoring low bugs also probably isn't a viable stragegy > for EPEL, because that's a long life distro stream, and > so won't automatically get low CVE fixes via a rebase > in 6 months like we do in Fedora. So the CVE mountain > is even bigger for EPEL, and also more ser

Re: Ideas for better development processes when maintaining hundreds of packages

On Wed, Jan 29, 2020 at 2:11 PM Ken Dreyer wrote: > > On Wed, Jan 29, 2020 at 7:18 AM Remi Collet wrote: > > > There are different: > > > > * Changelog is for end user > > * Git log is for package maintainer > > I completely agree with this distinction. We're creating more "noise" > for end users

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Huzaifa Sidhpurwala wrote: > On 1/30/20 8:32 AM, Kevin Kofler wrote: >> I don't see how it is an improvement to close security fixes that are >> blocking on upstream (in)action as UPSTREAM, as opposed to keeping them >> open so that it is clear to everyone that they need to be fixed. >> > Issues w

Re: Fedora pagure confusion wrt EPEL

Fabio Valentini wrote: > Until this functionality is merged into pagure's dist-git plugin, there is > a way, but it's a bit convoluted. > > You can set an override for Fedora / EPEL default assignees in yaml files > stored here, like this one for maven: > > https://pagure.io/releng/fedora-scm-req

Re: Orphaned ldapvi

On 2020-01-30, 11:04 GMT, Emmanuel Seyman wrote: > I will gladly take it (fas user: eseyman). Unfortunately, it is gone already, so I cannot add you. https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package ___

Re: Fedora pagure confusion wrt EPEL

On Thu, Jan 30, 2020 at 2:46 PM Kevin Kofler wrote: > > Fabio Valentini wrote: > > Until this functionality is merged into pagure's dist-git plugin, there is > > a way, but it's a bit convoluted. > > > > You can set an override for Fedora / EPEL default assignees in yaml files > > stored here, lik

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

On 21. 01. 20 13:35, Miro Hrončok wrote: Hello, we try to rebuild all Python packages against Python 3.9 and report the failures. I've seen several similar failures in a row now that can be reproduced in Fedora rawhide with the new gcc version. ld errors on multiple definitions of ..., for e

mock log output has DOS line endings?

Am I the only one having this problem? I don't know exactly when it started but all of a sudden all of the log output has DOS line endings and it's very annoying. I have to run dox2unix on the logs to make them readable. Thanks, Richard ___ devel mailing

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

On Thu, Jan 30, 2020 at 02:28:30PM +0100, Kevin Kofler wrote: > Daniel P. Berrangé wrote: > > Ignoring low bugs also probably isn't a viable stragegy > > for EPEL, because that's a long life distro stream, and > > so won't automatically get low CVE fixes via a rebase > > in 6 months like we do in F

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Not replying to anyone in particular but to the thead as a whole... 1. Nothing in the packager introduction process prepares a packager for what to do when they get a CVE filed against one of their packages. I found the whole ordeal rather stressful. 2. The process is somewhat confusing with all

[Bug 1796332] perl-Sereal-Decoder-4.008 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1796332 --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2020-c55eecf045 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c55eecf045 -- You are receiving this mail because: You are on

Re: mock log output has DOS line endings?

On 1/30/20 9:19 AM, Richard Shaw wrote: Am I the only one having this problem? I don't know exactly when it started but all of a sudden all of the log output has DOS line endings and it's very annoying. I have to run dox2unix on the logs to make them readable. I am seeing that too, and you ar

Re: mock log output has DOS line endings?

On Thu, Jan 30, 2020 at 7:21 AM Richard Shaw wrote: > Am I the only one having this problem? I don't know exactly when it started > but all of a sudden all of the log output has DOS line endings and it's very > annoying. I have to run dox2unix on the logs to make them readable. It's even worse

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 10:40:05AM +0100, Vít Ondruch wrote: >Dne 29. 01. 20 v 23:22 Pierre-Yves Chibon napsal(a): > > On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote: > > Julen Landa Alustiza [1] writes: > > > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi

Re: Git Forge Requirements: Please see the Community Blog

On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > > > My point is that we have to dedicate a team to work on Pagure, I would > > rather have these people working on improving the infrastructure so > > that we don't need these heroics to happen. If we don't put people to > > work on Pagure it

Re: mock log output has DOS line endings?

On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote: > Am I the only one having this problem? I don't know exactly when it > started but all of a sudden all of the log output has DOS line > endings and it's very annoying. I have to run dox2unix on the logs to > make them readable. I have the sam

Re: review swap , nodejs packages need some updates

On Thu, 2020-01-30 at 10:09 +0100, Vít Ondruch wrote: > Dne 30. 01. 20 v 5:10 Sérgio Basto napsal(a): > > Hi, > > > > I took js-jquery-file-upload package to save js-query > > Great and thx. If you want by a chance to maintain also js- > jquery{,1,2}, > I would not mind to have co-maintainers o

Re: review swap , nodejs packages need some updates

On 30/01/2020 18:22, Sérgio Basto wrote: On Thu, 2020-01-30 at 10:09 +0100, Vít Ondruch wrote: Dne 30. 01. 20 v 5:10 Sérgio Basto napsal(a): Hi, I took js-jquery-file-upload package to save js-query Great and thx. If you want by a chance to maintain also js- jquery{,1,2}, I would not mind t

Re: review swap , nodejs packages need some updates

On Thu, 2020-01-30 at 18:42 +, Tom Hughes wrote: > On 30/01/2020 18:22, Sérgio Basto wrote: > > On Thu, 2020-01-30 at 10:09 +0100, Vít Ondruch wrote: > > > Dne 30. 01. 20 v 5:10 Sérgio Basto napsal(a): > > > > Hi, > > > > > > > > I took js-jquery-file-upload package to save js-query > > > >

Re: review swap , nodejs packages need some updates

On 30/01/2020 18:53, Sérgio Basto wrote: Hi Tom , IIRC you can add me nodejs-multimatch , please my fasuser: sergiomb If you wan to maintain nodejs stuff then the best thing to do is to join the SIG rather than asking for ACLs on individual packages. If you're planning to update multimatch th

Re: review swap , nodejs packages need some updates

On Thu, 2020-01-30 at 18:57 +, Tom Hughes wrote: > On 30/01/2020 18:53, Sérgio Basto wrote: > > > Hi Tom , IIRC you can add me nodejs-multimatch , please > > my fasuser: sergiomb > > If you wan to maintain nodejs stuff then the best thing to do is to > join the SIG rather than asking for ACLs

Re: Orphaned ldapvi

* Matěj Cepl [30/01/2020 14:54] : > > https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package Done! Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email

Re: Fedora pagure confusion wrt EPEL

On Thu, 30 Jan 2020 14:44:50 +0100, Kevin Kofler wrote: > Fabio Valentini wrote: > > Until this functionality is merged into pagure's dist-git plugin, there is > > a way, but it's a bit convoluted. And it's too obscure. Instead, I just retired the two EPEL branches. > And we have to do that for

Re: Fedora pagure confusion wrt EPEL

On Thu, Jan 30, 2020 at 11:26 PM Michael Schwendt wrote: > > On Thu, 30 Jan 2020 14:44:50 +0100, Kevin Kofler wrote: > > > Fabio Valentini wrote: > > > Until this functionality is merged into pagure's dist-git plugin, there is > > > a way, but it's a bit convoluted. > > And it's too obscure. Inste

Re: RFC: Security policy adjustments to make it easier to implement and more friendly to maintainers

Richard Shaw writes: > Not replying to anyone in particular but to the thead as a whole... > > 1. Nothing in the packager introduction process prepares a packager > for what to do when they get a CVE filed against one of their > packages. I found the whole ordeal rather stressful. Agreed, this w

Re: Fedora pagure confusion wrt EPEL

On 31/1/20 08:57, Fabio Valentini wrote: >> With pkgdb I could see who maintains which "branches" and which branches >> exist. With this new web UI, I don't find where I could take a look at >> who maintains which branch. For some packages I see socalled "members", a >> "main admin", an "admin", pe

Re: Fedora pagure confusion wrt EPEL

On Thu, 30 Jan 2020 23:57:03 +0100, Fabio Valentini wrote: > Did you at least check if the packages were used by something else? ... No, and that doesn't interest me at all. I am not doing EPEL packaging, and I consider it inacceptable that somebody assigns five years old EPEL tickets to me and e

Re: Git Forge Requirements: Please see the Community Blog

On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > cough cough errata cough cough > > Honestly, sometimes the disconnect between what is going on in Fedora > and internally in Red Hat is intriguing. I did think about Errata tool* a bit back when I worked on Bodhi. I like the idea of sharing

Re: Fedora pagure confusion wrt EPEL

On Fri, Jan 31, 2020, 00:43 Michael Schwendt wrote: > On Thu, 30 Jan 2020 23:57:03 +0100, Fabio Valentini wrote: > > > Did you at least check if the packages were used by something else? ... > > No, and that doesn't interest me at all. I am not doing EPEL packaging, > and I consider it inacceptab

Fedora-Cloud-30-20200129.0 compose check report

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 devel-le...@lists.fedorap

Fedora-Cloud-31-20200129.0 compose check report

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 devel-le...@lists.fedorap

Re: Ideas for better development processes when maintaining hundreds of packages

* Remi Collet [29/01/2020 15:18] : > > And I really prefer to see stabilization of our current tools and > infrastructure before breaking it again. Same here, to be honest. I'm far more held up in my work by the infrastructure breaking up from under me than the absence of any of the suggestions fr

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow wrote: > > On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > > cough cough errata cough cough > > > > Honestly, sometimes the disconnect between what is going on in Fedora > > and internally in Red Hat is intriguing. > > I did think about Errata t

Fedora-Cloud-30-20200130.0 compose check report

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 devel-le...@lists.fedorap

Fedora-Cloud-31-20200130.0 compose check report

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 devel-le...@lists.fedorap

Re: Copr Build System - review of 2019 and vote for features in 2020

On Thu, Jan 23, 2020 at 11:07:21AM -0700, John M. Harris Jr wrote: > > EOL is not, literally, EOL. EOL just means the complete end of support, in > commercial products. Still doesn't mean systems with that version installed > cease to exist. In Fedora, it simply means that it gets little attenti

Re: Fedora notifications bug: 404 Not Found

On Thu, Jan 30, 2020 at 10:21:14AM +, Tom Hughes wrote: > On 30/01/2020 10:02, Michael Schwendt wrote: > > No idea where to report these: > > > > > > | Notification time stamped 2020-01-30 09:55:53 UTC > > | > > | mschwendt pushed 1 commit to rpms/claws-mail (el6) > > | https://src.fedorapr

Re: epel8: BuildrootError: could not init mock buildroot

On Thu, Jan 30, 2020 at 07:57:22AM -0500, Stephen John Smoogen wrote: > On Thu, 30 Jan 2020 at 06:06, Jiri Kucera wrote: > > > > Hello, > > > > when doing `fedpkg scratch-build --target epel8-candidate --srpm > > sox-14.4.2.0-29.el8.src.rpm`, I get: > > > > So there seems to be something off in

Re: mock log output has DOS line endings?

On Thu, Jan 30, 2020 at 06:02:33PM +, Sérgio Basto wrote: > On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote: > > Am I the only one having this problem? I don't know exactly when it > > started but all of a sudden all of the log output has DOS line > > endings and it's very annoying. I hav

Re: mock log output has DOS line endings?

On Thu, Jan 30, 2020 at 7:51 PM Kevin Fenzi wrote: > On Thu, Jan 30, 2020 at 06:02:33PM +, Sérgio Basto wrote: > > On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote: > > > Am I the only one having this problem? I don't know exactly when it > > > started but all of a sudden all of the log

Re: Ideas for better development processes when maintaining hundreds of packages

On Tue, Jan 28, 2020 at 12:36:23PM +0100, Pierre-Yves Chibon wrote: > > There are a few tricky things about this, but overall I think it's doable and > some of the tricky things may just be things we just have to accept as being > different from the current situation. > > We are playing a bit of

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 11:01:59PM +0100, Felix Schwarz wrote: > > Am 21.01.20 um 22:31 schrieb Michael Catanzaro: > > Well since we have a request for requirements: I propose requirements #1 and > > #2 are to be self-hosted and open source. > > +1 I am with you on open source, but I don't under

Mass rebuild reminders

Just a few reminders for folks: * If your package failed to build in the mass rebuild ( https://kojipkgs.fedoraproject.org/mass-rebuild/f32-failures.html ) and you want to fix it, please do so. Just do a normal commit/build cycle for rawhide as you normally would. It should disappear from the ab

Re: Ideas for better development processes when maintaining hundreds of packages

On Tue, 28 Jan 2020 at 04:04, Richard W.M. Jones wrote: > * kill the %changelog > > Please, let's kill it, and generate it from the git changelog. > I'm glad to see there's a proposal to do this. > As again... Very strong no. git changelog and spec changelog have different purposes. For some case

Re: mock log output has DOS line endings?

On Friday, January 31, 2020 2:44:21 AM CET Kevin Fenzi wrote: > On Thu, Jan 30, 2020 at 06:02:33PM +, Sérgio Basto wrote: > > On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote: > > > Am I the only one having this problem? I don't know exactly when it > > > started but all of a sudden all of

Packages webapp status

On Thu, 30 Jan 2020 at 08:03, Neal Gompa wrote: > > On Thu, Jan 30, 2020 at 6:40 AM Iñaki Ucar wrote: > > > > On Wed, 29 Jan 2020 at 23:23, Leigh Griffin wrote: > > > > > > I suspect that a bulk of our users are similar to you. Given that you are > > > engaged on the thread (thank you!) what is

Fedora-Cloud-30-20200131.0 compose check report

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 devel-le...@lists.fedorap

How to package a web service (nginx vs httpd)

Hello, I am working on packaging [netbox](https://github.com/netbox-community/netbox/) which is basically web service which is run via gunicorn and then it is up to admin to decide whether he wants to use nginx, httpd or anything else. Do we have somewhere written best practices how to package su