On 09/22/2017 06:47 PM, David Muse wrote:
I have a package with many subpackages. Some of the subpackages depend
on libraries provided by other subpackages.
When downloading with yum/dnf, the rpm's know what they depend on, and
the dnf/yum can figure out what to install to satisfy the depende
Hello list,
I have a package with many subpackages. Some of the subpackages depend
on libraries provided by other subpackages.
When downloading with yum/dnf, the rpm's know what they depend on, and
the dnf/yum can figure out what to install to satisfy the dependencies.
No problem there.
B
Petr Pisar wrote:
> In rawhide, if you want a longer time isolation, you ask relengs for
> a sige tag, you do all builds there without affecting others and then
> you ask relengs to merge the builds back to rawhide. Of course this has
> same races and one needs to reaply all rawhide changes into th
Missing expected images:
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 18/126 (x86_64), 1/18 (i386), 1/2 (arm)
ID: 146228 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/146228
ID: 146234 Test: x86
Missing expected images:
Server dvd i386
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 17/128 (x86_64), 1/2 (arm)
New failures (same test did not fail in Rawhide-20170921.n.1):
ID: 145838 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://o
Missing expected images:
Workstation live i386
Server boot i386
Kde live i386
Passed openQA tests: 2/128 (x86_64)
Installed system changes in test x86_64 Atomic-dvd_ostree-iso install_default:
System load changed from 0.05 to 0.33
Previous test data: https://openqa.fedoraproject.org/tests/1
For what it's worth: I just installed the 4.13.2 kernel from the
kernel-stabilization repo, and the nvidia akmod module (from negativo17
repo) failed to build (as expected). But after rebooting with the new
kernel, the system uses the fallback to nouveau correctly - without any
manual intervention.
On Fri, Sep 22, 2017 at 7:46 PM, wrote:
> Oh boy. :)
>
> Does anyone know if the fallback is working properly? Because if so, then
> everyone is happy and we don't need to be having this discussion. Sounds
> like there's a good chance that's the case. (I don't have an nvidia card to
> test myself
According to the schedule [1], Fedora 27 Candidate Beta-1.2 is now
available for testing. Please help us complete all the validation
testing! For more information on release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the cu
2017-09-22 20:46 GMT+02:00 :
> Oh boy. :)
>
> Does anyone know if the fallback is working properly? Because if so, then
Just restoring the fact here, because despite the fallback idea is
hans/WG the implementation is "RPM Fusion Community" original works.
(1)
So yet as soon as you are using "RPM F
On Fri, Sep 22, 2017 at 3:25 PM, Michael Catanzaro
wrote:
> On Fri, Sep 22, 2017 at 2:21 PM, Chris Adams wrote:
>>
>> On what grounds? There is nothing in the Fedora guidelines that makes
>> package maintainers beholden to third-party (by definition, not part of
>> Fedora) repos. There's nothin
Once upon a time, Michael Catanzaro said:
> OK, I'll bite. The grounds are that FESCo has granted the WG full
> control over the Workstation product
Where is it documented that "full control" includes non-Fedora content?
I would have assumed (unless otherwise stated) that anything that's part
of
On Fri, Sep 22, 2017 at 2:21 PM, Chris Adams wrote:
On what grounds? There is nothing in the Fedora guidelines that makes
package maintainers beholden to third-party (by definition, not part
of
Fedora) repos. There's nothing for FESCo to vote on, unless you are
going to propose that change.
Once upon a time, mcatanz...@gnome.org said:
> If the fallback is not working, then FESCo will probably need to
> decide indeed.
On what grounds? There is nothing in the Fedora guidelines that makes
package maintainers beholden to third-party (by definition, not part of
Fedora) repos. There's n
Oh boy. :)
Does anyone know if the fallback is working properly? Because if so,
then everyone is happy and we don't need to be having this discussion.
Sounds like there's a good chance that's the case. (I don't have an
nvidia card to test myself.)
If the fallback is not working, then FESCo w
On Fri, Sep 22, 2017 at 2:20 PM, Laura Abbott wrote:
> On 09/22/2017 09:43 AM, mcatanz...@gnome.org wrote:
>>
>> On Fri, Sep 22, 2017 at 8:41 AM, James Hogarth
>> wrote:
>>>
>>> Pretty sure the last testing I did with the details form Hans's blog[0]
>>> the behaviour was that if the nvidia driver
On 09/22/2017 09:43 AM, mcatanz...@gnome.org wrote:
On Fri, Sep 22, 2017 at 8:41 AM, James Hogarth
wrote:
Pretty sure the last testing I did with the details form Hans's
blog[0] the behaviour was that if the nvidia driver failed then the
nouveau driver was a fallback (rather than the older ins
On 12/09/17 02:47 PM, Laura Abbott wrote:
> On 09/05/2017 09:41 AM, Laura Abbott wrote:
>> Hi,
>>
>> Kernel 4.13 was released this past weekend. This kernel has been
>> built for rawhide and is building for F27 as well. We will be
>> following the same upgrade procedure as in the past. F25 and F26
Once upon a time, mcatanz...@gnome.org said:
> But if Negativo users start complaining that their computers don't
> boot anymore, then we'll definitely need to stop doing major kernel
> updates ("taking the entire distro hostage" I guess) as the Negativo
> support is important for product strategy
On Fri, Sep 22, 2017 at 1:06 PM, Stephen John Smoogen wrote:
> On 22 September 2017 at 12:43, wrote:
>> But if Negativo users start complaining that their computers don't boot
>> anymore, then we'll definitely need to stop doing major kernel updates
>> ("taking the entire distro hostage" I guess
On Fri, Sep 22, 2017 at 11:43:21AM -0500, mcatanz...@gnome.org wrote:
> On Fri, Sep 22, 2017 at 8:41 AM, James Hogarth
> wrote:
> > Pretty sure the last testing I did with the details form Hans's blog[0]
> > the behaviour was that if the nvidia driver failed then the nouveau
> > driver was a fallb
On 22 September 2017 at 12:43, wrote:
> On Fri, Sep 22, 2017 at 8:41 AM, James Hogarth
> wrote:
>>
>> Pretty sure the last testing I did with the details form Hans's blog[0]
>> the behaviour was that if the nvidia driver failed then the nouveau driver
>> was a fallback (rather than the older ins
On Fri, Sep 22, 2017 at 8:41 AM, James Hogarth
wrote:
Pretty sure the last testing I did with the details form Hans's
blog[0] the behaviour was that if the nvidia driver failed then the
nouveau driver was a fallback (rather than the older instructions
that totally blacklisted it leaving no GPU
On 22 September 2017 at 15:02, James Hogarth
wrote:
>
>
> On 22 September 2017 at 14:50, Gary Gatling wrote:
>
>>
>>
>> On Fri, Sep 22, 2017 at 9:41 AM, James Hogarth
>> wrote:
>>
>>>
>>> Pretty sure the last testing I did with the details form Hans's blog[0]
>>> the behaviour was that if
On 22 September 2017 at 14:50, Gary Gatling wrote:
>
>
> On Fri, Sep 22, 2017 at 9:41 AM, James Hogarth
> wrote:
>
>>
>>>
>> Pretty sure the last testing I did with the details form Hans's blog[0]
>> the behaviour was that if the nvidia driver failed then the nouveau driver
>> was a fallback (ra
On Fri, Sep 22, 2017 at 9:41 AM, James Hogarth
wrote:
>
>>
> Pretty sure the last testing I did with the details form Hans's blog[0]
> the behaviour was that if the nvidia driver failed then the nouveau driver
> was a fallback (rather than the older instructions that totally blacklisted
> it leav
On 22 September 2017 at 14:34, Matthew Miller
wrote:
> On Fri, Sep 22, 2017 at 09:22:08AM -0400, Josh Boyer wrote:
> > > repo is supported and it needs to not break. We've been super super
> lenient
> >
> > That's a completely untenable position. There is only one kernel for
> > all the Editions
On Fri, Sep 22, 2017 at 09:22:08AM -0400, Josh Boyer wrote:
> > repo is supported and it needs to not break. We've been super super lenient
>
> That's a completely untenable position. There is only one kernel for
> all the Editions. There will be times where the kernel needs to be
> updated to f
On Fri, Sep 22, 2017 at 9:05 AM, Michael Catanzaro
wrote:
> On Fri, Sep 22, 2017 at 6:54 AM, Josh Boyer
> wrote:
>>
>> Absolutely not.
>>
>> josh
>
>
> If it breaks the Negativo repo, then yes it is. The Nvidia driver from that
No, it's really not.
> repo is supported and it needs to not break.
On Fri, Sep 22, 2017 at 6:54 AM, Josh Boyer
wrote:
Absolutely not.
josh
If it breaks the Negativo repo, then yes it is. The Nvidia driver from
that repo is supported and it needs to not break. We've been super
super lenient with allowing kernel updates in the Workstation product,
since it
Hi Everybody,
I'll push builds with updated SELinux security policy into Rawhide soon,
this build will remove unnecessary dac_override capability in domains
where it's not needed. Because of this change, we're able to remove a
lot of unnecessary rules allowing dac_override, which means tighten
On 09/22/2017 01:07 PM, Petr Pisar wrote:
On 2017-09-22, Ralf Corsepius wrote:
How to build a sub tree of packages in fc27, when the root of this tree
changed SONAME?
In rawhide, if you want a longer time isolation, you ask relengs for
a sige tag, you do all builds there without affecting oth
On Fri, Sep 22, 2017 at 4:42 AM, James Hogarth wrote:
>
>
> On 15 September 2017 at 11:00, James Hogarth
> wrote:
>>
>>
>>
>> On 13 September 2017 at 01:39, James Hogarth
>> wrote:
>>>
>>>
>>>
>>> On 12 Sep 2017 10:49 pm, "Laura Abbott" wrote:
>>>
>>> On 09/05/2017 09:41 AM, Laura Abbott wrote:
I accidentally build perl-libwww-perl-6.27-1.fc28 that cannot be
installed because of broken dependencies. There is already
perl-libwww-perl-6.27-2.fc28 that fixes, but it still has not yet get
into f28-build target.
Hopefully next compose will resolve it because it looks like after
introducing th
On 2017-09-22, Ralf Corsepius wrote:
> How to build a sub tree of packages in fc27, when the root of this tree
> changed SONAME?
>
In rawhide, if you want a longer time isolation, you ask relengs for
a sige tag, you do all builds there without affecting others and then
you ask relengs to merge th
On 15 September 2017 at 11:00, James Hogarth
wrote:
>
>
> On 13 September 2017 at 01:39, James Hogarth
> wrote:
>
>>
>>
>> On 12 Sep 2017 10:49 pm, "Laura Abbott" wrote:
>>
>> On 09/05/2017 09:41 AM, Laura Abbott wrote:
>>
>>> Hi,
>>>
>>> Kernel 4.13 was released this past weekend. This kernel
On 22/09/17 08:50, Ralf Corsepius wrote:
How to build a sub tree of packages in fc27, when the root of this tree
changed SONAME?
Well it's painful - you have to build each one then add an override for
it and wait for that to appear and then move on to the next one etc...
Tom
--
Tom Hughes
On 09/22/2017 09:32 AM, Tom Hughes wrote:
On 22/09/17 08:03, Ralf Corsepius wrote:
I am trying to build a chain of packages in a build override?
I.e. a series of packages: A->B->C
I set up a build override for A, and B built successfully. Now, I
would have expect building C to pickup B from
On 22/09/17 08:03, Ralf Corsepius wrote:
I am trying to build a chain of packages in a build override?
I.e. a series of packages: A->B->C
I set up a build override for A, and B built successfully. Now, I would
have expect building C to pickup B from the A-override.
You seem to be confused a
On 22 Sep 2017 4:46 am, "Luya Tshimbalanga" wrote:
On 21/09/17 08:02 AM, James Hogarth wrote:
On 21 September 2017 at 07:17, Luya Tshimbalanga
wrote:
> Sparkleshare package is currently behind upstream which just reach
> 2.0[1][2]
> The maintainer was contacted for updating the package with
Hi,
I am trying to build a chain of packages in a build override?
I.e. a series of packages: A->B->C
I set up a build override for A, and B built successfully. Now, I would
have expect building C to pickup B from the A-override.
This does not seem to apply. C fails to build, apparently becau
41 matches
Mail list logo
