Miro,
Could you please also send a list of retired packages after you pull the
trigger?
Thx
Vít
Dne 01. 04. 19 v 23:17 Miro Hrončok napsal(a):
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know
> for sure
>
On Sun, Mar 17, 2019 at 9:54 PM Jerry James wrote:
> This appears to be caused by the clisp code incorrectly pairing
> register and volatile. Still, I find gcc's behavior surprising, which
> is why I filed https://bugzilla.redhat.com/show_bug.cgi?id=1689769.
> That may very well be closed as NOTA
Dear all,
You are kindly invited to the meeting:
Modularity Team (weekly) on 2019-04-02 from 15:00:00 to 16:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team
Docs](https://docs.pagure.o
For the record, the Change proposal I sent earlier without a title in
the subject is a follow-up to this proposal:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/PJVKI7DKPUL3MTT4GMKN5SMUGG5DGY6O/
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapo
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note:
A new Fedora Atomic Host update is available via an OSTree update:
Version: 29.20190401.0
Commit(x86_64): a39e99a72c80c9c4a8fce8a2092b2856f742a5c3ba5c9bedd59a9e76aa3e9924
Commit(aarch64):
5f9af9bc6c28829c93bbd0945d3e54205943b912e6fa2660f6fa3559a835494b
Commit(ppc64le):
cba5130d5355a5c087986de86
On 04. 03. 19 12:34, Pierre-Yves Chibon wrote:
On Sun, Mar 03, 2019 at 11:45:31AM +0100, Miro Hrončok wrote:
On 01. 03. 19 22:19, Ben Cotton wrote:
'''The CI system, the tests and the decision on which tests are used
to gate upon are out of scope for the present document.'''
This is both good
On Mon, 2019-02-11 at 11:56 -0500, Stephen Gallagher wrote:
> On Fri, Nov 16, 2018 at 7:18 PM Adam Williamson
> wrote:
> > On Thu, 2018-09-20 at 08:33 -0400, Stephen Gallagher wrote:
> > > There was a bug[1] filed recently that indicated that printing was
> > > broken on certain printers. As a res
On Mon, Apr 1, 2019 at 3:04 PM Adam Williamson
wrote:
> So, here's the specific text I propose. At Basic we would change this
> requirement:
>>
> To read only:
>
> "The boot menu for all release-blocking installer and live images
> should include an entry which causes both installation and the
>
On Tue, 2019-03-26 at 14:30 -0600, Chris Murphy wrote:
> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell,
Missing expected images:
Atomichost qcow2 x86_64
Atomichost raw-xz x86_64
Failed openQA tests: 6/144 (x86_64), 1/2 (arm)
ID: 375428 Test: x86_64 Workstation-live-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/375428
ID: 375451 Test: arm Minimal-raw_xz-raw.xz
install_a
https://fedoraproject.org/wiki/Changes/GatingRawhidePackages
Note that this was previously submitted as "Gating Rawhide - Single
package updates":
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SBB3DJO27HDDO6NAW54CLH2M62FEG622/
== Summary ==
We want to gate pac
OLD: Fedora-30-20190330.n.3
NEW: Fedora-30-20190401.n.0
= SUMMARY =
Added images:7
Dropped images: 2
Added packages: 17
Dropped packages:0
Upgraded packages: 128
Downgraded packages: 0
Size of added packages: 28.73 MiB
Size of dropped packages:0 B
Size of
Last month, we had a Modularity Hackfest in Boston. I wrote up a
hackfest report at the Community Blog[1] back then, which included
several open questions related to how to handle stream and profile
defaults. I'm reprinting them here on Fedora Devel for public input.
== Open Questions ==
We had so
On 03/31/2019 07:31 AM, Richard Shaw wrote:
> I'm working on building PySide2 for Fedora and have a problem with clang
> segfaulting only on armv7hf[1]...
>
> The source package has shiboken2, pyside2, and pyside2-tools in one big
> archive but I am building shiboken2 and pyside2-tools with GCC
OLD: Fedora-Rawhide-20190331.n.0
NEW: Fedora-Rawhide-20190401.n.0
= SUMMARY =
Added images:5
Dropped images: 2
Added packages: 9
Dropped packages:0
Upgraded packages: 48
Downgraded packages: 1
Size of added packages: 14.84 MiB
Size of dropped packages:0 B
Missing expected images:
Atomichost raw-xz x86_64
Atomichost qcow2 x86_64
Compose FAILS proposed Rawhide gating check!
8 of 47 required tests failed, 4 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not
tl;dr: There are no tickets scheduled for discussion. We will hold an
Open Floor meeting instead.
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fe
On 28/03/19 08:17 +, Tomasz Kłoczko wrote:
On Wed, 27 Mar 2019 at 21:27, Jonathan Wakely
wrote:
On 26/03/19 11:40 +, Tomasz Kłoczko wrote:
>On Tue, 26 Mar 2019 at 08:57, Jonathan Wakely
>wrote:
>[..]
>
>> >What does this 42 means in this case? It means that during whole gcc
build
>> >
On Sun, Mar 31, 2019 at 10:22 PM John Reiser wrote:
> On 3/31/19 7:31 AM, Richard Shaw wrote:
> > I'm working on building PySide2 for Fedora and have a problem with clang
> segfaulting only on armv7hf[1]...
>
> > [1]
> https://kojipkgs.fedoraproject.org//work/tasks/4670/33794670/build.log
>
> htt
Ben Cotton wrote on 2019/03/27 23:54:
Reminder: the Go/No-Go meeting for the Fedora 30 Beta release will be
held TOMORROW, 2019-03-28 at 17:00 UTC in #fedora-meeting-1. For more
information, see: https://fedoraproject.org/wiki/Go_No_Go_Meeting
View the meeting on Fedocal at:
https://apps.fedorap
Hi, I would like to change default sudoers file according to [1] proposed
patch is in a pull request [2]. Koji build is located here [3]. Planed
merge 14th of April 2019.
I would like to remove PS1 and PS2 variables from env_keep due to security
risks showed in bz [1].
[1] - https://bugzilla.redh
Dependency Checks
-
Also, I've tried to run some repoqueries to determine which of our packages are
leaf packages that could be retired eventually. However, running repoqueries on
f29 against the rawhide repos crashed dnf for some reason ... so I can't
automate that easily, yet.
On 01. 04. 19 10:55, Vít Ondruch wrote:
Dne 30. 03. 19 v 10:53 Miro Hrončok napsal(a):
On 29. 03. 19 22:25, Fabio Valentini wrote:
Dependency Checks
-
Also, I've tried to run some repoqueries to determine which of our
packages are
leaf packages that could be retired eventuall
On Mon, Apr 1, 2019, 10:55 Vít Ondruch wrote:
>
> Dne 30. 03. 19 v 10:53 Miro Hrončok napsal(a):
> > On 29. 03. 19 22:25, Fabio Valentini wrote:
> >
> >> Dependency Checks
> >> -
> >>
> >> Also, I've tried to run some repoqueries to determine which of our
> >> packages are
> >> le
Dne 30. 03. 19 v 10:53 Miro Hrončok napsal(a):
> On 29. 03. 19 22:25, Fabio Valentini wrote:
>
>> Dependency Checks
>> -
>>
>> Also, I've tried to run some repoqueries to determine which of our
>> packages are
>> leaf packages that could be retired eventually. However, running
>> r
26 matches
Mail list logo
