Adam Williamson wrote:
> What exactly would you have had me do? Just sit on this and pretend
> there was no bug and when we saw more and more people come into #fedora
> and complain about it, tell them the risk was minimal so they should
> just suck it up and get on with their lives? I mean, seriou
On 10/06/2016 05:45 AM, Adam Williamson wrote:
On Wed, 2016-10-05 at 20:38 -0700, Andrew Lutomirski wrote:
I don't understand how you arrive at this conclusion. dnf is sitting
on the top of a house of cards when it's running in Terminal. If
anything below it dies, dnf dies and by extension so
On 10/05/2016 03:00 AM, Adam Williamson wrote:
On Tue, 2016-10-04 at 20:43 -0400, Sam Varshavchik wrote:
But ordinary regular app updates will happily run on cruise control, without
bringing the system down into single user mode. If Android can do that, I
see no reason why Fedora can't, either.
Hi,
On 05-10-16 20:30, Bruno Wolff III wrote:
On Wed, Oct 05, 2016 at 14:19:12 -0400,
Matthew Miller wrote:
In any case, what do you all think?
I don't think the tracking side would be hard to do. What I'd like to hear
about is how the list will work for getting bugs better fixed than bug
As for the KDE part:
Adam Williamson wrote:
> The 'standard Fedora solution' for KDE is...well I don't know,
The standard updater on the KDE Spin is plasma-pk-updates. The other tools
can also do updates (or at least they claim to be able to), but the applet
in the system tray that automaticall
https://bugzilla.redhat.com/show_bug.cgi?id=1381897
--- Comment #4 from Fedora Update System ---
perl-Messaging-Message-1.6.1-1.el6 has been pushed to the Fedora EPEL 6 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/Q
On Tue, Oct 4, 2016 at 10:42 AM, Igor Gnatenko wrote:
> Hi,
>
> I'm preparing update for new version. According to release notes[0],
> there is only API additions and couple of changes. I will rebuild all
> dependent packages:
> * gstreamer-plugins-bad-free
Rebuilt and patch sent upstream:
https:/
On Tue, Oct 4, 2016 at 10:18 AM, Björn Esser wrote:
> Am 03.10.2016 um 06:10 schrieb Björn Esser:
>>
>> Chain-build is running:
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=15917326
>>
>>
>> Am 03.10.2016 um 05:38 schrieb Björn Esser:
>>>
>>> I'm upgrading jsoncpp to v1.7.7 in Rawhide.
Am 06.10.2016 um 11:09 schrieb Igor Gnatenko:
On Tue, Oct 4, 2016 at 10:18 AM, Björn Esser wrote:
Am 03.10.2016 um 06:10 schrieb Björn Esser:
Chain-build is running:
https://koji.fedoraproject.org/koji/taskinfo?taskID=15917326
Am 03.10.2016 um 05:38 schrieb Björn Esser:
I'm upgrading jsoncp
Adam Williamson writes:
On Wed, 2016-10-05 at 23:54 -0400, Sam Varshavchik wrote:
> * As a general workaround for this type of crashes, we need a
> > complete-transaction command in DNF – please add your voices to:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1091702
> > – and not the
On Wed, Oct 05, 2016 at 12:16:32PM -0600, Tim Flink wrote:
> On Tue, 4 Oct 2016 09:19:15 -0400
> Matthew Miller wrote:
>
> > On Mon, Oct 03, 2016 at 02:35:00PM -0600, Kevin Fenzi wrote:
> > > Another alternate here is that we could make taskotron a 'namespace'
> > > like currently rpms/ and docke
On Wed, Oct 5, 2016 at 8:43 PM, Adam Williamson
wrote:
>
> OK, from now on when I see bugs causing serious real world consequences
> for multiple real world reporters I'll just shut up and pretend it's
> not happening, shall I? Wouldn't want to be all 'alarmist' about it.
Adam... those question
In theory, I like this idea.
In practice, Kevin Kofler is probably right. Unless there is a big hammer,
bugs don't get fixed in many cases.
So I think the solution should be different: gfx team needs more manpower so
they can handle bug reports. Right now, for some packages bugzilla serves as
Hi every one,
Reading all ideas about solving issues with upgrading systems from working
systems are more or less ideas of ad choc solving some issues or even more
or less reinventing the wheel. IMO all those ideas will not solve anything
and will only increase total level of entropy. After this w
On Thu, Oct 06, 2016 at 12:44:02PM +, Zbigniew Jędrzejewski-Szmek wrote:
> Maybe we should standardize the prefix for git commits: "taskotron: "
> or "tests: " or whatever, so it's easy to stop in git history.
That'll have to be automated somehow or I don't think people will
remember.
--
Ma
06.10.2016, 08:23, "Pierre-Yves Chibon":
> On Wed, Oct 05, 2016 at 06:36:16PM +0300, Ponomarenko Andrey wrote:
>> The tool is based on different software stack for analysis of backward
>> compatibility developed since 2009: https://github.com/lvc (ABI Compliance
>> Checker, ABI Dumper, etc.)
>
On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote:
Adam Williamson wrote:
What exactly would you have had me do? Just sit on this and pretend
there was no bug and when we saw more and more people come into #fedora
and complain about it, tell them the risk was minimal so they should
just suck it
On Thu, 2016-10-06 at 08:20 -0700, Adam Williamson wrote:
> On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> What exactly would you have had me do? Just sit on this and pretend
> there was no bug and when we saw more and more people come into #fedora
> and complain
On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote:
> Missing expected images:
>
> Cloud_base raw-xz i386
> Atomic raw-xz x86_64
These are not expected, they are not things configured to be built in the
compose.
Dennis
signature.asc
Description: This is a digitally sig
On Wednesday, October 5, 2016 2:41:50 PM CDT Colin Walters wrote:
> Now that Cloud -> Atomic and will be focusing on Project Atomic, can we move
> the Docker base image into this group from the "Fedora Base" group?
>
> It never really made sense to me in Base; in:
>
> $ git log --format='%ae' fed
On Thu, 2016-10-06 at 10:39 +0200, Hans de Goede wrote:
>
> So I like the idea, I do propose to simply re-use most of
> the blocker bug process for this, rather then inventing yet
> another process. I guess this could even be integrated and
> the way to get bugs on the list would be to propose the
On Thu, 2016-10-06 at 10:26 -0500, Dennis Gilmore wrote:
> On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote:
> > Missing expected images:
> >
> > Cloud_base raw-xz i386
> > Atomic raw-xz x86_64
>
>
> These are not expected, they are not things configured to be built in
On Thu, Oct 6, 2016 at 5:30 PM, Adam Williamson
wrote:
> On Thu, 2016-10-06 at 10:26 -0500, Dennis Gilmore wrote:
>> On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote:
>> > Missing expected images:
>> >
>> > Cloud_base raw-xz i386
>> > Atomic raw-xz x86_64
>>
>>
>> These a
On Thu, Oct 6, 2016 at 7:43 AM, Tomasz Kłoczko wrote:
> So how problem of consistent upgrade have been solved on Solaris using ZFS
> and IPS?
> ZFS has ability to create snapshot of the vol (RO resource) and create on
> top of the shapshot clone (RW resource).
> Whole upgrade process consist fro
Hi,
I need/want/would like to build new node 6 for EL6, but gcc is too old.
For that reason, I'd like to use devtoolset-4-gcc, but the build fails
(obviously) because the package doesn't exist.
So, is there a way to make that work somehow?
I am not sure about enabling external repos during buil
I found this article stating some alarming claims about systemd
security, are this claims true?
If so, as developers should we be hardening systemd?
It states stuff like this:
"
Systemd's "we don't make mistakes" attitude towards security can be seen in
other places, such as this code from t
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-10-07 16:00 UTC'
Links to all tickets below
On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote:
>
> I found this article stating some alarming claims about systemd
> security, are this claims true?
>
First of all, do not hijack threads. If you want to start something new,
start it, and do not reply to unrelated thread.
Sec
On Thu, 06.10.16 12:33, Ivan Chavero (ichav...@redhat.com) wrote:
> Setting a umask of 0 means that, by default, any file created by systemd
> will be world-readable and -writable. Systemd defines a macro called
> RUN_WITH_UMASK
> which is used to temporarily set a more restrictive umask when s
Hello,
I was surprised to see /usr/share/texlive on my system although I
remembered very well removing it months ago. It turned out to be
caused by two rpmsave files, although some *empty* directories weren't
removed:
$ find /usr/share/texlive/
/usr/share/texlive/
/usr/share/texlive/texmf-dist
/u
Hello,
I have an issue that likely needs a bug or something to fix but I'm
not sure which component is at fault. So I'm writing here in the hopes
that someone will know where to point me.
I have a F24 Workstation where I've been using libvirt/qemu VMs for
development for awhile now. It works
On 05.10.2016 12:44, Pierre-Yves Chibon wrote:
> It has been a month, more than I expected, so I asked FESCo to consider the
> user
> spike MIA: https://fedorahosted.org/fesco/ticket/1632
Sorry, must have missed that mail. Just changed my Bugzilla EMail address back
to what is was.
On Thu, Oct 6, 2016 at 10:32 AM, Zuzana Svetlikova
wrote:
> Hi,
>
> I need/want/would like to build new node 6 for EL6, but gcc is too old.
> For that reason, I'd like to use devtoolset-4-gcc, but the build fails
> (obviously) because the package doesn't exist.
>
> So, is there a way to make that
On Thu, Oct 06, 2016 at 07:20:55PM +0200, spike wrote:
> On 05.10.2016 12:44, Pierre-Yves Chibon wrote:
> > It has been a month, more than I expected, so I asked FESCo to consider the
> > user
> > spike MIA: https://fedorahosted.org/fesco/ticket/1632
>
> Sorry, must have missed that mail. Just ch
Missing expected images:
Kde live i386
Workstation live i386
Server dvd i386
Server boot x86_64
Server dvd x86_64
Kde live x86_64
Cloud_base raw-xz x86_64
Xfce raw-xz armhfp
Cloud_base raw-xz i386
Server boot i386
Atomic raw-xz x86_64
Minimal raw-xz armhfp
Workstation live x86_64
Failed openQA te
"checksums": {
"sha256":
"79e98c18676919782db4ef29d6bf5ce6e79f9dbe91ad95cbe7155682a73b09d0"
},
"disc_count": 1,
"disc_n
At the Fedora 25 Beta Go/No-Go Meeting [1][2] that just ended,
has been agreed by QA, Release Engineering and Development
representatives to go live with the Fedora 25 Beta [3].
Fedora 25 Beta will be publicly available on Oct 11, 2016.
Meeting details can be seen here:
[1] Minutes:
https://meet
On Thu, Oct 06, 2016 at 11:08:21AM -0600, Nathanael D. Noblet wrote:
> Hello,
>
> I have an issue that likely needs a bug or something to fix but I'm
> not sure which component is at fault. So I'm writing here in the hopes
> that someone will know where to point me.
>
> I have a F24 Workstati
On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote:
> I rarely mess with docker, but I expect that the docker0 bridge has
> an ip
> address on it which may conflict with the one on libvirt
> bridge. That is to
> say, if they are on the same subnet, and the route for the docker0
> bridge takes
>
Missing expected images:
Kde live i386
Workstation live i386
Server dvd i386
Server boot x86_64
Server dvd x86_64
Kde live x86_64
Cloud_base raw-xz x86_64
Cloud_base raw-xz i386
Server boot i386
Atomic raw-xz x86_64
Kde raw-xz armhfp
Minimal raw-xz armhfp
Workstation live x86_64
Failed openQA tes
On Thu, 2016-10-06 at 12:39 -0600, Nathanael D. Noblet wrote:
> On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote:
> >
> > I rarely mess with docker, but I expect that the docker0 bridge has
> > an ip
> > address on it which may conflict with the one on libvirt
> > bridge. That is to
> > say,
On Thu, Oct 06, 2016 at 02:02:09PM -0500, Dan Williams wrote:
> On Thu, 2016-10-06 at 12:39 -0600, Nathanael D. Noblet wrote:
> > On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote:
> > >
> > > I rarely mess with docker, but I expect that the docker0 bridge has
> > > an ip
> > > address on it wh
Hi everyone,
the F25 Beta Readiness meeting has shown readiness of all teams for
the F25 Beta release. There were no major issues reported during the
meeting and all teams stated we are ready to release the F25 Beta as
planned, on October 11th, 2016 at 14:00 UTC. For more details please
check the
On Thu, Oct 06, 2016 at 08:20:34AM -0700, Adam Williamson wrote:
> On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote:
> > rpm -Uvh --nodeps --nopostun \
> >
> > http://$MIRROR/updates/testing/25/x86_64/s/systemd-udev-231-8.fc25.x86_64.rpm
>
> Huh - that's handy, and I did not actually know
- Original Message -
> From: "Tomasz Torcz"
> To: devel@lists.fedoraproject.org
> Sent: Thursday, October 6, 2016 11:53:23 AM
> Subject: Re: Systemd Security
>
> On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote:
> >
> > I found this article stating some alarming claims abou
On Thu, Oct 06, 2016 at 04:05:34PM -0400, Ivan Chavero wrote:
> > On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote:
> > >
> > > I found this article stating some alarming claims about systemd
> > > security, are this claims true?
> > >
> >
> > First of all, do not hijack threads. I
On Thu, 2016-10-06 at 16:05 -0400, Ivan Chavero wrote:
> I'm not hijacking any thread, I STARTED this thread (BTW, just searched for
> emails
> with the "Systemd Security" subject in this mailing list and didn't find any
> immediate matches) because i have an honest concern for Systemd Security a
Once upon a time, Ivan Chavero said:
> I'm not hijacking any thread, I STARTED this thread
No, you didn't start a thread. You posted a reply to an unrelated
message (the subject of that message was "Re: Fedora 25 Beta 1.1 compose
check report").
When you want to start a new thread, do not reply
c18676919782db4ef29d6bf5ce6e79f9dbe91ad95cbe7155682a73b09d0" },
> "disc_count": 1,
> "disc_number": 1,
> "format": "raw.xz",
> "implant_md5"
- Original Message -
> From: "Lennart Poettering"
> To: "Development discussions related to Fedora"
>
> Sent: Thursday, October 6, 2016 11:58:06 AM
> Subject: Re: Systemd Security
>
> On Thu, 06.10.16 12:33, Ivan Chavero (ichav...@redhat.com) wrote:
>
> > Setting a umask of 0 means t
On Thu, 2016-10-06 at 15:11 -0500, Dennis Gilmore wrote:
> For the sake of clarity (It was resolved on IRC) we deliver all artifacts as
> part of teh nightly branched/rawhide composes, the atomic host production
> deliverables are only delivered via the two week atomic host process and not
> as
On Wed, Oct 05, 2016 at 03:26:10PM -0700, Japheth Cleaver wrote:
> I don't know what the dnf equivalent is, but isn't that precisely what the
> 'needs-restarting' command provided?
DNF has the tracer plugin for doing exactly that, including printing a
list of commands to restart the affected servi
- Original Message -
> From: "Tomasz Torcz"
> To: devel@lists.fedoraproject.org
> Sent: Thursday, October 6, 2016 3:11:36 PM
> Subject: Re: Systemd Security
>
> On Thu, Oct 06, 2016 at 04:05:34PM -0400, Ivan Chavero wrote:
> > > On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wro
On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > What exactly would you have had me do? Just sit on this and pretend
> > there was no bug and when we saw more and more people come into #fedora
> > and complain about it, tell them the risk was minimal so they shoul
Adam Williamson wrote:
> Next time maybe I'll just say 'screw this' and go play golf instead, if this
> is the thanks I get for trying to help people out.
Others have thanked you, actually, but parts of this email chain have gotten a
little heated, so I guess it's worth repeating: Thanks for sta
Can anyone answer this relatively simple question: "Why grubby?" I've seen a
number of discussions on various topics surrounding the boot loader that all
seem to devolve into "We would love to support that, but grubby doesn't, so we
can't."
At what point does the maintenance burden of using gr
On Thu, 2016-10-06 at 17:05 -0400, Eric Griffith wrote:
> Can anyone answer this relatively simple question: "Why grubby?" I've
> seen a number of discussions on various topics surrounding the boot
> loader that all seem to devolve into "We would love to support that,
> but grubby doesn't, so we ca
On Thu, 6 Oct 2016 17:05:45 -0400
Eric Griffith wrote:
> Can anyone answer this relatively simple question: "Why grubby?" I've
> seen a number of discussions on various topics surrounding the boot
> loader that all seem to devolve into "We would love to support that,
> but grubby doesn't, so we c
At risk of asking a redundant question, I'm assuming Wayland is still a go?
IIRC the contingency deadline was the beta.
I ask because it does not appear to be a part of the changeset, yet this FEDCo
ticket seems to suggest otherwise:
https://fedorahosted.org/fesco/ticket/1615
We've discussed how and whether it's best practice to disallow a user from
logging into an account they previously had access to.
But now I'm sorta curious about the opposite situation: What's the use case for
blocking a user from accessing their account, rather than just deleting the
account a
Er, let me clarify: Much of the discussion here, as I see it, has been about
how to preserve a user account, but block user access to that account.
My question is: If it were really important to make sure the user could no
longer access the system at all, why not just delete the account? Deletin
maybe I'm come with not right answer ,
I think that depend by network configuration over internet and routing process
over applications. so will not be any conflict. I'm right?
> Both docker and libvirt use iptables to direct traffic in various ways. They
> may well be in conflict
2016-10-06 22
I just noticed that I can't take a screenshot of anything on the secondary
display when using two displays - you just get a transparent PNG. In fact,
if you try and grab an area that spans the displays it'll capture the
screen from the primary display properly while the area from the secondary
disp
On Thu, 2016-10-06 at 21:22 +, Jeremy Newton wrote:
> At risk of asking a redundant question, I'm assuming Wayland is still a go?
> IIRC the contingency deadline was the beta.
Workstation still uses Wayland by default in the Beta, yep.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw
>My question is: If it were really important to make sure the user could no
>longer access the system at all, why not just delete the account? Deleting the
>user does not >(necessarily) delete their data, so what's the use case for
>keeping the account at all in such a situation?
In my experien
Adam Williamson wrote:
> Huh - that's handy, and I did not actually know --nopostun (something
> new every day, etc.). It does involve including instructions on how to
> find the package, though, which would inevitably go stale as it moves
> from u-t to stable. Still, thanks.
Seeing how this is no
Once upon a time, Andrew Toskin said:
> But now I'm sorta curious about the opposite situation: What's the use case
> for blocking a user from accessing their account, rather than just deleting
> the account altogether?
There are lots of reasons. For example, if someone is paying for an
accoun
On Fri, 2016-10-07 at 01:25 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Huh - that's handy, and I did not actually know --nopostun (something
> > new every day, etc.). It does involve including instructions on how to
> > find the package, though, which would inevitably go stale as it mo
On Wed, Oct 05, 2016 at 01:57:20PM -, Peter Larsen wrote:
> > I never needed to reboot. I just keep working on my stuff, when I'm
> > done I turn the laptop off. Is there any reason to reboot right after
> > updating?
>
> That's actually a very common misunderstanding. People think that "y
On Thu, Oct 6, 2016 at 3:17 PM, Kevin Fenzi wrote:
> On Thu, 6 Oct 2016 17:05:45 -0400
> Eric Griffith wrote:
>
>> Can anyone answer this relatively simple question: "Why grubby?" I've
>> seen a number of discussions on various topics surrounding the boot
>> loader that all seem to devolve into "
On Thu, Oct 6, 2016 at 3:59 PM, Jeffrey Ollie wrote:
> I just noticed that I can't take a screenshot of anything on the secondary
> display when using two displays - you just get a transparent PNG. In fact,
> if you try and grab an area that spans the displays it'll capture the screen
> from the p
I'm just thinking out loud here, but, given that rpm-ostree does not use
grubby, and we do have the Bootloader Spec, and no other distro uses grubby,
would it be prudent to take a really hard look at whether grubby is still a
path we want to walk?
If it is, then more work obviously needs to be
On Thu, Oct 06, 2016 at 07:20:55PM +0200, spike wrote:
> On 05.10.2016 12:44, Pierre-Yves Chibon wrote:
> > It has been a month, more than I expected, so I asked FESCo to consider the
> > user
> > spike MIA: https://fedorahosted.org/fesco/ticket/1632
>
> Sorry, must have missed that mail. Just ch
73 matches
Mail list logo
