<
eslerm[m]>
github set branches in mesa to stale
<
eslerm[m]>
I made a mistake with main, and then synced it with `ubuntu/mantic` branch
<
eslerm[m]>
I believe we need to reset mantic to asahi/mesa
<
eslerm[m]>
and cherry-pick tobias' packaging back on top
<
tobhe[m]>
or just dump the debian folder in there and start over with a new commit
<
tobhe[m]>
as long as we have each release tagged and available on gh I don't care too much about coherent git history
mkukri has joined #ubuntu-asahi
<
eslerm[m]>
tobhe: for migration to team ppa, I could copy all the mantic binaries over
<
tobhe[m]>
sure, that wouldn't hurt
<
tobhe[m]>
the part we haven't figured out is migrating existing installations
<
tobhe[m]>
without locking anyone out
<
tobhe[m]>
I don't think there is a nice way to move ppas
<
eslerm[m]>
what if we only migrated mantic's ppas?
<
eslerm[m]>
on the new ppa, we could make sure folks have 9 months of supoort to upgrade between releases
<
tobhe[m]>
but how?
<
eslerm[m]>
is there a package that configures apt ppas? or is it baked into the image?
<
tobhe[m]>
One thing I tried to avoid is having to keep two ppas in sync. I'd prefer if everyone used the same
<
tobhe[m]>
I don't think there is a package
<
tobhe[m]>
we can maybe call add-apt-repository from a maintainer script
<
tobhe[m]>
like have an ubuntu-asahi meta package update with a postinst script doing that
<
tobhe[m]>
but it feels pretty risky to me
<
john-cabaj[m]>
I’ve heard of the concept of a transitional package
<
tobhe[m]>
but that is when one package replaces another I think
<
eslerm[m]>
I'll ask a friend who has likely seen this ppa scenario resolved a few different ways