Hi,
On 19-09-18 02:09, Adam Williamson wrote:
On Tue, 2018-09-18 at 17:06 -0700, Adam Williamson wrote:
On Tue, 2018-09-18 at 18:57 -0400, Randy Barlow wrote:
On 9/18/18 3:23 PM, Chris Murphy wrote:
But is this bugginess worth a FE to try and get -58 onto the Beta?
Lots of users will install
Hi, folks! Just a quick mail to let everyone know where we are with F29
Beta.
We managed to throw together fixes for all the currently-accepted
blockers (thanks to the dnf team for help there), so an RC4 (aka Beta-
1.4) is currently composing. Compared to RC3 it contains a newer libdnf
with a fix
On Tue, 2018-09-18 at 18:58 -0600, Chris Murphy wrote:
>
> By the way, can we get some clarification as to the scope of the
> hidden grub menu change? I think it should be restricted to
> Workstation only. And not extend to anything else, including even
> Silverblue (yes it's a workstation variant
On Tue, Sep 18, 2018 at 6:55 PM, Chris Murphy wrote:
> On Tue, Sep 18, 2018 at 6:48 PM, Adam Williamson
> wrote:
>> On Tue, 2018-09-18 at 18:45 -0600, Chris Murphy wrote:
>>> On Tue, Sep 18, 2018 at 6:37 PM, Adam Williamson
>>> wrote:
>>> > On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
On Tue, 2018-09-18 at 18:55 -0600, Chris Murphy wrote:
>
> I'm not finding a criterion requiring either the key reveal feature to
> work; or for the failed boot detection to work. Seems like that might
> need a tweak.
Yeah, possibly. Not surprising there's no criterion *yet*, as it's a
new featur
On Tue, Sep 18, 2018 at 6:48 PM, Adam Williamson
wrote:
> On Tue, 2018-09-18 at 18:45 -0600, Chris Murphy wrote:
>> On Tue, Sep 18, 2018 at 6:37 PM, Adam Williamson
>> wrote:
>> > On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
>> > > Hi,
>> > >
>> > > On 18-09-18 17:28, Chris Murphy wrot
On Tue, 2018-09-18 at 18:45 -0600, Chris Murphy wrote:
> On Tue, Sep 18, 2018 at 6:37 PM, Adam Williamson
> wrote:
> > On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 18-09-18 17:28, Chris Murphy wrote:
> > > > On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewsk
On Tue, Sep 18, 2018 at 6:37 PM, Adam Williamson
wrote:
> On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 18-09-18 17:28, Chris Murphy wrote:
>> > On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
>> > wrote:
>> > > On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chri
On Tue, 2018-09-18 at 20:09 +0200, Hans de Goede wrote:
> Hi,
>
> On 18-09-18 17:28, Chris Murphy wrote:
> > On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
> > wrote:
> > > On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
> > > > On Tue, Sep 18, 2018 at 4:56 AM, Hans de
Hi,
The more I think about the bootloader writing to grubenv, the more I'm
not a fan. I'm really suspicious of even the general case of anything
doing (over)writes outside of the file system. Is block device writing
something all UEFI firmware support? Even with Secure Boot enabled?
Setting aside
On Tue, 2018-09-18 at 17:06 -0700, Adam Williamson wrote:
> On Tue, 2018-09-18 at 18:57 -0400, Randy Barlow wrote:
> > On 9/18/18 3:23 PM, Chris Murphy wrote:
> > > But is this bugginess worth a FE to try and get -58 onto the Beta?
> > > Lots of users will install the Beta and will not want to rein
On Tue, 2018-09-18 at 18:57 -0400, Randy Barlow wrote:
> On 9/18/18 3:23 PM, Chris Murphy wrote:
> > But is this bugginess worth a FE to try and get -58 onto the Beta?
> > Lots of users will install the Beta and will not want to reinstall.
> > Seems like suboptimal behavior.
>
> I think it's worth
Hi,
I am planning to orphan the coan package in a week or so unless someone
else is interested in taking on the package.
"Coan is a software engineering tool for analysing preprocessor-based
configurations of C or C++ source code. Its principal use is to simplify a
body of source code by eliminat
On 9/18/18 3:23 PM, Chris Murphy wrote:
> But is this bugginess worth a FE to try and get -58 onto the Beta?
> Lots of users will install the Beta and will not want to reinstall.
> Seems like suboptimal behavior.
I think it's worth a FE since this was one of the Fedora 29 changes. I
think it'd be
On Tue, Sep 18, 2018 at 12:09 PM, Hans de Goede wrote:
> Ok, I've managed to reproduce this in a classic BIOS boot using VM and
> then after updating grub2 to 2.02-58 and running grub2-mkinstall the
> problem went away. It looks like this somehow for broken in one specific
> grub2 build and then
OLD: Fedora-Rawhide-20180916.n.0
NEW: Fedora-Rawhide-20180917.n.1
= SUMMARY =
Added images:1
Dropped images: 1
Added packages: 11
Dropped packages:2
Upgraded packages: 160
Downgraded packages: 1
Size of added packages: 122.59 MiB
Size of dropped packages:7
Den tis 18 sep. 2018 kl 17:29 skrev Chris Murphy :
>
> On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
> >> On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede wrote:
> >> > Hi,
> >> >
> >> > On 18-09-18 01:12, Chr
Hi,
On 18-09-18 17:28, Chris Murphy wrote:
On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
wrote:
On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede wrote:
Hi,
On 18-09-18 01:12, Chris Murphy wrote:
I've got a Fedora
OLD: Fedora-29-20180917.n.0
NEW: Fedora-29-20180918.n.0
= SUMMARY =
Added images:3
Dropped images: 2
Added packages: 0
Dropped packages:32
Upgraded packages: 3
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:11.25 MiB
Size of
=
#fedora-meeting-3: Weekly Meeting of the Modularity Working Group
=
Meeting started by nils at 14:00:20 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meetin
On Tue, Sep 18, 2018 at 8:57 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
>> On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede wrote:
>> > Hi,
>> >
>> > On 18-09-18 01:12, Chris Murphy wrote:
>> >>
>> >> I've got a Fedora 29 Silverblue instal
On Tue, Sep 18, 2018 at 08:36:32AM -0600, Chris Murphy wrote:
> On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede wrote:
> > Hi,
> >
> > On 18-09-18 01:12, Chris Murphy wrote:
> >>
> >> I've got a Fedora 29 Silverblue installation in a VM.
What kind of VM is it?
Zbyszek
_
On Tue, Sep 18, 2018 at 4:56 AM, Hans de Goede wrote:
> Hi,
>
> On 18-09-18 01:12, Chris Murphy wrote:
>>
>> I've got a Fedora 29 Silverblue installation in a VM. First boot I see
>> the GRUB menu, and after that it's hidden. And I can't figure out how
>> to unhide it. Boot is failing before I get
On 09/17/2018 03:19 PM, nore...@fedoraproject.org wrote:
>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180917.0
> Commit(x86_64):
> 17b11d74047ded1264a57555a64ae6fc5d02a332c556679bfcf32864fc91f11e
> Commit(aarch64):
> 95cdc6d02ed7f3645bdd513b07b2c2db
On Tue, Sep 18, 2018 at 12:49 AM wrote:
>
>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180917.0
> Commit(x86_64):
17b11d74047ded1264a57555a64ae6fc5d02a332c556679bfcf32864fc91f11e
> Commit(aarch64):
95cdc6d02ed7f3645bdd513b07b2c2db9b04e91d8aae897fa88e3782
Hi,
On 18-09-18 01:12, Chris Murphy wrote:
I've got a Fedora 29 Silverblue installation in a VM. First boot I see
the GRUB menu, and after that it's hidden. And I can't figure out how
to unhide it. Boot is failing before I get multiuser login or ssh, so
extracting information to troubleshoot/bug
Exit codes with top bit set to 1 (IOW higher than 127) usually mean
unhandled signal. In your case 141 & 127 = 13 (or 141 - 128 = 13 if you
want) indicating the app got SIGPIPE and died on it.
This is not 100% reliable since you can deliberately exit your app with
>127 code but most apps do not do
On su, 16 syys 2018, Björn Persson wrote:
I have a Kerberos authentication problem.
On one computer running Fedora 27, I run kinit to authenticate to the
Fedora servers. After I enter my passphrase, kinit returns exit status
141. Then I run "fedpkg build", and get these error messages:
Kerberos
On Mon, Sep 17, 2018 at 12:20 PM Petr Šabata wrote:
> On Mon, Sep 03, 2018 at 03:35:50PM +0200, Adam Samalik wrote:
> > This is a summary of a recent thread [1].
> >
> > Traditional branches (such as "f29") have their EOL (end of life) encoded
> > in the name. But what about stream branches [2] (
On Wed, Sep 12, 2018 at 10:19 PM Matthew Miller
wrote:
> On Mon, Sep 03, 2018 at 03:35:50PM +0200, Adam Samalik wrote:
> > There would be a policy that a module can reach its EOL in the middle of
> a
> > Fedora release to prevent madness.
>
> Can or can't? I assume you mean "can't", because "can"
On Wed, Sep 12, 2018 at 10:54 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> On Tuesday, 11 September 2018 at 21:43, Richard Shaw wrote:
> [...]
> > This would take care of most of the complains about people using "git
> merge
> > master" across release branches (even though
On Tue, Sep 11, 2018 at 10:08 PM Richard Shaw wrote:
> On Tue, Sep 11, 2018 at 2:30 PM Adam Samalik wrote:
>
>> On Wed, Sep 5, 2018 at 3:43 PM Richard Shaw wrote:
>> As a packager, what is your experience with lifecycles of your packages?
>> Do you get a specific EOL date from the upstream? If
Hi,
I just update mongo-c-driver to 1.13.0
ABI/API is compatible
http://rpms.remirepo.net/compat_reports/libbson/1.12.0_to_1.13.0/compat_report.html
http://rpms.remirepo.net/compat_reports/libmongoc/1.12.0_to_1.13.0/compat_report.html
Warning: headers paths have changed
from /usr/include/lib
33 matches
Mail list logo
