Hi, my name is Dan Shoemaker. I have been using Fedora since Fedora Core 6
for both personal and professional use. About five years ago I started
developing bash scripts in order to start automating tasks I was doing
while maintaining Linux servers for various clients. Last year I started
Le mercredi 26 février 2020 à 23:07 -0500, Neal Gompa a écrit :
>
> You don't use Release for upstream versioning, even for snapshots.
> For
> your examples:
>
> * 0-0.1.beta.2 -> 0~beta.2-1
> * 0-0.1.20120225gitd6c789a -> 0~git20120225.d6c789a-
Sorry but no
You are attempting to redefine the
Hi list,
Stephen John Smoogen writes:
> On Mon, 24 Feb 2020 at 11:50, Pierre-Yves Chibon
> wrote:
>
>> Good Morning Everyone,
>>
>> This topic has already been discussed a few times over the past month, but
>> Adam
>> Saleh, Nils Philippsen and myself have had the opportunity to invest some
>>
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
For a while now we have generated rpm cmake provides automatically for
packages that install cmake "packages". The was done in a
case-sensitive manner using the name of the cmake files installed.
However, cmake looks for packages in a case-insensitive manner so
distributions that have also
https://fedorapeople.org/groups/389ds/ci/nightly/2020/02/27/report-389-ds-base-1.4.3.3-20200227gitea4fa54.fc31.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Wed, Feb 26, 2020 at 8:05 PM Robert-André Mauchin wrote:
>
> On Monday, 24 February 2020 17:48:36 CET Pierre-Yves Chibon wrote:
> > However, for the release field, we are struggling a little bit more, two
> > options are more appealing to us:
> >
> > A) The release field is automatically
On Monday, 24 February 2020 17:48:36 CET Pierre-Yves Chibon wrote:
> However, for the release field, we are struggling a little bit more, two
> options are more appealing to us:
>
> A) The release field is automatically generated using two elements:
> - the number of commits at this version
>
The following Fedora EPEL 6 Security updates need testing:
Age URL
13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dd6b868b6d
pam_radius-1.4.0-4.el6
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-91512b5eee
proftpd-1.3.3g-14.el6
The following builds have
The following Fedora EPEL 7 Security updates need testing:
Age URL
561 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d
condor-8.6.11-1.el7
302 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80
python-gnupg-0.4.4-1.el7
300
On Wed, 26 Feb 2020 at 15:58, Kevin Fenzi wrote:
> On Wed, Feb 26, 2020 at 08:26:09AM +0100, Clement Verna wrote:
> > Hi all,
> >
> > FMN (https://apps.fedoraproject.org/notifications) is currently one of
> the
> > main blocking point for dropping fedmsg in favour of fedora-messaging.
> > FMN is
On 2/24/20 5:57 PM, Daniel Pocock wrote:
On 24/02/2020 20:47, Dakota Williams wrote:
Does anyone know how to contact maintainer pocock?
https://bugzilla.redhat.com/show_bug.cgi?id=1806708
https://bugzilla.redhat.com/show_bug.cgi?id=1790674
Like most developers, I have a backlog of things
On Mon, Feb 24, 2020 at 06:13:21PM +0100, Miro Hrončok wrote:
> On 24. 02. 20 17:48, Pierre-Yves Chibon wrote:
> >However, for the release field, we are struggling a little bit more, two
> >options
> >are more appealing to us:
>
> Can we please have a "git is the only source of truth" version of
On Wed, Feb 26, 2020 at 02:45:24PM +, Jeremy Cline wrote:
>
> FYI before I left the team I started hacking up a replacement[0]. My
> design focused on how to get as rich a feature set as I could using
> only AMQPs currently available filtering features. There's a couple
> feature differences
On Wed, Feb 26, 2020 at 08:26:09AM +0100, Clement Verna wrote:
> Hi all,
>
> FMN (https://apps.fedoraproject.org/notifications) is currently one of the
> main blocking point for dropping fedmsg in favour of fedora-messaging.
> FMN is quite important to the community and the composition of Fedora
On 26. 02. 20 19:38, Ben Cotton wrote:
Components can be marked inactive in Bugzilla, which I believe will prevent
users from filing new bugs without losing any historical data.
Correct. We have done this with the "python" component.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Components can be marked inactive in Bugzilla, which I believe will prevent
users from filing new bugs without losing any historical data. Perhaps this
should be part of the retirement process?
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
On Wed, 2020-02-26 at 13:04 -0500, Robbie Harwood wrote:
>
> Would be nice if there were an API that would let us listen to it
> without needing to write an IRC bot or loop polling an HTTP endpoint.
> It sounds like this is similar to what Jeremy was proposing, but I'm not
> sufficiently versed
https://pagure.io/389-ds-base/pull-request/50916
--
389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Clement Verna writes:
> Fabio Valentini wrote:
>> Clement Verna wrote:
>>
>>> Hi all,
>>>
>>> FMN (https://apps.fedoraproject.org/notifications) is currently one
>>> of the main blocking point for dropping fedmsg in favour of
>>> fedora-messaging. FMN is quite important to the community and
https://bugzilla.redhat.com/show_bug.cgi?id=1806215
--- Comment #7 from Fedora Update System ---
perl-experimental-0.021-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See
https://bugzilla.redhat.com/show_bug.cgi?id=1805790
--- Comment #5 from Fedora Update System ---
perl-Alien-pkgconf-0.16-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See
I think we could just tell the user that a component is retired by changing
the component name to name(retired) or maybe some other means .
The gist is to tell the user that the component is retired and is probably
not the one that is causing the bug and maybe point to other components
which might
No missing expected images.
Failed openQA tests: 3/35 (x86_64)
ID: 528383 Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/528383
ID: 528409 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL:
OLD: Fedora-Rawhide-20200225.n.0
NEW: Fedora-Rawhide-20200226.n.0
= SUMMARY =
Added images:2
Dropped images: 2
Added packages: 9
Dropped packages:3
Upgraded packages: 163
Downgraded packages: 0
Size of added packages: 1.23 GiB
Size of dropped packages
Missing expected images:
Iot dvd aarch64
Iot dvd x86_64
Failed openQA tests: 1/8 (x86_64)
New failures (same test not failed in Fedora-IoT-32-20200224.0):
ID: 528416 Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/528416
Soft failed
No missing expected images.
Failed openQA tests: 26/171 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-32-20200225.n.0):
ID: 527934 Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/527934
ID: 527937 Test: x86_64
On Wed, 26 Feb 2020 at 11:13, Nicolas Kovacs wrote:
> Le 26/02/2020 à 15:48, Stephen John Smoogen a écrit :
> > I would open a bug on this so that the maintainer knows about it. They
> may not
> > be on this list or may filter it to the 'read once a year' bucket.
> Second, I
> > would check to
I today tried to mimic something that random Fedora user can do, and I
submitted bug against one of our long-time retired components. I haven't
been warned at all that the package is dead.
As user, it is easy to pick a wrong component when filling a bug - but the
problem with orphaned/retired
Le 26/02/2020 à 15:48, Stephen John Smoogen a écrit :
I would open a bug on this so that the maintainer knows about it. They may not
be on this list or may filter it to the 'read once a year' bucket. Second, I
would check to see what the audit2allow policy came up with and if the files it
is
On Wed, 2020-02-26 at 11:29 +0100, Nicolas Mailhot via devel wrote:
> Le 2020-02-26 11:14, Nils Philippsen a écrit :
>
> > Well, if we officially were to break with the upgrade path
> > constraints,
> > we'd have to document this. While we're at it, we should then
> > document
> > that Rawhide
On Mon, 24 Feb 2020 at 11:50, Pierre-Yves Chibon
wrote:
> Good Morning Everyone,
>
> This topic has already been discussed a few times over the past month, but
> Adam
> Saleh, Nils Philippsen and myself have had the opportunity to invest some
> time
> on it with the hope of making the packager's
[This is mainly a note-to-self so I know what the problems
are next time]
On Mon, Feb 24, 2020 at 01:53:37PM -0700, Jerry James wrote:
> I may have caused you a problem with the ocaml-ounit update I
> requested. Now we have ocaml-ounit requiring ocaml-dune to build, and
> ocaml-dune requiring
mschorm commented on the pull-request: `Use the correct name of the required
package` that you are following:
``
Hello,
I'm the mainatiner of 'mariadb' and 'community-mysql', which both provides this
"mysql-compat*" names.
I'm trying to clean up ancient artifact and get rid of them.
Your
mschorm opened a new pull-request against the project: `perl-Test-mysqld` that
you are following:
``
Use the correct name of the required package
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test-mysqld/pull-request/1
___
https://bugzilla.redhat.com/show_bug.cgi?id=1807554
Bug ID: 1807554
Summary: perl-MooX-Struct-0.020 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-MooX-Struct
Keywords: FutureFeature, Triaged
Dne 26. 02. 20 v 12:16 clime napsal(a):
> Few more notes:
> - having just: Release: means every commit bumps
> release and hence every commit should likely generate a new record
> into changelog => changelog basically becomes dumped `git log` (in
> rpm-compatible format) - i.e. there is no
On Wed, Feb 26, 2020 at 5:10 PM Fabio Valentini
wrote:
> Hi all,
>
> I've just orphaned a few Java packages on behalf of the Stewardship
> SIG since we no longer have any use for them.
>
> - aalto-xml
> - compress-lzf
> - icu4j
>
^^ Mat, should we take it or keep a huge patch removing the need
Dne 25. 02. 20 v 15:03 Pierre-Yves Chibon napsal(a):
> On Tue, Feb 25, 2020 at 12:59:39PM +0100, Vít Ondruch wrote:
>
> [About the release field]
>
>> I am not really sure about this. How do you envision this is going to be
>> implemented? Is there going to be "release" file, similarly to
>>
Hi all,
I've just orphaned a few Java packages on behalf of the Stewardship
SIG since we no longer have any use for them.
- aalto-xml
- compress-lzf
- icu4j
- jboss-marshalling
- jetty-alpn-api
- lz4-java
- lzma-java
- os-maven-plugin
Fabio
___
devel
OLD: Fedora-32-20200225.n.0
NEW: Fedora-32-20200226.n.0
= SUMMARY =
Added images:1
Dropped images: 1
Added packages: 0
Dropped packages:0
Upgraded packages: 57
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size
On Wed, 26 Feb 2020 at 07:06, Nicolas Kovacs wrote:
> Hi,
>
> I have an Internet-facing server running CentOS 7. I just installed
> Fail2ban
> using the following packages:
>
>* fail2ban-server
>* fail2ban-firewalld
>
> For the record, IPv6 is disabled on this server.
>
> Here's the
On Wed, 2020-02-26 at 08:26 +0100, Clement Verna wrote:
> Hi all,
>
> FMN (https://apps.fedoraproject.org/notifications) is currently one
> of the main blocking point for dropping fedmsg in favour of fedora-
> messaging.
> FMN is quite important to the community and the composition of Fedora
>
On 2/26/20 3:33 PM, Bussi Andrea wrote:
On 2/26/20 2:52 PM, Nicolas Kovacs wrote:
Le 26/02/2020 à 13:05, Nicolas Kovacs a écrit :
Weirdly enough, when I follow this suggestion, generate the module
and then empty audit.log and restart my server, I still get the exact
same error again.
On 2/26/20 2:52 PM, Nicolas Kovacs wrote:
Le 26/02/2020 à 13:05, Nicolas Kovacs a écrit :
Weirdly enough, when I follow this suggestion, generate the module and
then empty audit.log and restart my server, I still get the exact same
error again.
Which makes Fail2ban unusable with SELinux in
No missing expected images.
Compose FAILS proposed Rawhide gating check!
1 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 22/171 (x86_64), 1/2 (arm)
New failures (same test not failed in
Le 26/02/2020 à 13:05, Nicolas Kovacs a écrit :
Weirdly enough, when I follow this suggestion, generate the module and then
empty audit.log and restart my server, I still get the exact same error again.
Which makes Fail2ban unusable with SELinux in enforcing mode in the current
state.
Looks
https://bugzilla.redhat.com/show_bug.cgi?id=1807479
Bug ID: 1807479
Summary: Upgrade perl-MooX-late to 0.100
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-MooX-late
Assignee: rc040...@freenet.de
Missing expected images:
Iot dvd aarch64
Iot dvd x86_64
Failed openQA tests: 2/8 (x86_64)
Old failures (same test failed in Fedora-IoT-33-20200224.0):
ID: 527917 Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/527917
ID: 527918 Test:
On 2/26/20 1:05 PM, Nicolas Kovacs wrote:
Hi,
I have an Internet-facing server running CentOS 7. I just installed
Fail2ban using the following packages:
* fail2ban-server
* fail2ban-firewalld
For the record, IPv6 is disabled on this server.
Here's the SELinux error I get.
On 2/25/20 12:05 PM, Michal Schorm wrote:
> Hello,
>
> Will anybody be able to explain to me the current state of the
> containers & containerization in Fedora, please?
>
> I have some questions, but the more I searched for whom & where to
> ask, the more confused I became.
>
> --
>
> 1) There ́s
Hi,
I have an Internet-facing server running CentOS 7. I just installed Fail2ban
using the following packages:
* fail2ban-server
* fail2ban-firewalld
For the record, IPv6 is disabled on this server.
Here's the SELinux error I get.
On Mon, Feb 24, 2020 at 01:53:37PM -0700, Jerry James wrote:
> On Mon, Feb 24, 2020 at 1:57 AM Richard W.M. Jones wrote:
> > * z3 - https://bugzilla.redhat.com/show_bug.cgi?id=1792740
>
> Actually, z3 should build. I checked in a workaround. The bug is
> still open to remind me to figure out
On 26. 02. 20 12:19, Anthony Green wrote:
Thank you for all of the offers. The team that maintains glibc
(Carlos, Florian and DJ) has stepped up to help with libffi packaging.
I think that this is the right group to handle libffi for now.
Thanks!
--
Miro Hrončok
--
Phone: +420777974800
IRC:
Thank you for all of the offers. The team that maintains glibc
(Carlos, Florian and DJ) has stepped up to help with libffi packaging.
I think that this is the right group to handle libffi for now.
Thanks again,
AG
On Tue, Feb 25, 2020 at 10:56 AM Anthony Green wrote:
>
> Hello -- I'm the
Few more notes:
- having just: Release: means every commit bumps
release and hence every commit should likely generate a new record
into changelog => changelog basically becomes dumped `git log` (in
rpm-compatible format) - i.e. there is no capability to group multiple
changes into one changelog
Le 2020-02-26 11:14, Nils Philippsen a écrit :
Well, if we officially were to break with the upgrade path constraints,
we'd have to document this. While we're at it, we should then document
that Rawhide users should use "dnf distro-sync".
That won’t work because (for example) rawhide is
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
On Mon, 2020-02-24 at 18:13 +0100, Miro Hrončok wrote:
> On 24. 02. 20 17:48, Pierre-Yves Chibon wrote:
> > However, for the release field, we are struggling a little bit
> > more, two options
> > are more appealing to us:
>
> Can we please have a "git is the only source of truth" version of
>
Hi Martin,
I was quite busy lately so did not have time to reply.
(Most of the time I'll speak for Rust ecosystem below)
On Fri, Feb 21, 2020 at 4:06 PM Martin Sehnoutka wrote:
>
> Hi,
>
> before I write the proposal itself I just want to stress the fact that
> it isn’t my intention to change
Adam Williamson wrote:
> If a library is not intended for use by other things, it should not be
> installed to the well-known public shared library path. It should be
> installed somewhere private to the application and the application
> should handle including it in its own library path when
On Tue, 2020-02-25 at 17:45 +0100, Miro Hrončok wrote:
> On 25. 02. 20 15:27, Fabio Valentini wrote:
> > Side note: I've been meaning to propose dropping Epoch because of
> > this
> > "we don't care about upgrade path anymore", but I've not gotten
> > around
> > to do that yet
We still need Epoch
Le 2020-02-26 09:50, Martin Sehnoutka a écrit :
Hi,
Hi,
Go package management:
I know that Go has a package management now, but the question is if
upstream communities are going to adopt it.
Upstream communities won’t have any choice if they want their software
to be trusted by third
On Wed, 26 Feb 2020 at 09:43, Fabio Valentini wrote:
> On Wed, Feb 26, 2020 at 8:27 AM Clement Verna
> wrote:
> >
> > Hi all,
> >
> > FMN (https://apps.fedoraproject.org/notifications) is currently one of
> the main blocking point for dropping fedmsg in favour of fedora-messaging.
> > FMN is
On Wed, 26 Feb 2020 at 09:17, Adam Williamson
wrote:
> On Wed, 2020-02-26 at 08:26 +0100, Clement Verna wrote:
> > Hi all,
> >
> > FMN (https://apps.fedoraproject.org/notifications) is currently one of
> the
> > main blocking point for dropping fedmsg in favour of fedora-messaging.
> > FMN is
Le 2020-02-26 08:51, Iñaki Ucar a écrit :
Hi,
Welcome !
I've submitted a new font package for review [1], but I have 0
experience with fonts (I need it to unbundle it from [2]), and I found
the documentation about font packages a little bit outdated. It's a
pretty simple font (OFL, single
W dniu 25.02.2020 o 16:09, Christophe de Dinechin pisze:
> Is there any documented procedure to safely downgrade from rawhide
> to the latest release?
>
> I tried
>
> # dnf update --releasever=32 fedora-release
> # dnf distro-sync --allowerasing --skip-broken
>
> Does something like that have
Hi all,
I've been looking after the ancient Gnome 1 library stack for the last
decade as I had a local use for the libraries. That is no longer the
case so I'm planning to orphan the following packages, none of which
appear to be used by anything else in Fedora (Rawhide):
* libglade
*
Hi,
thank you all for your input! I have few notes:
Review process:
I don't think that the review process is a problem. It is independent of
the file format we use. I mean we can have regular review process and
store the package in a tarball as well as we do it with RPM.
Go package
On Wed, Feb 26, 2020 at 8:27 AM Clement Verna wrote:
>
> Hi all,
>
> FMN (https://apps.fedoraproject.org/notifications) is currently one of the
> main blocking point for dropping fedmsg in favour of fedora-messaging.
> FMN is quite important to the community and the composition of Fedora because
https://bugzilla.redhat.com/show_bug.cgi?id=1807263
--- Comment #2 from Fedora Update System ---
FEDORA-2020-f72d6a2647 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f72d6a2647
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1807263
Paul Howarth changed:
What|Removed |Added
Status|NEW |MODIFIED
Fixed In Version|
On Wed, 2020-02-26 at 08:26 +0100, Clement Verna wrote:
> Hi all,
>
> FMN (https://apps.fedoraproject.org/notifications) is currently one of the
> main blocking point for dropping fedmsg in favour of fedora-messaging.
> FMN is quite important to the community and the composition of Fedora
>
On Tue, Feb 25, 2020 22:26:24 -0500, Randy Barlow wrote:
> On 2/25/20 3:12 PM, Ankur Sinha wrote:
> > Basically, packages do not pass review merely because they use good
> > licenses.
>
> Note that I just said that I thought it was the primary purpose, not
> the only purpose.
Sure, but I'm
74 matches
Mail list logo
