On Fri, Oct 7, 2016 at 5:58 PM, Andrew Lutomirski wrote:
> On Fri, Oct 7, 2016 at 2:32 PM, Chris Murphy wrote:
>> Modifying the image at all breaks the existing media verification
>> option in the boot menu, and we know people get bad writes using bad
>> or flaky media
>
> This part, at least, sh
Hi folks! I'm proposing we cancel Monday's blocker review meeting.
There's just one proposed Final blocker to review:
https://bugzilla.redhat.com/show_bug.cgi?id=1382001
there are five proposed Final freeze exceptions, but we're some way out
from Final freeze, no real need to review them yet. I f
# Fedora Quality Assurance Meeting
# Date: 2016-10-10
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time again on Monday! We've polished off the Beta, so it's
time to clean up any loose en
On Tue, Oct 04, 2016 at 09:16:12AM -0600, Chris Murphy wrote:
> Over on Windows and macOS, there is no such thing as a non-destructive
> install media creation. It warns but obliterates the entire stick.
> They also don't have persistence. So I think you're on very solid
> ground calling both featu
Dear All,
I intend to unretire the package psad (Port Scan Attack Detector)
which was retired due to not having a native systemd unit.
I have updated the package to the latest upstream version which
supports journalctl and added an unit file. Here's my review
request: https://bugzilla.redhat.com/s
On Fri, Oct 7, 2016 at 4:55 PM, Josh Boyer wrote:
> On Fri, Oct 7, 2016 at 5:14 PM, Chris Murphy wrote:
>> Changed this subject to match the other one I changed, so if I'm doing
>> it wrong at least I'm consistent!
>>
>> On Fri, Oct 7, 2016 at 9:22 AM, Kevin Fenzi wrote:
>>> So, I think we would
On Fri, Oct 7, 2016 at 2:32 PM, Chris Murphy wrote:
> Modifying the image at all breaks the existing media verification
> option in the boot menu, and we know people get bad writes using bad
> or flaky media
This part, at least, should be relatively straightforward to get
around. The allocation
On Fri, Oct 7, 2016 at 5:14 PM, Chris Murphy wrote:
> Changed this subject to match the other one I changed, so if I'm doing
> it wrong at least I'm consistent!
>
> On Fri, Oct 7, 2016 at 9:22 AM, Kevin Fenzi wrote:
>> So, I think we would need to get buyin to get our changes into the spec
>> and
On Fri, 2016-10-07 at 13:32 -0700, Andrew Lutomirski wrote:
>
> At the risk of muddying the waters a bit: now that OverlayFS is here, I
> think that even a dd-copied image should be able to support persistence.
> The image could notice that it's dd-copied (by checking GPT GUIDs or layout
> or what
On Fri, Oct 7, 2016 at 2:08 PM, Adam Williamson
wrote:
> Hi folks! Sending this to devel@ as well as test@ as there's been some
> relevant discussion there recently. We've been kicking around a couple
> of issues lately:
>
> 1. Exactly what do we need to test and block on, in terms of writing
> im
On Fri, Oct 7, 2016 at 2:32 PM, Andrew Lutomirski wrote:
> On Oct 7, 2016 12:39 PM, "Adam Williamson"
> wrote:
>>
>> On Mon, 2016-10-03 at 20:03 +, John Florian wrote:
>> > On Mon, 2016-10-03 at 12:07 -0700, Adam Williamson wrote:
>> > If we do not 'support' livecd-iso-to-disk any more, we no
Changed this subject to match the other one I changed, so if I'm doing
it wrong at least I'm consistent!
On Fri, Oct 7, 2016 at 9:22 AM, Kevin Fenzi wrote:
> On Fri, 7 Oct 2016 00:18:21 -0400
> Eric Griffith wrote:
>
>> I'm just thinking out loud here, but, given that rpm-ostree does not
>> use
On Oct 7, 2016 1:29 PM, "Frank Ch. Eigler" wrote:
>
>
> >> > [...] I always run dnf manually from the
> >> > command line, in a VT logged in as root. And I can run X while doing
> >> > this and I've never had a dnf update issue.
>
> To the extent that the problem is that dnf gets interrupted whe
On Oct 7, 2016 12:39 PM, "Adam Williamson"
wrote:
>
> On Mon, 2016-10-03 at 20:03 +, John Florian wrote:
> > On Mon, 2016-10-03 at 12:07 -0700, Adam Williamson wrote:
> > If we do not 'support' livecd-iso-to-disk any more, we no longer
> > support:
> >
> > 1) persistent storage (via overlays)
>> > [...] I always run dnf manually from the
>> > command line, in a VT logged in as root. And I can run X while doing
>> > this and I've never had a dnf update issue.
To the extent that the problem is that dnf gets interrupted when its
xterm dies, can that be worked around by dnf SIG_IGN'ing
On Fri, Oct 7, 2016 at 1:26 PM, Adam Williamson
wrote:
> On Tue, 2016-10-04 at 09:16 -0600, Chris Murphy wrote:
> The one concern I have is with Sugar on a Stick spin. Their
> installation instructions require livecd-iso-to-disk, because their
> media boots straight into SoaS, not Anaconda. But I
Hi folks! Sending this to devel@ as well as test@ as there's been some
relevant discussion there recently. We've been kicking around a couple
of issues lately:
1. Exactly what do we need to test and block on, in terms of writing
images to USB sticks?
2. 'Default boot and install' table was suppos
On Mon, 2016-10-03 at 20:03 +, John Florian wrote:
> On Mon, 2016-10-03 at 12:07 -0700, Adam Williamson wrote:
> If we do not 'support' livecd-iso-to-disk any more, we no longer
> support:
>
> 1) persistent storage (via overlays)
> 2) non-destructive write
>
>
> I've known for quite some tim
On Wed, 2016-10-05 at 21:51 +0200, Kevin Kofler wrote:
> I personally think that wiping all existing data on the USB stick is
> extremely user-unfriendly. A non-destructive method that just works would
> make everyone happy (both the majority that wants something that just works,
> no matter how
On Tue, 2016-10-04 at 09:16 -0600, Chris Murphy wrote:
The one concern I have is with Sugar on a Stick spin. Their
installation instructions require livecd-iso-to-disk, because their
media boots straight into SoaS, not Anaconda. But I have some ideas
about how to deal with that going forward to, ra
On Tue, 2016-10-04 at 11:12 +0200, Martin Kolman wrote:
>
> > There is currently no real way to use FMW on non-Fedora Linux
> > distributions that don't a) support Flatpak and b) have an
> > appropriate
> > Flatpak runtime for running FMW on (beyond compiling it yourself, I
> > guess).
>
> That s
On Friday, 07 October 2016 at 19:35, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Oct 07, 2016 at 06:43:10PM +0200, Dominik 'Rathann' Mierzejewski
> wrote:
> > Dear All,
> > I was made aware that EOL software with known security bugs that will
> > not be fixed upstream (due to EOL status) was revi
On Fri, 2016-10-07 at 21:11 +0200, Roberto Ragusa wrote:
> On 10/04/2016 08:10 PM, stan wrote:
>
> > I think I can confirm this advice. I always run dnf manually from the
> > command line, in a VT logged in as root. And I can run X while doing
> > this and I've never had a dnf update issue.
>
>
Hi Björn,
Let's swap :D I've got some packages to review, just pick some ones open
in Astronomy SIG tracker :)
https://bugzilla.redhat.com/show_bug.cgi?id=115
Greetings,
Christian
On 10/07/2016 09:18 PM, Björn Esser wrote:
> Hello,
>
> I have another three reviews to swap [1]. The first o
Hello,
I have another three reviews to swap [1]. The first one in the tree is
pretty brain-dead, the other two are a bit more advanced C-compiled
packages, but not too exhausting.
Any offers?
Cheers,
Björn
[1]
https://bugzilla.redhat.com/showdependencytree.cgi?id=1382810&hide_resolved=
Missing expected images:
Cloud_base qcow2 x86_64
Atomic qcow2 x86_64
Cloud_base raw-xz x86_64
Atomic raw-xz x86_64
Failed openQA tests: 70/102 (x86_64), 17/17 (i386), 1/2 (arm)
Old failures (same test failed in Rawhide-20161006.n.0):
ID: 39438 Test: x86_64 Everything-boot-iso install_defa
On 10/04/2016 08:10 PM, stan wrote:
> I think I can confirm this advice. I always run dnf manually from the
> command line, in a VT logged in as root. And I can run X while doing
> this and I've never had a dnf update issue.
The problem with this is that the VT doesn't have a long history,
so i
On Fri, 2016-10-07 at 17:35 +, Fedora compose checker wrote:
> No missing expected images.
>
> Failed openQA tests: 3/102 (x86_64), 1/17 (i386)
>
> Old failures (same test failed in 25-20161006.n.0):
>
> ID: 39572 Test: x86_64 Workstation-live-iso
> desktop_notifications_postinstall
> U
No missing expected images.
Failed openQA tests: 3/102 (x86_64), 1/17 (i386)
Old failures (same test failed in 25-20161006.n.0):
ID: 39572 Test: x86_64 Workstation-live-iso
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/39572
ID: 39577 Test: x86_64 Ato
On Fri, Oct 07, 2016 at 06:43:10PM +0200, Dominik 'Rathann' Mierzejewski wrote:
> Dear All,
> I was made aware that EOL software with known security bugs that will
> not be fixed upstream (due to EOL status) was reviewed and accepted into
> Fedora recently. This came on the back of the FPC ticket [
Hi,
On 07-10-16 18:58, Michael Catanzaro wrote:
On Fri, 2016-10-07 at 18:07 +0200, Hans de Goede wrote:
Suggested fix if you "shell out to passwd" in g-c-c, then why not
also do this in g-i-s presumable you can share the code then and
have less security sensitive code to worry about ? When you
This probably should have its own thread but I'm just changing the subject.
On Thu, Oct 6, 2016 at 10:18 PM, Eric Griffith wrote:
> 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 b
On Fri, 2016-10-07 at 18:07 +0200, Hans de Goede wrote:
> Suggested fix if you "shell out to passwd" in g-c-c, then why not
> also do this in g-i-s presumable you can share the code then and
> have less security sensitive code to worry about ? When you do
> make sure you run passwd as root (from g-
Dear All,
I was made aware that EOL software with known security bugs that will
not be fixed upstream (due to EOL status) was reviewed and accepted into
Fedora recently. This came on the back of the FPC ticket [1] asking to
make some changes in the Python Packaging Guidelines. I did go back and
re-
===
#fedora-meeting: FESCO (2016-10-07)
===
Meeting started by kalev at 16:00:29 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-10-07/fesco.2016-10-07-16.00.log.html
.
Meeting summary
---
On Fri, 2016-10-07 at 16:17 +0200, Tomas Mraz wrote:
> On Pá, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
> > Hi,
> >
> > So 2 devel cycles ago we had this whole discussion
> > about how forcing people to choose strong passwords in anaconda
> > was making live hard for testers / test-installs
Hi,
On 07-10-16 18:03, Adam Williamson wrote:
On Fri, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
Hi,
So 2 devel cycles ago we had this whole discussion
about how forcing people to choose strong passwords in anaconda
was making live hard for testers / test-installs and this
decision was re
Hi,
On 07-10-16 17:42, Michael Catanzaro wrote:
On Fri, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
So can we get this fixed please, or do we need to escalate
this all the way up to FESco again ?
Hi,
The status quo is that we are not in compliance with FESCo's policy
[1], which clearly a
On Fri, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
> Hi,
>
> So 2 devel cycles ago we had this whole discussion
> about how forcing people to choose strong passwords in anaconda
> was making live hard for testers / test-installs and this
> decision was reverted.
>
> So now here I'm doing a F
On Fri, Oct 7, 2016 at 9:42 AM, Michael Catanzaro wrote:
> But there is one more issue. FESCo's policy actually requires that only
> admin users (wheel users, including the initial user account) would be
> able to set weak passwords, and that unprivileged users should be
> blocked from doing so.
On Fri, Oct 7, 2016 at 8:17 AM, Tomas Mraz wrote:
> On Pá, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
>> Hi,
>>
>> So 2 devel cycles ago we had this whole discussion
>> about how forcing people to choose strong passwords in anaconda
>> was making live hard for testers / test-installs and this
On Fri, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
> So can we get this fixed please, or do we need to escalate
> this all the way up to FESco again ?
Hi,
The status quo is that we are not in compliance with FESCo's policy
[1], which clearly applies to all tools that change passwords and not
Thank you, Solomon for that info,
actually gutenprint maintainer is my colleague, but he is sick today. I'm
adding him into CC, so he's aware of it when he returns. ;)
2 Zdenek: Please, look at the whole thread here -
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/mes
On Fri, Oct 07, 2016 at 03:14:57PM -, David Kaspar wrote:
> Right now, I think only packages that depend on ghostscript-devel subpackage
> *might* be affected by this change. List of those packages:
> > ariamaestosa
> > ImageMagick
> > wfdb
Add gutenprint to that list. I don't expect the exi
On Fri, 7 Oct 2016 00:18:21 -0400
Eric Griffith wrote:
> 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
Hello folks,
ghostscript package has been rebased to version 9.20 across all current Fedora
releases. I am very well aware that we shouldn't do rebases for current
releases, to avoid stability problems. However, I have decided for this step in
order to fix 4 CVEs that arrived yesterday for ghos
On Thu, Oct 6, 2016 at 10:41 PM, Chris Murphy
wrote:
> 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
Hi,
On 07-10-16 16:17, Tomas Mraz wrote:
On Pá, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
Hi,
So 2 devel cycles ago we had this whole discussion
about how forcing people to choose strong passwords in anaconda
was making live hard for testers / test-installs and this
decision was reverted
On Fri, Oct 07, 2016 at 12:51:59AM +0300, Catalin wrote:
> 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
On Pá, 2016-10-07 at 15:56 +0200, Hans de Goede wrote:
> Hi,
>
> So 2 devel cycles ago we had this whole discussion
> about how forcing people to choose strong passwords in anaconda
> was making live hard for testers / test-installs and this
> decision was reverted.
>
> So now here I'm doing a F2
Hi,
So 2 devel cycles ago we had this whole discussion
about how forcing people to choose strong passwords in anaconda
was making live hard for testers / test-installs and this
decision was reverted.
So now here I'm doing a F25 Fedora ARM test install, end up
in the gnome-ified first-time-setup
Hi all,
the openssl will be rebased in Rawhide to 1.1.0 on Monday. There will
be also 1.0.2 compat package (compat-openssl10) so the dependencies are
not broken and Rawhide should be installable. Also things that do not
depend on openssl should be rebuildable without changes.
On the other hand du
Andrew Toskin wrote:
> 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?
The files
On Fri, Oct 07, 2016 at 08:35:52AM +0200, Pierre-Yves Chibon wrote:
> 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://fedo
Hi,
- Original Message -
> From: "mario riassetto"
> To: devel@lists.fedoraproject.org
> Sent: Tuesday, October 4, 2016 2:52:41 PM
> Subject: problems in Virtualbox
>
> I have noted a one problem in to the start of the image in Virtualbox.
> Virtualbox in fedora, not starting the virtual
On Thu, Oct 06, 2016 at 05:58:10PM +0300, Ponomarenko Andrey wrote:
>
>
> 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 sin
On 09/27/2016 04:47 AM, Felix Kaechele wrote:
I'm orphaning vdr-streamdev since I no longer use it. There shouldn't be any
open issues with this one.
Since apparently nobody is all that keen to take it and I'm still using
it, I'm willing to take it.
Thomas
_
On Thursday, 06 October 2016 at 18:58, Dridi Boukelmoune wrote:
> 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:
[...
58 matches
Mail list logo
