No missing expected images.
Soft failed openQA tests: 1/1 (x86_64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-29-20191125.0):
ID: 488591 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproj
Adam Williamson wrote on Mon, Nov 25, 2019 at 03:55:28PM -0800:
> I gotta say +1 too. I don't buy that there's a significant 'hardening'
> benefit worth all the effort mentioned in the Change *plus* the
> additional consequences Kevin and Martin pointed out. At minimum I'd
> like to see a much more
Hello,
There will be no NeuroFedora team meeting this afternoon. Meetings will
continue next week.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
signature.asc
Description: PGP signature
_
On 11/26/19 12:45 AM, Dominique Martinet wrote:
Adam Williamson wrote on Mon, Nov 25, 2019 at 03:55:28PM -0800:
I gotta say +1 too. I don't buy that there's a significant 'hardening'
benefit worth all the effort mentioned in the Change *plus* the
additional consequences Kevin and Martin pointed
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
Samuel Sieb wrote on Tue, Nov 26, 2019 at 01:38:51AM -0800:
> >FWIW this has happened at an association I help at -- they had VMs with
> >no root password set, and users created by puppet some of whom have
> >sudo.
> >They just expected no root password = no login possible, but it turns
> >out 'su'
https://bugzilla.redhat.com/show_bug.cgi?id=1769913
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Fixed In Version|
On Tue, Nov 26, 2019 at 09:45:44AM +0100, Dominique Martinet wrote:
> FWIW this has happened at an association I help at -- they had VMs with
> no root password set, and users created by puppet some of whom have
> sudo.
> They just expected no root password = no login possible, but it turns
> out '
David Kaufmann wrote on Tue, Nov 26, 2019 at 11:13:15AM +0100:
> On Tue, Nov 26, 2019 at 09:45:44AM +0100, Dominique Martinet wrote:
> > FWIW this has happened at an association I help at -- they had VMs with
> > no root password set, and users created by puppet some of whom have
> > sudo.
> > They
On Mon, Nov 25, 2019 at 10:27 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/DisallowEmptyPasswordsByDefault
>
> == Summary ==
> Remove ''nullok'' parameter from pam_unix module in default PAM
> configuration in order to disallow authentication with empty password.
>
> == Owner ==
Hi,
One of the `munge` package bugs I'm looking into are related to a "Man
Page Scan":
https://bugzilla.redhat.com/show_bug.cgi?id=1612190
Are these suggestions for improvement only, or are they changes that
must be made? Was this a system-wide change or something of the sort,
since I've not hear
On Tuesday, November 26, 2019 3:31:54 AM MST Kamil Paral wrote:
> On Mon, Nov 25, 2019 at 10:27 PM Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/DisallowEmptyPasswordsByDefault
> >
> > == Summary ==
> > Remove ''nullok'' parameter from pam_unix module in default PAM
> > configurati
In preparation for the move of rdiff-backup to python3, we have built
the current beta for rawhide.
In addition to allow testing over older systems, we have also created a
COPR repo, for F29, F30, F31, EPEL7 and EPEL8 for all support
architectures. This can be accessed as "dnf copr enable
frankcr
On Tue, Nov 26, 2019 at 10:37:57AM +, Ankur Sinha wrote:
> Hi,
>
> One of the `munge` package bugs I'm looking into are related to a "Man
> Page Scan":
> https://bugzilla.redhat.com/show_bug.cgi?id=1612190
>
> Are these suggestions for improvement only, or are they changes that
> must be made
On Mon, Nov 25, 2019 at 03:55:28PM -0800, Adam Williamson wrote:
> On Tue, 2019-11-26 at 00:34 +0100, Kevin Kofler wrote:
> > Samuel Sieb wrote:
> > > Steps 1 - 4 are not benefits, they are workarounds to critical system
> > > utilities required by this change. I don't understand why this change
>
26.11.2019, 11:39, "Zbigniew Jędrzejewski-Szmek" :
> On Mon, Nov 25, 2019 at 03:55:28PM -0800, Adam Williamson wrote:
>> On Tue, 2019-11-26 at 00:34 +0100, Kevin Kofler wrote:
>> > Samuel Sieb wrote:
>> > > Steps 1 - 4 are not benefits, they are workarounds to critical system
>> > > utilities
Once upon a time, David Kaufmann said:
> At least with Fedora 31 the root-Password is invalid by default, so I
> guess it has been set to an empty password explicitely.
How does that work with single-user mode, rescue mode, etc.?
In the past, you could change the options to /sbin/sulogin, but sy
On Sun, 2019-11-24 at 12:00 +0100, Thomas Haller wrote:
> On Sun, 2019-11-24 at 11:54 +0100, Thomas Haller wrote:
>
> > when building libnm for Fedora 31, I noticed a recent increase in
> > size.
>
> this seems to be the RHBZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=1775885
>
Hi,
to pro
On Tue, Nov 26, 2019 11:30:16 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Nov 26, 2019 at 10:37:57AM +, Ankur Sinha wrote:
> > Hi,
> >
> > One of the `munge` package bugs I'm looking into are related to a "Man
> > Page Scan":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1612190
> >
On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
How does that work with single-user mode, rescue mode, etc.?
I assume single-user mode does not work. Rescue mode certainly does not
work. It asks for a root password, but root account is locked.
Michael
__
On Tue, Nov 26, 2019 at 9:45 am, Dominique Martinet
wrote:
They just expected no root password = no login possible, but it turns
out 'su' just gave out a root shell with no password entered...
It depends on whether the account is locked or not. In Workstation we
default to locked passwordless
Once upon a time, Michael Catanzaro said:
> On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
> >How does that work with single-user mode, rescue mode, etc.?
>
> I assume single-user mode does not work. Rescue mode certainly does
> not work. It asks for a root password, but root account is loc
On Tue, Nov 26, 2019 at 9:35 am, Chris Adams wrote:
That should be considered a bug IMHO...
At least for rescue mode, probably yes, but I don't know what to do
about it. Can we make systemd's rescue prompt ask for username and
allow logging in with any user account (goal being to log in to a
Hello fellows,
After last publication on LWN about Fedora Modularity mess, I think it
is time to describe the idea I was proposing internally with few other
folks (Adam Samalik, Brian Exelbierd) back in the RH times.
Before I actually go deep, I'll try to answer main questions to myself
(so that
No missing expected images.
Compose FAILS proposed Rawhide gating check!
18 of 43 required tests failed, 17 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 89/161 (x86_64), 1/2 (arm)
New failures (same test not failed in Fed
On Tue, 2019-11-26 at 09:45 +0100, Dominique Martinet wrote:
> Adam Williamson wrote on Mon, Nov 25, 2019 at 03:55:28PM -0800:
> > I gotta say +1 too. I don't buy that there's a significant 'hardening'
> > benefit worth all the effort mentioned in the Change *plus* the
> > additional consequences K
On Tue, 2019-11-26 at 08:14 -0800, Adam Williamson wrote:
> On Tue, 2019-11-26 at 09:45 +0100, Dominique Martinet wrote:
> > Adam Williamson wrote on Mon, Nov 25, 2019 at 03:55:28PM -0800:
> > > I gotta say +1 too. I don't buy that there's a significant 'hardening'
> > > benefit worth all the effor
OLD: Fedora-Rawhide-20191122.n.0
NEW: Fedora-Rawhide-20191126.n.1
= SUMMARY =
Added images:1
Dropped images: 3
Added packages: 59
Dropped packages:5
Upgraded packages: 336
Downgraded packages: 0
Size of added packages: 433.59 MiB
Size of dropped packages
On Tue, Nov 26, 2019 at 8:36 AM Chris Adams wrote:
>
> Once upon a time, Michael Catanzaro said:
> > On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
> > >How does that work with single-user mode, rescue mode, etc.?
> >
> > I assume single-user mode does not work. Rescue mode certainly does
>
Once upon a time, Chris Murphy said:
> On Tue, Nov 26, 2019 at 8:36 AM Chris Adams wrote:
> >
> > Once upon a time, Michael Catanzaro said:
> > > On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
> > > >How does that work with single-user mode, rescue mode, etc.?
> > >
> > > I assume single-u
On Mon, Nov 25, 2019 at 2:26 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/DisallowEmptyPasswordsByDefault
>
> == Summary ==
> Remove ''nullok'' parameter from pam_unix module in default PAM
> configuration in order to disallow authentication with empty password.
How difficult i
On Tue, Nov 26, 2019 at 9:48 AM Chris Adams wrote:
>
> Once upon a time, Chris Murphy said:
> > On Tue, Nov 26, 2019 at 8:36 AM Chris Adams wrote:
> > >
> > > Once upon a time, Michael Catanzaro said:
> > > > On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
> > > > >How does that work with
Dominique Martinet wrote:
> They just expected no root password = no login possible, but it turns
> out 'su' just gave out a root shell with no password entered...
Then they need to RTFM of passwd. The correct way to block password login
for an account is passwd -l, not passwd -d.
Even passwd --
Good Morning Everyone,
Tomorrow we are planning on deploying a new version of pagure and
pagure-dist-git on production.
These changes come with two changes to the packager workflow:
* Anitya integration in dist-git
Something we lost when loosing pkgdb was the easy integration to anitya
(https:/
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, November 26, 2019 6:13 AM, Pierre-Yves Chibon
wrote:
> Good Mo
On Tue, Nov 26, 2019 at 12:22 PM Pierre-Yves Chibon wrote:
>
> Good Morning Everyone,
>
> Tomorrow we are planning on deploying a new version of pagure and
> pagure-dist-git on production.
>
> These changes come with two changes to the packager workflow:
>
> * Anitya integration in dist-git
>
> So
As a meta-goal, we should break up "Modularity" into a number of
separate components, some build-side, some client-side. Modularity
suffers greatly from trying to encode everything into one document.
This greatly raises the complexity of the task and makes it hard to
consider alternative proposals
- Original Message -
> From: "Pierre-Yves Chibon"
> To: devel-annou...@lists.fedoraproject.org
> Sent: Tuesday, November 26, 2019 1:13:45 PM
> Subject: Announcing new anitya integration and de-orphaning process
>
> Good Morning Everyone,
>
> Tomorrow we are planning on deploying a new
On Tue, Nov 26, 2019 at 05:26:40PM +, Gwyn Ciesla via devel wrote:
>
Seconded!
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs
Le mardi 26 novembre 2019 à 16:58 +0100, Igor Gnatenko a écrit :
Hi, Igor
> And we can't actually
> have multiple versions of a package with same name (without "mangled"
> names) in a repo due to the way how our buildsystem works (and not
> only buildsystem, with some caveats).
I suppose you're
On Tue, Nov 26, 2019 at 10:56 AM Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Nov 26, 2019 at 05:26:40PM +, Gwyn Ciesla via devel wrote:
> >
>
> Seconded!
Thirded! Or more like fifthed, actually. This is great.
--
Jerry James
http://www.jamezone.org/
__
Hi list,
I have just orphaned i3-ipc and dzen2. Both packages are dead upstream
and I never used them (I inherited both as parts of the i3 stack).
Feel free to take them, but be aware that you'll effectively have to
become the new upstream.
Cheers,
Dan
signature.asc
Description: PGP signatur
Hi guys,
I just wanted to poll you for some advice. My notification tool I maintain
supports more than 50+ services now, but the only package isolation I do
within 2 RPMs. One for the actual CLI (for admin's who want to use it) and
the other is for the backend library (for Devs). I only ask beca
Chris writes:
Hi guys,
I just wanted to poll you for some advice. My notification tool I maintain
supports more than 50+ services now, but the only package isolation I do
You should really count the number of texlive subpackages…
pgpeYylRqybGZ.pgp
Description: PGP signature
__
\ Original Message
On Nov 26, 2019, 9:45 PM, Sam Varshavchik < mr...@courier-mta.com> wrote:
Chris writes:
> Hi guys,
>
>
> I just wanted to poll you for some advice. My notification tool I maintain
> supports more than 50+ services now, but the only package isolation I do
On Tue, 2019-11-26 at 20:49 -0500, Chris wrote:
> Hi guys,
>
> I just wanted to poll you for some advice. My notification tool I
> maintain supports more than 50+ services now, but the only package
> isolation I do within 2 RPMs. One for the actual CLI (for admin's
> who want to use it) and the
On Tuesday, November 26, 2019 8:10:49 AM MST Michael Catanzaro wrote:
> On Tue, Nov 26, 2019 at 8:03 am, Chris Adams wrote:
>
> > How does that work with single-user mode, rescue mode, etc.?
>
>
> I assume single-user mode does not work. Rescue mode certainly does not
> work. It asks for a roo
On Tuesday, November 26, 2019 8:53:49 AM MST Michael Catanzaro wrote:
> On Tue, Nov 26, 2019 at 9:35 am, Chris Adams wrote:
>
> > That should be considered a bug IMHO...
>
>
> At least for rescue mode, probably yes, but I don't know what to do
> about it. Can we make systemd's rescue prompt as
embree2 is no longer needed by luxcorerender and YafaRay as both
supports embree 3.6.1. There are no other depending packages
so it is now retired from the development repository.
Reference:
---
[1] https://src.fedoraproject.org/rpms/embree2
--
Luya Tshimbalanga
Fedora Design Team
On 11/26/19 8:34 PM, Sérgio Basto wrote:
On Tue, 2019-11-26 at 20:49 -0500, Chris wrote:
I just wanted to poll you for some advice. My notification tool I
maintain supports more than 50+ services now, but the only package
isolation I do within 2 RPMs. One for the actual CLI (for admin's who
No, 50 is perfectly fine. As others mentioned, we have much bigger amount
of them in texlive.
If those are like plugins which may or may not require other packages, I
would split them. And probably put Recommends in the main package for the
most used ones.
On Wed, Nov 27, 2019, 02:58 Chris wrote
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
On 27/11/2019 01:49, Chris wrote:
I kind of like the way nagios-plugins breaks apart it's check_scripts
into many sub-packages, but 50+ subpackages seems a bit extreme... or is
it? It certainly seems like a bit of a nightmare to maintain; it would
be one very large .spec file.
If the subpack
On 11/27/19 5:45 AM, Sam Varshavchik wrote:
Chris writes:
Hi guys,
I just wanted to poll you for some advice. My notification tool I
maintain supports more than 50+ services now, but the only package
isolation I do
You should really count the number of texlive subpackages…
I would not
54 matches
Mail list logo
