Update from debian/unstable for apertis/v2022dev3
All threads resolved!
All threads resolved!
Merge request reports
Activity
- Resolved by Emanuele Aina
The automated merge failed here, so we're left with the unmerged
debian/unstable
branch. It should be manually merged to theapertis/v2022dev3
branch.I'd say that we should:
- rename the
debian/unstable
branch todebian/bookworm
as the package is now in testing and it makes tracking sources easier - locally do a manual merge of
proposed-updates/debian/unstable/6e7ece57
(which isdebian/bookworm
at the moment) withapertis/v2022dev3
and push the result here
@daissi do you need help?
- rename the
added 2 commits
added 34 commits
-
15dd62db...6e7ece57 - 33 commits from branch
apertis/v2022dev3
- e8aec25a - Merge branch 'apertis/v2022dev3' into proposed-updates/debian/unstable/6e7ece57
-
15dd62db...6e7ece57 - 33 commits from branch
added 1 commit
- af633fdf - Refresh the automatically detected licensing information
requested review from @em
assigned to @daissi
Please register or sign in to reply