On Wed, 01 Mar 2017 18:04:04 +
Russel Winder wrote:
> On Wed, 2017-03-01 at 17:58 +, Russel Winder wrote:
> > On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
> > > […]
> > >
> > > This should work:
> > >
> > > koji download-build --quiet --arch=$(uname -m) $(koji
> > > latest-bu
if there should be a simple, standard way of
>> being able to install the last released kernel, perhaps a package last-
>> release-kernel or something.
>>
>> The problem for me is that the release kernel only ever seems to be in
>> Rawhide for one day, and if I miss up
install the last released kernel, perhaps a package last-
> release-kernel or something.
>
> The problem for me is that the release kernel only ever seems to be in
> Rawhide for one day, and if I miss updating on that day, I have missed
> capturing that kernel – it just happened with 4
On Wed, 2017-03-01 at 17:58 +, Russel Winder wrote:
> On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
> > […]
> >
> > This should work:
> >
> > koji download-build --quiet --arch=$(uname -m) $(koji latest-build
> > --quiet f25 kernel | awk '{print $1}')
I guess the import point here i
On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
> […]
>
> This should work:
>
> koji download-build --quiet --arch=$(uname -m) $(koji latest-build
> --quiet f25 kernel | awk '{print $1}')
>
> but it downloads all the rpms of the kernel package so in the end it
> might be slower than the
On Wed, 1 Mar 2017 13:24:29 +
Peter Robinson wrote:
> On Wed, Mar 1, 2017 at 12:23 PM, Russel Winder
> wrote:
> > On Wed, 2017-03-01 at 12:10 +, Russel Winder wrote:
> >> On Wed, 2017-03-01 at 11:07 +, Peter Robinson wrote:
> >> >
> >>
> >> […]
> >> > You can always just pull
On Wed, 2017-03-01 at 13:24 +, Peter Robinson wrote:
> […]
> It depends, sometimes they might still be in the signing queue,
> sometimes they might have been replaced before they were signed but I
> suspect you're using a f26 kernel on a different release which means
> it'll be signed with a di
On 01.03.2017 13:30, Russel Winder wrote:
On Wed, 2017-03-01 at 13:17 +0100, Sandro Mani wrote:
[…]
Don't know if this helps, but I have
exclude=kernel*
in dnf.conf and use a script like
ver=$(( $(cat /etc/redhat-release | awk '{print $3}') - 1 ))
dnf -y --disablerepo=* --releasever=$ver --
On Wed, Mar 1, 2017 at 12:23 PM, Russel Winder wrote:
> On Wed, 2017-03-01 at 12:10 +, Russel Winder wrote:
>> On Wed, 2017-03-01 at 11:07 +, Peter Robinson wrote:
>> >
>>
>> […]
>> > You can always just pull it from koji either via the website or
>> > cli.
>> >
>> > For cli you can use "k
On Wed, 2017-03-01 at 13:17 +0100, Sandro Mani wrote:
>
[…]
> Don't know if this helps, but I have
>
> exclude=kernel*
>
> in dnf.conf and use a script like
>
> ver=$(( $(cat /etc/redhat-release | awk '{print $3}') - 1 ))
> dnf -y --disablerepo=* --releasever=$ver --enablerepo=updates*
> --dis
On Wed, 2017-03-01 at 12:10 +, Russel Winder wrote:
> On Wed, 2017-03-01 at 11:07 +, Peter Robinson wrote:
> >
>
> […]
> > You can always just pull it from koji either via the website or
> > cli.
> >
> > For cli you can use "koji download-build --arch=x86_64 kernel-
> > 4.10.0-
> > 1.fc2
On 01.03.2017 10:07, Russel Winder wrote:
I appreciate that Rawhide always has the latest kernel snapshot as the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released
On Wed, 2017-03-01 at 11:07 +, Peter Robinson wrote:
>
[…]
> You can always just pull it from koji either via the website or cli.
>
> For cli you can use "koji download-build --arch=x86_64 kernel-4.10.0-
> 1.fc26"
>
> For web grab what ever version you want from
> https://koji.fedoraproject.
install the last released kernel, perhaps a package last-
> release-kernel or something.
>
> The problem for me is that the release kernel only ever seems to be in
> Rawhide for one day, and if I miss updating on that day, I have missed
> capturing that kernel – it just happened with 4
I appreciate that Rawhide always has the latest kernel snapshot as the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released kernel, perhaps a package last-
release-kernel or
15 matches
Mail list logo
