On Thu, Jun 2, 2016 at 11:59 PM, Kalev Lember wrote:
> Following is the list of topics that will be discussed in the FESCo
> meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.
>
> To convert UTC to your local time, take a look at
> http://fedoraproject.org/wiki/UTCHowto
>
> or ru
On Fri, Jun 03, 2016 at 02:25:19AM +, Christopher wrote:
> Ugh. Wish I had noticed. Is there a quick way to get it unretired? It's
> still an essential dependency of some packages which are not retired, or
> even orphaned.
I tried to assign nc6 and hadoop to you but pkgdb seems to be not
prop
On Thu, Jun 2, 2016 at 7:09 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, May 31, 2016 at 04:07:28PM -0400, Eric Griffith wrote:
>> On May 31, 2016 15:44, "Adam Williamson" wrote:
>> >
>> > On Tue, 2016-05-31 at 15:26 -0400, Eric Griffith wrote:
>> > > What if the Anaconda team changed it so t
On 06/02/2016 01:39 AM, Gerd Hoffmann wrote:
Hi,
As mentioned, this isn't just about screen, tmux, and nohup (or if
there's any other programs used in a similar context). *Any* command
run with a trailing & is commonly expected to survive logout, usually
from remote shells.
No. They get S
On Thu, 02 Jun 2016 21:03:14 +, you wrote:
>So, it would seem at some point, without me noticing (certainly my fault,
>for not paying attention enough), the Hadoop packages got orphaned and/or
>retired? in Fedora.
March 12 the packager of nc6 orphaned the packages they were
responsible for:
On Thu, Jun 2, 2016 at 5:33 PM gil wrote:
>
>
> Il 02/06/2016 23:20, Chris Murphy ha scritto:
> > On Thu, Jun 2, 2016 at 3:03 PM, Christopher
> wrote:
> >> So, it would seem at some point, without me noticing (certainly my
> fault,
> >> for not paying attention enough), the Hadoop packages got o
On Tue, May 31, 2016 at 04:07:28PM -0400, Eric Griffith wrote:
> On May 31, 2016 15:44, "Adam Williamson" wrote:
> >
> > On Tue, 2016-05-31 at 15:26 -0400, Eric Griffith wrote:
> > > What if the Anaconda team changed it so the "Make this user an
> > > administrator" checkbox also enabled linger?
>
On Tue, May 31, 2016 at 03:04:52PM -0600, Orion Poplawski wrote:
> On 05/29/2016 05:14 PM, Chris Murphy wrote:
> > On Fri, May 27, 2016 at 5:03 PM, Paul Wouters wrote:
> >
> >> If there is a systematic
> >> problem of badly written code leaving orphaned code running when
> >> a user logs out, the
On Thu, 2016-06-02 at 18:01 -0400, Sam Varshavchik wrote:
> Gerd Hoffmann writes:
>
> > On Do, 2016-06-02 at 10:07 -0400, Matthias Clasen wrote:
> > >
> > > You are misinformed. This is not about 'obviously broken' windowing
> > > apps. Applications that have X or wayland connections get killed
>
Gerd Hoffmann writes:
On Do, 2016-06-02 at 10:07 -0400, Matthias Clasen wrote:
>
> You are misinformed. This is not about 'obviously broken' windowing
> apps. Applications that have X or wayland connections get killed
> reliably when the session ends, because that connection is going away.
No.
Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2016-06-03 16:00 UTC'
Links to all tickets below c
Lennart Poettering writes:
Well. Let's say you are responsible for the Linux desktops of a large
security-senstive company (let's say bank, whatever), and the desktops
are installed as fixed workstations, which different employees using
them at different times. They log in, they do some "importa
On Thu, Jun 2, 2016 at 5:21 PM Chris Murphy wrote:
> On Thu, Jun 2, 2016 at 3:03 PM, Christopher
> wrote:
> > So, it would seem at some point, without me noticing (certainly my fault,
> > for not paying attention enough), the Hadoop packages got orphaned and/or
> > retired? in Fedora.
> >
> > Th
Il 02/06/2016 23:20, Chris Murphy ha scritto:
On Thu, Jun 2, 2016 at 3:03 PM, Christopher wrote:
So, it would seem at some point, without me noticing (certainly my fault,
for not paying attention enough), the Hadoop packages got orphaned and/or
retired? in Fedora.
This is a big problem for m
On Thu, Jun 2, 2016 at 3:03 PM, Christopher wrote:
> So, it would seem at some point, without me noticing (certainly my fault,
> for not paying attention enough), the Hadoop packages got orphaned and/or
> retired? in Fedora.
>
> This is a big problem for me, because the main package I work on is
>
So, it would seem at some point, without me noticing (certainly my fault,
for not paying attention enough), the Hadoop packages got orphaned and/or
retired? in Fedora.
This is a big problem for me, because the main package I work on is
dependent upon Hadoop.
What's the state of Hadoop in Fedora t
Thanks.. I forgot an important part.
5. People comment about the broken cycle and then various people
nitpick that comment in some fashion that doesn't improve anything but
'proves' that they are 'correcter' than the commenter. Overall
everyone involved feels worse off.
On 2 June 2016 at 16:31, H
On 2 June 2016 at 21:39, Neal Gompa wrote:
> On Thu, Jun 2, 2016 at 3:21 PM, James Hogarth
> wrote:
> > Right now the retirement guidelines state that you should only retire in
> > branched (prior to freeze) and up to master...
> >
> > But I just had a user bitten by a change in behaviour betwee
On Thu, Jun 2, 2016 at 3:21 PM, James Hogarth wrote:
> Right now the retirement guidelines state that you should only retire in
> branched (prior to freeze) and up to master...
>
> But I just had a user bitten by a change in behaviour between dnf and yum
> that was discovered here:
> https://bugzi
Stephen John Smoogen wrote:
1. There is a problem for a certain group that systemd people care
about (usually desktop but not always).
2. Systemd puts in a fix for that problem.
In this timeline, your step (2) is crucially missing a piece. Systemd has put
in a *change* but it has been shown *n
On Thu, Jun 2, 2016 at 3:44 AM Pierre-Yves Chibon
wrote:
> On Wed, Jun 01, 2016 at 04:37:26PM -0600, Kevin Fenzi wrote:
> > On Wed, 01 Jun 2016 22:30:14 +
> > Christopher wrote:
> >
> > > Thanks. I opened:
> > > https://fedorahosted.org/fedora-infrastructure/ticket/5333 to address
> > > the
On 06/02/2016 02:19 PM, Paul Wouters wrote:
On Jun 1, 2016, at 09:48, Lennart Poettering wrote:
Any scheme that relies on unprivileged programs "being nice" doesn't
fix the inherent security problem: after logout a user should not be
able consume further runtime resources on the system, regardle
On 2 June 2016 at 15:17, Justin Brown wrote:
> On Thu, Jun 2, 2016 at 1:26 PM, Ivan Chavero wrote:
>> Well, if i'm writing a malware i'll make sure it uses systemd-run so it
> keeps on running.
>
> The point of the feature is not to prevent users from running anything in
> the background. It's th
- Original Message -
> From: "Justin Brown"
> To: "Development discussions related to Fedora"
>
> Sent: Thursday, June 2, 2016 1:17:22 PM
> Subject: Re: systemd 230 change - KillUserProcesses defaults to yes
>
> On Thu, Jun 2, 2016 at 1:26 PM, Ivan Chavero < ichav...@redhat.com > wrot
Right now the retirement guidelines state that you should only retire in
branched (prior to freeze) and up to master...
But I just had a user bitten by a change in behaviour between dnf and yum
that was discovered here:
https://bugzilla.redhat.com/show_bug.cgi?id=1096506
This is the bug raised wi
On Thu, Jun 2, 2016 at 1:26 PM, Ivan Chavero wrote:
> Well, if i'm writing a malware i'll make sure it uses systemd-run so it
keeps on running.
The point of the feature is not to prevent users from running anything in
the background. It's that *anything* the user runs has proper systemd
confineme
On Thu, 2016-06-02 at 14:19 -0400, Paul Wouters wrote:
> >
> > On Jun 1, 2016, at 09:48, Lennart Poettering wrote:
> >
> > Any scheme that relies on unprivileged programs "being nice"
> > doesn't
> > fix the inherent security problem: after logout a user should not
> > be
> > able consume further
> On Thursday, June 02, 2016 13:04:44 Lennart Poettering wrote:
> > On Wed, 01.06.16 07:20, Adam Williamson (adamw...@fedoraproject.org) wrote:
> > > On Wed, 2016-06-01 at 15:48 +0200, Lennart Poettering wrote:
> > > > Any scheme that relies on unprivileged programs "being nice" doesn't
> > > > fi
> On Jun 1, 2016, at 09:48, Lennart Poettering wrote:
>
> Any scheme that relies on unprivileged programs "being nice" doesn't
> fix the inherent security problem: after logout a user should not be
> able consume further runtime resources on the system, regardless if he
> does that because of a b
On 06/02/2016 12:37 PM, Tom Rivers wrote:
The potential problem I see with changing the default behavior of
systemd is that it is non-intuitive and could be potentially harmful
if the user is not aware of it. Consider the following example. I
routinely use screen when I connect to the systems
On Wed, Jun 01, 2016 at 10:25:32AM +0100, Tom Hughes wrote:
> On 01/06/16 10:20, Bastien Nocera wrote:
>
> >>On Sun, May 29, 2016 at 06:51:20PM -0600, Chris Murphy wrote:
> >>>So there's tmux, screen, curl, wget, and probably quite a few others
> >>>that don't necessarily get daemonized that are p
On Thu, Jun 2, 2016 at 7:14 AM, Björn Persson wrote:
> Lennart Poettering wrote:
>
>> And even more: after you disabled his
>> user account and logged him out, he really should be gone.
>
> After you disabled his user account, he really should be gone. If he's
> just logged out, he will be back t
ests/20162
> >
> > This is kind of an interesting one I haven't managed to look into yet:
> > I think what's going on is that initial-setup is not behaving as
> > expected because there's no network connection, but I haven't worked
> > out why t
on is that initial-setup is not behaving as
> expected because there's no network connection, but I haven't worked
> out why there's no network connection yet. Will look into it when I
> can.
Did this fail happen with 20160531.n.0? Or is it new in 20160602.n.0?
On 6/2/2016 7:04 AM, Lennart Poettering wrote:
In all of these cases you really want to make sure that whatever the
user did ends – really ends – by the time he logs out.
I apologize if this has already been brought up, but I didn't see this
particular point raised in the replies I've read and
On Tue, May 31, 2016 at 9:37 PM, Jan Kurik wrote:
> On Wed, May 4, 2016 at 3:03 AM, Langdon White wrote:
>> Hi,
>>
>> Unfortunately, I heard from some of the new voting members that the current
>> Modularity WG meeting time is not doable for them. Please use the link below
>> to help us figure ou
Hi,
> I don't think we need to change Fedora 24 for this. Unless I misunderstood,
> this
> systemd change has not been pushed to Fedora 24 (nor proposed for it). We're
> prepping for how to deal with things in Fedora 25.
No, I was the one misunderstanding things. I thought the systemd
change go
On Thu, Jun 02, 2016 at 01:04:44PM +0200, Lennart Poettering wrote:
> Well. Let's say you are responsible for the Linux desktops of a large
> security-senstive company (let's say bank, whatever), and the desktops
> are installed as fixed workstations, which different employees using
> them at diffe
On Thu, Jun 2, 2016 at 9:01 AM, Ray Strode wrote:
>
> Of course, starting in Fedora 24, we no longer have a session bus.
> It's a user bus now. So the bus won't go away until the last user
> session (for a user) ends, and those background services won't go away
> until they lose their bus connec
On 06/02/2016 11:36 AM, Jóhann B. Guðmundsson wrote:
> On 06/02/2016 03:13 PM, Stephen Gallagher wrote:
>
>> I don't think we need to change Fedora 24 for this. Unless I misunderstood,
>> this
>> systemd change has not been pushed to Fedora 24 (nor proposed for it). We're
>> prepping for how to d
On 06/02/2016 03:13 PM, Stephen Gallagher wrote:
I don't think we need to change Fedora 24 for this. Unless I misunderstood, this
systemd change has not been pushed to Fedora 24 (nor proposed for it). We're
prepping for how to deal with things in Fedora 25.
You should not so easily dismiss and
On Thu, 2016-06-02 at 14:28 +, Fedora compose checker wrote:
> Missing expected images:
>
> Kde live i386
> Kde live x86_64
> Cloud_base raw-xz i386
>
> Failed openQA tests: 3/70 (x86_64), 2/16 (i386), 1/2 (arm)
>
> ID: 20162 Test: x86_64 Workstation-live-iso install_default@uefi
> URL:
On 06/02/2016 11:01 AM, Ray Strode wrote:
> Hi,
>
> On Wed, Jun 1, 2016 at 10:58 AM, Matthias Clasen wrote:
>> Leaking session processes have been a perennial problem that
>> we have been battling forever (gconf, ibus, pulseaudio, the list goes
>> on...). And they are causing actual problems, fro
On 2 June 2016 at 11:01, Ray Strode wrote:
> Hi,
>
>
> We may want to consider reverting the user bus change for F24 and
> revisit in F25, not sure.
I believe we are less than a week from releasing F24... if there is a
need to do this how far back does testing need to go? Are we back to
alp
Hi,
On Wed, Jun 1, 2016 at 10:58 AM, Matthias Clasen wrote:
> Leaking session processes have been a perennial problem that
> we have been battling forever (gconf, ibus, pulseaudio, the list goes
> on...). And they are causing actual problems, from preventing re-login
> to subtly breaking the next
Hi,
> In all of these cases you really want to make sure that whatever the
> user did ends – really ends – by the time he logs out.
Sure, there are valid use cases for that. The admin will probably also
turn off lingering then, right?
So, what is problem with simply allowing screen + tmux con
On Thu, 2016-06-02 at 13:04 +0200, Lennart Poettering wrote:
> On Wed, 01.06.16 07:20, Adam Williamson (adamw...@fedoraproject.org) wrote:
>
> > On Wed, 2016-06-01 at 15:48 +0200, Lennart Poettering wrote:
> > >
> > > Any scheme that relies on unprivileged programs "being nice" doesn't
> > > fix
On Do, 2016-06-02 at 10:07 -0400, Matthias Clasen wrote:
> On Thu, 2016-06-02 at 10:02 -0400, Paul Wouters wrote:
> >
> > People aren't agreeing with you. So making it a default seems like a
> > bad
> > idea. People do seem to agree on "obviously broken windoing apps"
> > that
> > are left lingeri
Missing expected images:
Kde live i386
Kde live x86_64
Cloud_base raw-xz i386
Failed openQA tests: 3/70 (x86_64), 2/16 (i386), 1/2 (arm)
ID: 20162 Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/20162
ID: 20173 Test: arm Minimal-raw_
On Thu, 2 Jun 2016 14:14:17 +0200
Petr Šplíchal wrote:
...snip...
> I forgot to update my email address in FAS. This should be fixed
> now. Thanks for the reminder. Hope everything is now clear.
>
> psss...
Yes indeed. Thanks for the quick answer and keeping maintaining your
packages. :)
kev
On Thu, 2 Jun 2016 12:29:16 +0300
Oded Gabbay wrote:
> Hi,
> That is my old email address.
> I'll update it to my new email address.
Thanks very much for the quick answer and keeping maintaining your
packages. ;)
kevin
pgpQUNaGaEq2E.pgp
Description: OpenPGP digital signature
--
devel mailing
On Thu, 2016-06-02 at 10:02 -0400, Paul Wouters wrote:
>
> People aren't agreeing with you. So making it a default seems like a
> bad
> idea. People do seem to agree on "obviously broken windoing apps"
> that
> are left lingering. Why can't we just let those get killed?
>
You are misinformed. Th
hi
i retired solr and parquet depend on hadoop that was retired
parquet-format was used only by parquet
regards
.g
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Thu, 2 Jun 2016, Lennart Poettering wrote:
Well. Let's say you are responsible for the Linux desktops of a large
security-senstive company (let's say bank, whatever), and the desktops
are installed as fixed workstations, which different employees using
them at different times. They log in, th
OLD: Fedora-24-20160601.n.0
NEW: Fedora-24-20160602.n.0
= SUMMARY =
Added images:0
Dropped images: 9
Added packages: 0
Dropped packages:2
Upgraded packages: 2
Downgraded packages: 0
Size of added packages: 0.00 B
Size of dropped packages:36.39 MiB
Size of
Lennart Poettering wrote:
> On Wed, 01.06.16 07:20, Adam Williamson (adamw...@fedoraproject.org) wrote:
>
> > On Wed, 2016-06-01 at 15:48 +0200, Lennart Poettering wrote:
> > >
> > > Any scheme that relies on unprivileged programs "being nice" doesn't
> > > fix the inherent security problem: a
Hi,
new version of DNF and DNF-PLUGINS-CORE is out. This release is focused on
stability
and should ease the transition for prepared DNF 2.0. Any call of not documented
and
so not supported Python methods should print warning. If you see them and you
would
like the methods to be included into D
Hi
someone could update picketbox [1] to 4.9.5.Final(not more newer just
this one)
is necessary for import a dependency of wildfly 10+
thanks in advance
regards
.g
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1342100
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fed
Hi!
2016-06-02 13:35 GMT+02:00 David Kutalek :
>
> Hi,
>
> wrt psss - former email: pspli...@redhat.com:
>
> Afaik:
> - he would like to continue with did (with other e-mail address)
Yes, I'm taking did as my personal hobby project and will continue
with the development. Ondřej Pták offered help
On Thursday, June 02, 2016 13:04:44 Lennart Poettering wrote:
> On Wed, 01.06.16 07:20, Adam Williamson (adamw...@fedoraproject.org) wrote:
> > On Wed, 2016-06-01 at 15:48 +0200, Lennart Poettering wrote:
> > > Any scheme that relies on unprivileged programs "being nice" doesn't
> > > fix the inher
Hi,
I started rebuilds of whole rubygems.org as RPM packages in Copr.
See:
https://copr.fedorainfracloud.org/coprs/g/rubygems/rubygems/
However lots of gems cannot be imported due licensing problems.
Such gems fail with this dist-git log:
http://copr-dist-git.fedorainfracloud.org/per-task-logs
On Wed, 01.06.16 07:20, Adam Williamson (adamw...@fedoraproject.org) wrote:
> On Wed, 2016-06-01 at 15:48 +0200, Lennart Poettering wrote:
> >
> > Any scheme that relies on unprivileged programs "being nice" doesn't
> > fix the inherent security problem: after logout a user should not be
> > able
On Wed, 01.06.16 16:28, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> Five years ago, so basically from day one. We have this optional
> security feature – fantastic!
> Also, the concept of a ”session” isn't anything new, it's core UNIX
> concept (setsid() enyone?)
setsid() is really mostly a
On Thu, 2 Jun 2016 09:31:46 +0200
Normand wrote:
> Hi there,
>
> This is the first time I am using fedpkg update command, and I hit
> the error (1). Is the "Cannot find release ..." error a concequence
> of f24 still not yet released ? or is there something wrong in my
> setup of fedpkg environm
Hi
undertow package changes from ASL 2.0 and LGPLv2 to ASL 2.0
regards
.g
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On 02/06/2016 10:53, Charalampos Stratakis wrote:
Hello Normand,
As I saw there are no builds of your package. When you do some changes to your package you need to
build it first with "fedpkg build". After that you can do a "fedpkg update" to
sent it to bodhi so it goes through the testing re
Hi,
That is my old email address.
I'll update it to my new email address.
Oded
On Thu, Jun 2, 2016 at 12:50 AM, Kevin Fenzi wrote:
> Greetings, we've been told that the email addresses
> for these package maintainers are no longer valid. I'm starting the
> unresponsive maintainer policy to find
Hello Normand,
As I saw there are no builds of your package. When you do some changes to your
package you need to build it first with "fedpkg build". After that you can do a
"fedpkg update" to sent it to bodhi so it goes through the testing repositories
and then to stable (fedpkg update is not
On Wed, Jun 01, 2016 at 04:37:26PM -0600, Kevin Fenzi wrote:
> On Wed, 01 Jun 2016 22:30:14 +
> Christopher wrote:
>
> > Thanks. I opened:
> > https://fedorahosted.org/fedora-infrastructure/ticket/5333 to address
> > the issue more broadly (I figure this would be useful to others, and
> > not
ca32219fff65ccc29eafca368b7540d5 Regexp-Common-2016060101.tar.gz
http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Regexp-Common/Regexp-Common-2016060101.tar.gz/md5/ca32219fff65ccc29eafca368b7540d5/Regexp-Common-2016060101.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki
Hi,
> As mentioned, this isn't just about screen, tmux, and nohup (or if
> there's any other programs used in a similar context). *Any* command
> run with a trailing & is commonly expected to survive logout, usually
> from remote shells.
No. They get SIGHUP when you logout, and the default act
Hi there,
This is the first time I am using fedpkg update command, and I hit the error
(1).
Is the "Cannot find release ..." error a concequence of f24 still not yet
released ?
or is there something wrong in my setup of fedpkg environment ?
=== (1)
[michel@fc24ppc64le:~/work/libcxl]
$git branc
72 matches
Mail list logo
