Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
linux-seblu-meta
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
archlinux
linux-seblu-meta
Commits
b5b500da
Commit
b5b500da
authored
6 years ago
by
Seblu
Browse files
Options
Downloads
Patches
Plain Diff
Bump to 2019.03.08
- Upgrade to linux 5.0.0
parent
2829f553
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#180
passed with stages
in 5 minutes and 52 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
PKGBUILD
+5
-4
5 additions, 4 deletions
PKGBUILD
with
5 additions
and
4 deletions
PKGBUILD
+
5
−
4
View file @
b5b500da
...
...
@@ -2,7 +2,7 @@
pkgbase
=
linux-seblu-meta
pkgname
=(
linux-seblu-meta linux-4.19-seblu-meta linux-4.9-seblu-meta
)
pkgver
=
2019.0
2.2
8
pkgver
=
2019.0
3.0
8
pkgrel
=
1
pkgdesc
=
'Meta package for Linux kernel cooked by Seblu'
arch
=(
'x86_64'
)
...
...
@@ -16,20 +16,21 @@ package_linux-seblu-meta() {
# kernel release are about every 2/3 months
depends
=(
'linux-firmware'
'linux-
4.2
0.
2
-seblu'
'linux-
5.
0.
0
-seblu'
)
optdepends
=(
'linux-4.20.2-seblu'
'linux-4.20.1-seblu'
'linux-4.20.0-seblu'
'linux-4.19.0-seblu'
)
conflicts
=(
'linux-4.18.20-seblu'
'linux-4.18.18-seblu'
'linux-4.18.16-seblu'
'linux-4.18.3-seblu'
'linux-4.18.1-seblu'
'linux-4.18.0-seblu'
)
conflicts
=(
'linux-4.17.14-seblu'
'linux-4.17.0-seblu'
'linux-4.16.0-seblu'
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment