Sorry, I don't understand. What's the matter?
On Thu, May 28, 2026 at 8:51 PM Jérémy Lal <[email protected]> wrote: > > > Le jeu. 28 mai 2026 à 19:15, masume dehghan <[email protected]> a > écrit : > >> Thank you for the reply. >> >> I packaged gaphor which is a GNOME Circle app. >> >> https://salsa.debian.org/gnome-team/gaphor >> >> Of course I sent another email with my primary email address ( >> [email protected]) to find a sponsor for it. >> >> On Fri, May 22, 2026 at 1:56 AM Jeremy Bícha <[email protected]> wrote: >> >>> On Thu, May 21, 2026 at 3:12 PM masume dehghan >>> <[email protected]> wrote: >>> > Can I add my packages to the GNOME group so they get updated faster? >>> >>> Yes. Welcome! Thank you for helping to make Debian better! I have >>> added you to the Salsa team. I think that gives you enough permission >>> to move your projects with Settings > General > Transfer project. >>> >>> GNOME Core and GNOME Circle apps and libraries should be in the >>> regular Debian GNOME team, while other apps and libraries for GNOME >>> are handled in the Extras subteam. >>> >>> Please take time to read through https://wiki.debian.org/Gnome/Git . >>> In particular, we use a DEP-14 style layout with git-buildpackage. >>> That means the default branch is debian/latest and there is also an >>> upstream/latest branch. >>> >>> Converting the upstream branch is a little complicated. Basically it >>> requires first renaming upstream to a temporary branch and then >>> renaming the temporary branch to upstream/latest since git won't allow >>> branches named upstream & upstream/latest to exist simultaneously. >>> This also means that it is probably easiest for people who have a >>> local copy of these repos to just do a new git clone afterwards. Let >>> me know if you want me to rename the branches for you after the repos >>> are moved to the Debian GNOME team on Salsa. >>> >> > See also dep-14-convert-git-branch-names > in devscripts > > > >> >>> We also use the full upstream git history so there will be one extra >>> step when importing new upstream versions: git fetch --all (or >>> sometimes also git fetch --all --tags ) assuming you have the >>> upstreamvcs git remote. One way to get that remote is with gbp clone >>> --add-upstream-vcs when doing the initial git clone. >>> >>> Thank you, >>> Jeremy Bícha >>> >>
