Re: Salsa repository request
Le 27/12/2021 à 20:11, Pierre-Elliott Bécue a écrit : Thomas Perret wrote on 27/12/2021 at 15:39:31+0100: Le 26/12/2021 à 22:21, Pierre-Elliott Bécue a écrit : Done. Happy hacking! Hi, Thanks a lot but it looks like I can't push to the repository (or more precisely, create a branch). When I push to the repository, I get: I'm sorry, I certainly was tired when I added you as a member of the project. It's fixed. Everything works as expected. Perfect! Thanks again
Re: Salsa repository request
Thomas Perret wrote on 27/12/2021 at 15:39:31+0100: > Le 26/12/2021 à 22:21, Pierre-Elliott Bécue a écrit : >> >> Done. >> Happy hacking! >> > > Hi, > > Thanks a lot but it looks like I can't push to the repository (or more > precisely, create a branch). When I push to the repository, I get: I'm sorry, I certainly was tired when I added you as a member of the project. It's fixed. -- PEB signature.asc Description: PGP signature
Re: Salsa repository request
Le 26/12/2021 à 22:21, Pierre-Elliott Bécue a écrit : Done. Happy hacking! Hi, Thanks a lot but it looks like I can't push to the repository (or more precisely, create a branch). When I push to the repository, I get: Enumerating objects: 123, done. Counting objects: 100% (123/123), done. Delta compression using up to 4 threads Compressing objects: 100% (108/108), done. Writing objects: 100% (123/123), 76.84 KiB | 76.84 MiB/s, done. Total 123 (delta 10), reused 113 (delta 7), pack-reused 0 remote: Resolving deltas: 100% (10/10), done. remote: GitLab: remote: A default branch (e.g. master) does not yet exist for debian/pass-audit remote: Ask a project Owner or Maintainer to create a default branch: remote: remote: https://salsa.debian.org/debian/pass-audit/-/project_members remote: To salsa.debian.org:debian/pass-audit.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'salsa.debian.org:debian/pass-audit.git' It seems having Developer rights on gitlab repository doesn't give enough permissions to manage the repository. Could you create the the needed branches (master, upstream, pristine-tar) Or (better), give me the Maintainer permissions on this repo. Note that for the other source package I maintain on global Debian namespace (gfsecret[0]), I have the Maintainer permissions. Cheers, Thomas [0]: https://salsa.debian.org/debian/gfsecret
Re: Salsa repository request
Thomas Perret wrote on 26/12/2021 at 15:28:15+0100: > [[PGP Signed Part:No public key for 69299C8ED390E51C created at > 2021-12-26T15:28:16+0100 using RSA]] > Dear mentors, > > Could someone create a "pass-audit"[0] project on Salsa under the > debian global namespace and grant me (username: moht) write access? > > From the official website[1]: > pass audit is a password-store[2] extension for auditing your password > repository. Passwords will be checked against the Python > implementation of Dropbox' zxcvbn algorithm and Troy Hunt's Have I > Been Pwned Service. It supports safe breached password detection from > haveibeenpwned.com using a K-anonymity method. Using this method, you > do not need to (fully) trust the server that stores the breached > password. > > Thanks > > Best, > Thomas > > > [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002618 > [1]: https://github.com/roddhjav/pass-audit > [2]: https://tracker.debian.org/pkg/password-store Done. Happy hacking! -- PEB signature.asc Description: PGP signature
Salsa repository request
Dear mentors, Could someone create a "pass-audit"[0] project on Salsa under the debian global namespace and grant me (username: moht) write access? From the official website[1]: pass audit is a password-store[2] extension for auditing your password repository. Passwords will be checked against the Python implementation of Dropbox' zxcvbn algorithm and Troy Hunt's Have I Been Pwned Service. It supports safe breached password detection from haveibeenpwned.com using a K-anonymity method. Using this method, you do not need to (fully) trust the server that stores the breached password. Thanks Best, Thomas [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002618 [1]: https://github.com/roddhjav/pass-audit [2]: https://tracker.debian.org/pkg/password-store OpenPGP_signature Description: OpenPGP digital signature
Re: Salsa repository request, granted
On Tue, Sep 21, 2021 at 11:00:36PM +0200, Lorenzo wrote: > Dear Mentors, > > can someone please give me access to > > https://salsa.debian.org/debian/opensysusers Done > The package is orphaned - I'm not listed as maintainer - but I've > done and plan to keep doing some occasional work on it in order to keep > it usable. > My account is Lorenzo.ru.g-guest Now developer for that repository Groeten Geert Stappers DD -- Silence is hard to parse
Salsa repository request
Dear Mentors, can someone please give me access to https://salsa.debian.org/debian/opensysusers The package is orphaned - I'm not listed as maintainer - but I've done and plan to keep doing some occasional work on it in order to keep it usable. My account is Lorenzo.ru.g-guest Regards, Lorenzo
Re: Salsa repository request
On Sun, 7 Feb 2021 21:03:11 +0100 Tobias Frost wrote: > Am Sat, Feb 06, 2021 at 06:39:22AM +0100 schrieb Lorenzo: > > > > Hi, > > > > Can someone please give me access to > > > > https://salsa.debian.org/debian/dh-sysuser > > > > I'm the maintainer, but I'm not allowed to push. > > My account is Lorenzo.ru.g-guest > > ✔ > > > Regards, > > Lorenzo > > Thank you!
Re: Salsa repository request
Am Sat, Feb 06, 2021 at 06:39:22AM +0100 schrieb Lorenzo: > > Hi, > > Can someone please give me access to > > https://salsa.debian.org/debian/dh-sysuser > > I'm the maintainer, but I'm not allowed to push. > My account is Lorenzo.ru.g-guest ✔ > Regards, > Lorenzo >
Salsa repository request
Hi, Can someone please give me access to https://salsa.debian.org/debian/dh-sysuser I'm the maintainer, but I'm not allowed to push. My account is Lorenzo.ru.g-guest Regards, Lorenzo
Re: Salsa repository request
Le 18/08/2020 à 23:54, Kyle Robbertze a écrit : > Hi > > Created and added you as maintainer > > https://salsa.debian.org/debian/aqemu > > Cheers > Thanks :) -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F
Re: Salsa repository request
Hi On 2020/08/18 23:23, Alexis Murzeau wrote: > Dear mentors, > > The aqemu package is now orphaned (#955988, [1]). > > I would like to put it under the "debian" group on Salsa so that > future QA work can be made collaboratively by anyone. > > > => Thus, could someone create an empty "aqemu" project in the "debian" group > on Salsa and grant me (@amurzeau) write access ? (I'm not a DD nor a DM) > Created and added you as maintainer https://salsa.debian.org/debian/aqemu Cheers -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄ https://wiki.debian.org/KyleRobbertze
Salsa repository request
Dear mentors, The aqemu package is now orphaned (#955988, [1]). I would like to put it under the "debian" group on Salsa so that future QA work can be made collaboratively by anyone. => Thus, could someone create an empty "aqemu" project in the "debian" group on Salsa and grant me (@amurzeau) write access ? (I'm not a DD nor a DM) I will populate it then. Thanks :) Note: the package could just be removed from Debian instead, but its popcon is not that low I think (721 [2]) and upstream is now a bit active [3]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955988 [2] https://qa.debian.org/popcon.php?package=aqemu [3] https://github.com/tobimensch/aqemu -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F signature.asc Description: OpenPGP digital signature
Re: salsa repository request for davfs2
Hi Andrius, Thanks for explanations, I will figure out later. Woodrow On Thu, Jun 18, 2020 at 6:06 PM wrote: > Hi Woodrow, > > On 2020-06-18 13:02, Woodrow Shen wrote: > > I'm doing NMU for davfs2 and would like to access > > https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. > > Can someone help me? Thanks. > > > > My username on salsa already aligned to "woodrowshen" as NM. > > To submit a PR you do not need the access to the repository in question. > Instead, you can fork it to your namespace, create a branch and then > submit a PR to the original repository. AFAIK, opening a PR does not > require write permission. > > HTH, > Andrius > >
Re: salsa repository request for davfs2
Hi Woodrow, On 2020-06-18 13:02, Woodrow Shen wrote: > I'm doing NMU for davfs2 and would like to access > https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. > Can someone help me? Thanks. > > My username on salsa already aligned to "woodrowshen" as NM. To submit a PR you do not need the access to the repository in question. Instead, you can fork it to your namespace, create a branch and then submit a PR to the original repository. AFAIK, opening a PR does not require write permission. HTH, Andrius
salsa repository request for davfs2
Hi Mentors, I'm doing NMU for davfs2 and would like to access https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. Can someone help me? Thanks. My username on salsa already aligned to "woodrowshen" as NM. Woodrow
Re: Salsa repository request
On 3/15/20 7:14 PM, Kyle Robbertze wrote: > Hi, > > On 2020/03/15 03:13, Lorenzo wrote: >> Dear mentors, >> >> I'm maintaining runit and dh-runit, >> can someone grant me write access to >> >> https://salsa.debian.org/debian/runit >> and >> https://salsa.debian.org/debian/dh-runit > Added to both > > Cheers > Kyle > Thank you Lorenzo
Re: Salsa repository request
Hi, On 2020/03/15 03:13, Lorenzo wrote: > Dear mentors, > > I'm maintaining runit and dh-runit, > can someone grant me write access to > > https://salsa.debian.org/debian/runit > and > https://salsa.debian.org/debian/dh-runit Added to both Cheers Kyle -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄ https://wiki.debian.org/KyleRobbertze
Salsa repository request
Dear mentors, I'm maintaining runit and dh-runit, can someone grant me write access to https://salsa.debian.org/debian/runit and https://salsa.debian.org/debian/dh-runit my Salsa account is Lorenzo.ru.g-guest Best Regards, Lorenzo Puliti
Salsa repository request
Dear mentors, I am packaged software for XTRX SDR support. Now, I guess, I need the repositories in the "debian" group to specify proper VCS URLs in a source package info. The software is also fit for the Debian Hamradio Maintainers group. The package names are: liblms7compact[1] libusb3380[2] libxtrxll[3] libxtrxdsp[4] libxtrx[5] xtrx-dkms[6] Please create the repositories and give me access or tell me how the packaging process should go on this step. My username in Salsa is diospyros-guest. Many thanks. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945150 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945152 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945153 4. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945154 5. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945155 6. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945156
Salsa repository request
Hello, I am packaged a bunch of libraries and drivers and I probably need repos for all of them with access. I guess group should be "debian" or "debian-hamradio-team" since all of packages are made for radio equipment (SDR) support. Names of requested repos: liblms7compact[1] libusb3380[2] libxtrxll[3]libxtrxdsp[4] libxtrx[5] xtrx-dkms[6] My username in Salsa is diospyros-guest. Please let me know if I incorrectly understand the uploading process. Thank you. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945150 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945152 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945153 4. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945154 5. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945155 6. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945156
Re: Salsa repository request
Hi, On 2020/01/06 18:58, Thomas Perret wrote: > Dear mentors, > > Could someone create a "gfsecret"[0] project on Salsa under the "debian" > namespace and grant me (moht-guest) write access? Created and granted you maintainer access. Let me know if you need anything else done. Cheers Kyle -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄ https://wiki.debian.org/KyleRobbertze
Salsa repository request
Dear mentors, Could someone create a "gfsecret"[0] project on Salsa under the "debian" namespace and grant me (moht-guest) write access? From the official website[1]: Gfsecret is a set of tools to facilitate secret sharing according to the Adi Shamir’s secret sharing scheme. Thanks Best, Thomas [0]: ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948038 [1]: https://incenp.org/dvlpt/gfsecret.html signature.asc Description: OpenPGP digital signature
Re: Salsa repository request (dbab)
Hi, On Wed, Dec 18, 2019 at 08:34:55PM -0500, Tong Sun wrote: > So, could somebody please create it for me and give me, suntong-guest, > maintenance access? Done – shout if I messed up ☺ Happy package management days David Kalnischkies signature.asc Description: PGP signature
Salsa repository request (dbab)
Hi, I am currently preparing a new version for the 'dbab' packages [0]. I would like to create a packaging repository for it in the Debian group on Salsa this time [1], but I don't have the necessary permissions on Salsa to create it myself. So, could somebody please create it for me and give me, suntong-guest, maintenance access? Thank you! Best regards, tong [0] https://tracker.debian.org/pkg/dbab [1] https://salsa.debian.org/debian
Re: Salsa repository request
On 11/16/19 8:39 PM, Georg Faerber wrote: > On 19-11-16 19:00:26, Fabian Wolff wrote: >> It's 'wolff-guest'. (And please CC me in your replies, as I'm not >> subscribed to debian-mentors.) > > I've created the repo, and gave you Maintainer access. Let me know if > that's not sufficient. It should be sufficient - I just pushed everything, and it worked without any problems. Thanks again for your help!
Re: Salsa repository request
On 19-11-16 19:00:26, Fabian Wolff wrote: > It's 'wolff-guest'. (And please CC me in your replies, as I'm not > subscribed to debian-mentors.) I've created the repo, and gave you Maintainer access. Let me know if that's not sufficient. Cheers, Georg
Re: Salsa repository request
On Thu, 14 Nov 2019 17:01:13 +, Georg Faerber wrote:
> Hi,
>
> On 19-11-13 23:38:46, Fabian Wolff wrote:
> > I am currently working on the boogie package. There has been a new
> > upstream release which I'm trying to package; I'm not very familiar
> > with Mono and CLI packaging, but I'll see how far I can get.
> >
> > In any case, I would like to maintain my (and others') work in a
> > repository on Salsa in the Debian group. But since I'm not a Debian
> > Developer, I can't create the repository myself.
> >
> > So, can somebody please create a 'boogie' repository in the Debian
> > group on Salsa *and* give me Maintainer access to it (so that I can
> > set up everything and push to the master branch etc.)?
> >
> > Thanks in advance!
> >
> > By the way: I did take note of the Vcs-* fields in debian/control, but
> > the URL is not reachable anymore ("404 Not Found"). Also, the current
> > maintainer has given the package up for adoption (#903142), so he
> > won't mind me working on the package.
>
> What's your username on salsa?
Good question :-)
It's 'wolff-guest'. (And please CC me in your replies, as I'm not
subscribed to debian-mentors.)
Thanks again!
Re: Salsa repository request
Hi,
On 19-11-13 23:38:46, Fabian Wolff wrote:
> I am currently working on the boogie package. There has been a new
> upstream release which I'm trying to package; I'm not very familiar
> with Mono and CLI packaging, but I'll see how far I can get.
>
> In any case, I would like to maintain my (and others') work in a
> repository on Salsa in the Debian group. But since I'm not a Debian
> Developer, I can't create the repository myself.
>
> So, can somebody please create a 'boogie' repository in the Debian
> group on Salsa *and* give me Maintainer access to it (so that I can
> set up everything and push to the master branch etc.)?
>
> Thanks in advance!
>
> By the way: I did take note of the Vcs-* fields in debian/control, but
> the URL is not reachable anymore ("404 Not Found"). Also, the current
> maintainer has given the package up for adoption (#903142), so he
> won't mind me working on the package.
What's your username on salsa?
Cheers,
Georg
Salsa repository request
Dear mentors,
I am currently working on the boogie package. There has been a new upstream
release which I'm trying to package; I'm not very familiar with Mono and CLI
packaging, but I'll see how far I can get.
In any case, I would like to maintain my (and others') work in a repository
on Salsa in the Debian group. But since I'm not a Debian Developer, I can't
create the repository myself.
So, can somebody please create a 'boogie' repository in the Debian group on
Salsa *and* give me Maintainer access to it (so that I can set up everything
and push to the master branch etc.)?
Thanks in advance!
By the way: I did take note of the Vcs-* fields in debian/control, but the
URL is not reachable anymore ("404 Not Found"). Also, the current maintainer
has given the package up for adoption (#903142), so he won't mind me working
on the package.
Best regards,
Fabian
Re: Salsa repository request
On Sat, Oct 12, 2019 at 08:45:42AM +0200, Geert Stappers wrote: > On Fri, Oct 11, 2019 at 06:37:29PM +0300, Yavor Doganov wrote: > > Could please someone create a "gkdebconf" project on Salsa and grant > > me (yavor-quest) commit access? This is a Debian-specific program > > that is orphaned and I'm preparing a QA upload. I'll take care to > > import the old repository that used to be on Alioth. > > In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942192 > is hinted that it is done. Yes, it is. ( https://salsa.debian.org/debian/gkdebconf )
Re: Salsa repository request
On Fri, Oct 11, 2019 at 06:37:29PM +0300, Yavor Doganov wrote: > Could please someone create a "gkdebconf" project on Salsa and grant > me (yavor-quest) commit access? This is a Debian-specific program > that is orphaned and I'm preparing a QA upload. I'll take care to > import the old repository that used to be on Alioth. In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942192 is hinted that it is done. > TIA. > Groeten Geert Stappers -- Leven en laten leven
Salsa repository request
Could please someone create a "gkdebconf" project on Salsa and grant me (yavor-quest) commit access? This is a Debian-specific program that is orphaned and I'm preparing a QA upload. I'll take care to import the old repository that used to be on Alioth. TIA.
Re: Salsa repository request (aj-snapshot, dbacl, ffe)
On Monday, August 26 2019, Fabian Wolff wrote: > Thank you! > > Unfortunately, when I tried to push to these repositories, I ran into the > following issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/51484 Ops. > In other words, it seems that you need Maintainer permissions to be able to > push to an empty Gitlab repository, but you've given me only Developer > permissions. Sure thing. Done. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Re: Salsa repository request (aj-snapshot, dbacl, ffe)
Thank you! Unfortunately, when I tried to push to these repositories, I ran into the following issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/51484 In other words, it seems that you need Maintainer permissions to be able to push to an empty Gitlab repository, but you've given me only Developer permissions. So, could you (or somebody else) upgrade my permissions in these three Gitlab repositories to "Maintainer"? On 8/26/19 1:55 AM, Sergio Durigan Junior wrote: > On Sunday, August 25 2019, Fabian Wolff wrote: > >> Hi, > > Hi Fabian, > >> I am currently preparing QA uploads for the 'aj-snapshot', 'dbacl', and >> 'ffe' packages [0, 1, 2]. > > Thanks for doing this. > >> I would like to create packaging repositories for these projects in >> the Debian group on Salsa [3], but since I am not a Debian Developer, >> I don't have the necessary permissions on Salsa to create them myself. >> >> >> So, could somebody please create these three repositories for me and give >> me, wolff-guest, write access to them? > > Done for all three. > > Thanks, >
Re: Salsa repository request (aj-snapshot, dbacl, ffe)
On Sunday, August 25 2019, Fabian Wolff wrote: > Hi, Hi Fabian, > I am currently preparing QA uploads for the 'aj-snapshot', 'dbacl', and 'ffe' > packages [0, 1, 2]. Thanks for doing this. > I would like to create packaging repositories for these projects in > the Debian group on Salsa [3], but since I am not a Debian Developer, > I don't have the necessary permissions on Salsa to create them myself. > > > So, could somebody please create these three repositories for me and give me, > wolff-guest, write access to them? Done for all three. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Salsa repository request (aj-snapshot, dbacl, ffe)
Hi, I am currently preparing QA uploads for the 'aj-snapshot', 'dbacl', and 'ffe' packages [0, 1, 2]. I would like to create packaging repositories for these projects in the Debian group on Salsa [3], but since I am not a Debian Developer, I don't have the necessary permissions on Salsa to create them myself. So, could somebody please create these three repositories for me and give me, wolff-guest, write access to them? Thank you! Best regards, Fabian [0] https://tracker.debian.org/pkg/aj-snapshot [1] https://tracker.debian.org/pkg/dbacl [2] https://tracker.debian.org/pkg/ffe [3] https://salsa.debian.org/debian
Re: Salsa repository request
On Thursday, December 06 2018, Peter Colberg wrote: > Dear mentors, > > I would like to migrate the packages cgit [1] and fcgiwrap [2] to > salsa, but as a DM lack the needed permission for the debian group. > Could you create the two projects and set me (pcolberg-guest) as > master? (I have contacted my co-maintainers but unsuccessfully.) > > Thanks, > Peter > > [1] https://tracker.debian.org/pkg/cgit > [2] https://tracker.debian.org/pkg/fcgiwrap No problem: https://salsa.debian.org/debian/cgit https://salsa.debian.org/debian/fcgiwrap I added you as a Maintainer on both projects. Hopefully that's enough. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Salsa repository request
Dear mentors, I would like to migrate the packages cgit [1] and fcgiwrap [2] to salsa, but as a DM lack the needed permission for the debian group. Could you create the two projects and set me (pcolberg-guest) as master? (I have contacted my co-maintainers but unsuccessfully.) Thanks, Peter [1] https://tracker.debian.org/pkg/cgit [2] https://tracker.debian.org/pkg/fcgiwrap
Re: Salsa repository request
Le 06/11/2018 à 10:05, Dmitry Bogatov a écrit : > > There is self-service: signup.salsa.debian.org > Thanks, I though it needed DD level access. signature.asc Description: OpenPGP digital signature
Re: Salsa repository request
[2018-11-05 15:38] Thomas Perret > > part 1.1 text/plain1182 > Dear mentors, > > I'm currently preparing packaging of paperwork[0] which depends on a few > package I'm also packaging[1-4]. > I'm not sure if this is a good idea but would it be possible to create a > group or subgroup (is it necessary a team?) named openpaperwork which > would contain the following empty repositories: There is self-service: signup.salsa.debian.org
Salsa repository request
Dear mentors, I'm currently preparing packaging of paperwork[0] which depends on a few package I'm also packaging[1-4]. I'm not sure if this is a good idea but would it be possible to create a group or subgroup (is it necessary a team?) named openpaperwork which would contain the following empty repositories: 'paperwork', 'libpillowfight', 'pyinsane' and 'simplebayes' and give them commit access to me (user 'moht-guest') If it is not possible to group them, could you create each of them separately? Another question I have is that paperwork depends on an existing package which seems abandoned[4]. I have already contacted the maintainer without response for now. Would it be possible to create a repository 'pyocr' for this source also even if it will not be used as official source for now but just to prepare the update if I either adopt the package or salvage it? Thanks [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721287 [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741881 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912928 [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912927 [4]: https://tracker.debian.org/pkg/python-pyocr signature.asc Description: OpenPGP digital signature
Re: Salsa repository request
On Wed, Oct 24, 2018 at 01:42:00PM +0300, Yavor Doganov wrote: > I'd appreciate if someone creates an empty gnome-mastermind repository > at salsa.d.o and grants me (yavor-guest) commit access. This package > has been orphaned by Bart Martens (bartm) in 2016 (#826926). Done. https://salsa.debian.org/debian/gnome-mastermind/project_members Please consider to use `gbp import-dscs --debsnap` for the initial repository creation, so to have all the package's history in git. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Salsa repository request
I'd appreciate if someone creates an empty gnome-mastermind repository at salsa.d.o and grants me (yavor-guest) commit access. This package has been orphaned by Bart Martens (bartm) in 2016 (#826926). TIA.
Re: Salsa repository request
On Sun, Jun 24, 2018 at 04:59:03PM +0300, Alexander Inyukhin wrote: > I have to move old task-spooler repository from collab-maint on alioth > to debian project at salsa. > > I would like to ask someone to create an empty repository task-spooler > on salsa and grant access to it for user shurick-guest. Done. -- ⢀⣴⠾⠻⢶⣦⠀ There's an easy way to tell toy operating systems from real ones. ⣾⠁⢰⠒⠀⣿⡁ Just look at how their shipped fonts display U+1F52B, this makes ⢿⡄⠘⠷⠚⠋⠀ the intended audience obvious. It's also interesting to see OSes ⠈⠳⣄ go back and forth wrt their intended target.
Salsa repository request
Hello, mentors! I have to move old task-spooler repository from collab-maint on alioth to debian project at salsa. I would like to ask someone to create an empty repository task-spooler on salsa and grant access to it for user shurick-guest. Thanks!
Re: Salsa repository request
On Monday, June 18 2018, Fabian Wolff wrote: > On Sun, Jun 17, 2018 at 07:02:15PM -0400, Sergio Durigan Junior wrote: >> I see a few problems here; some I need you to address before moving >> forward, and others can be tackled later. Let me make a list: >> >> 1) You're basically removing functionalities from the upstream project, >> so I think you should detail what's being removed (and why) on >> d/README.Debian. >> >> 2) I also think it's a good idea to proper license your code, because it >> will be redistributed along with the project. I'd suggest choosing the >> same license as the project. >> >> These two problems are easy enough to fix, and I think that uploading a >> package without having them addressed first is not going to work. > > I have added a README.Debian as well as copyright and license notices > in antlr3convertutf.*. Thanks. >> Other things worth doing: >> >> 3) IANAL, but this issue seems serious enough to justify contacting >> upstream and reporting the problem to them. > > https://github.com/antlr/antlr3/issues/193 > > I don't have much hope though; the most recent activity in the > runtime/C/ folder of the repository seems to date back to more than > four years ago. Oh, well... At least you've done your part. >> 4) I see that src/antlr3string.c is the only user of the >> ConvertUTF16toUTF8 function. What do you think of declaring the >> function inside the file? This way we'd get rid of the problematic >> files, which is a good thing, since we'll not export their API anymore. > > In principle, I agree. In fact, the declaration of ConvertUTF16toUTF8 > is already in antlr3string.c (and not in the header file). However, > moving the *definition* of the function into antlr3string.c (which is > probably what you meant) is not possible because it is a C++ function, > and antlr3string.c is written in C. Yeah, that'd complicate things indeed. > Also, the remaining content of the header file (the typedefs and > preprocessor definitions) are used in other parts of the code, too (in > antlr3inputstream.c, for instance). Right. Going forward, maybe you could make sure that the ./usr/include/antlr3convertutf.h file is not installed as part of the -dev package, since we don't want to export the API at all. >> > Sergio, would you be willing to sponsor this upload? I would also be >> > glad if you could assist me with the rest of the transition process. >> >> Yeah, I'd be happy too. It will be my first time monitoring a >> transition :-). Just let me know when you have addressed the two issues >> I mentioned above, and I'll upload the package right away. > > I have pushed my changes to the Salsa repository (on the > debian-experimental branch), and I've also reuploaded the package to > Mentors. Thanks, I've uploaded the package now. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Re: Salsa repository request
On Sun, Jun 17, 2018 at 07:02:15PM -0400, Sergio Durigan Junior wrote:
> I see a few problems here; some I need you to address before moving
> forward, and others can be tackled later. Let me make a list:
>
> 1) You're basically removing functionalities from the upstream project,
> so I think you should detail what's being removed (and why) on
> d/README.Debian.
>
> 2) I also think it's a good idea to proper license your code, because it
> will be redistributed along with the project. I'd suggest choosing the
> same license as the project.
>
> These two problems are easy enough to fix, and I think that uploading a
> package without having them addressed first is not going to work.
I have added a README.Debian as well as copyright and license notices
in antlr3convertutf.*.
> Other things worth doing:
>
> 3) IANAL, but this issue seems serious enough to justify contacting
> upstream and reporting the problem to them.
https://github.com/antlr/antlr3/issues/193
I don't have much hope though; the most recent activity in the
runtime/C/ folder of the repository seems to date back to more than
four years ago.
> 4) I see that src/antlr3string.c is the only user of the
> ConvertUTF16toUTF8 function. What do you think of declaring the
> function inside the file? This way we'd get rid of the problematic
> files, which is a good thing, since we'll not export their API anymore.
In principle, I agree. In fact, the declaration of ConvertUTF16toUTF8
is already in antlr3string.c (and not in the header file). However,
moving the *definition* of the function into antlr3string.c (which is
probably what you meant) is not possible because it is a C++ function,
and antlr3string.c is written in C.
Also, the remaining content of the header file (the typedefs and
preprocessor definitions) are used in other parts of the code, too (in
antlr3inputstream.c, for instance).
> Great. I see you did the experimental work on the master branch. I
> personally don't think it's a good idea, because eventually you'll have
> to release the package on stable, and d/changelog doesn't need to have
> entries reflecting experimental releases. What I usually do is create a
> separate branch ("debian-experimental" or some such) and do the
> experimental work there. This way, when it's time to merge, it's
> easier.
>
> There's a nice write-up of this workflow here:
>
>
> https://wiki.debian.org/PackagingWithGit#Merging_a_debian-experimental_branch_into_master_for_sid
>
> But bear in mind, you don't need to fix this before I upload. Actually,
> if you prefer you can keep your experimental work on the master branch,
> no problem at all.
Thanks for the info. I have now continued my work on the
debian-experimental branch.
> > Sergio, would you be willing to sponsor this upload? I would also be
> > glad if you could assist me with the rest of the transition process.
>
> Yeah, I'd be happy too. It will be my first time monitoring a
> transition :-). Just let me know when you have addressed the two issues
> I mentioned above, and I'll upload the package right away.
I have pushed my changes to the Salsa repository (on the
debian-experimental branch), and I've also reuploaded the package to
Mentors.
Best regards,
Fabian
Re: Salsa repository request
On Saturday, June 16 2018, Fabian Wolff wrote:
> On Sat, Jun 16, 2018 at 02:53:54PM -0400, Sergio Durigan Junior wrote:
>> On Saturday, June 16 2018, Fabian Wolff wrote:
>> > Could someone please create a 'libantlr3c' repository in the Debian
>> > group on Salsa and give me (wolff-guest) write access to it? An empty
>> > repository will suffice, I will populate the repository with the
>> > history from snapshot.debian.org as well as my own changes.
>>
>> Done:
>>
>> https://salsa.debian.org/debian/libantlr3c
>
> Great, thank you.
No problem.
> You see, I am the maintainer of a reverse dependency of libantlr3c
> (cvc4). libantlr3c is scheduled for autoremoval on 15 July due to
> #900601, and since libantlr3c is currently orphaned, I took it upon
> myself to investigate the issue.
That's a great initiative, thanks a lot for doing it.
> I have attempted to fix the issue by removing the non-DFSG-compliant
> files.
OK.
> One of the functions that was defined there is needed by other
> parts of the code, however, which is why I have provided an
> alternative implementation. I know rather little about proper Unicode
> string handling, and I have never worked with libicu, which is why
> I've attempted a solution in C++. Better solutions are welcome, of
> course.
OK. That's kind of a bold move, but I can see your rationale. I myself
have never worked with Unicode as well, so it's hard to say if your code
will really work. It does look OK, but without proper testing it's a
shot in the dark.
I see a few problems here; some I need you to address before moving
forward, and others can be tackled later. Let me make a list:
1) You're basically removing functionalities from the upstream project,
so I think you should detail what's being removed (and why) on
d/README.Debian.
2) I also think it's a good idea to proper license your code, because it
will be redistributed along with the project. I'd suggest choosing the
same license as the project.
These two problems are easy enough to fix, and I think that uploading a
package without having them addressed first is not going to work.
Other things worth doing:
3) IANAL, but this issue seems serious enough to justify contacting
upstream and reporting the problem to them.
4) I see that src/antlr3string.c is the only user of the
ConvertUTF16toUTF8 function. What do you think of declaring the
function inside the file? This way we'd get rid of the problematic
files, which is a good thing, since we'll not export their API anymore.
> Removing the non-DFSG files changes the public API, so a transition is
> necessary. There has also been a new upstream release that changes the
> SONAME, so I figured it would be best to combine both of those into a
> single transition, which is why I've included the new upstream release
> into this QA upload.
>
> I have uploaded the package to Mentors:
>
> https://mentors.debian.net/package/libantlr3c
>
> I have set the distribution to "experimental", as described in [0].
Great. I see you did the experimental work on the master branch. I
personally don't think it's a good idea, because eventually you'll have
to release the package on stable, and d/changelog doesn't need to have
entries reflecting experimental releases. What I usually do is create a
separate branch ("debian-experimental" or some such) and do the
experimental work there. This way, when it's time to merge, it's
easier.
There's a nice write-up of this workflow here:
https://wiki.debian.org/PackagingWithGit#Merging_a_debian-experimental_branch_into_master_for_sid
But bear in mind, you don't need to fix this before I upload. Actually,
if you prefer you can keep your experimental work on the master branch,
no problem at all.
> Sergio, would you be willing to sponsor this upload? I would also be
> glad if you could assist me with the rest of the transition process.
Yeah, I'd be happy too. It will be my first time monitoring a
transition :-). Just let me know when you have addressed the two issues
I mentioned above, and I'll upload the package right away.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
signature.asc
Description: PGP signature
Re: Salsa repository request
On Sat, Jun 16, 2018 at 02:53:54PM -0400, Sergio Durigan Junior wrote: > On Saturday, June 16 2018, Fabian Wolff wrote: > > Could someone please create a 'libantlr3c' repository in the Debian > > group on Salsa and give me (wolff-guest) write access to it? An empty > > repository will suffice, I will populate the repository with the > > history from snapshot.debian.org as well as my own changes. > > Done: > > https://salsa.debian.org/debian/libantlr3c Great, thank you. You see, I am the maintainer of a reverse dependency of libantlr3c (cvc4). libantlr3c is scheduled for autoremoval on 15 July due to #900601, and since libantlr3c is currently orphaned, I took it upon myself to investigate the issue. I have attempted to fix the issue by removing the non-DFSG-compliant files. One of the functions that was defined there is needed by other parts of the code, however, which is why I have provided an alternative implementation. I know rather little about proper Unicode string handling, and I have never worked with libicu, which is why I've attempted a solution in C++. Better solutions are welcome, of course. Removing the non-DFSG files changes the public API, so a transition is necessary. There has also been a new upstream release that changes the SONAME, so I figured it would be best to combine both of those into a single transition, which is why I've included the new upstream release into this QA upload. I have uploaded the package to Mentors: https://mentors.debian.net/package/libantlr3c I have set the distribution to "experimental", as described in [0]. Sergio, would you be willing to sponsor this upload? I would also be glad if you could assist me with the rest of the transition process. Thank you very much! Best regards, Fabian [0] https://wiki.debian.org/Teams/ReleaseTeam/Transitions
Re: Salsa repository request
On Saturday, June 16 2018, Fabian Wolff wrote: > Dear mentors, Hi Fabian, > I am currently preparing a QA upload for the libantlr3c package. > > This package is currently orphaned and not maintained in any packaging > VCS repository. For this reason, I think it would be a good idea to > create a repository for this package on Salsa in the Debian group. > However, since I am not a Debian Developer, I cannot create the > repository myself. Good idea. > Could someone please create a 'libantlr3c' repository in the Debian > group on Salsa and give me (wolff-guest) write access to it? An empty > repository will suffice, I will populate the repository with the > history from snapshot.debian.org as well as my own changes. Done: https://salsa.debian.org/debian/libantlr3c Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Salsa repository request
Dear mentors, I am currently preparing a QA upload for the libantlr3c package. This package is currently orphaned and not maintained in any packaging VCS repository. For this reason, I think it would be a good idea to create a repository for this package on Salsa in the Debian group. However, since I am not a Debian Developer, I cannot create the repository myself. Could someone please create a 'libantlr3c' repository in the Debian group on Salsa and give me (wolff-guest) write access to it? An empty repository will suffice, I will populate the repository with the history from snapshot.debian.org as well as my own changes. Thank you! Best regards, Fabian
Re: Salsa repository request (gpp)
On Tuesday, May 15 2018, Fabian Wolff wrote: > On Mon, May 14, 2018 at 10:16:42PM -0400, Sergio Durigan Junior wrote: >> Hey Fabian, >> >> Can you add yourself on d/copyright, under the entry for the "debian/*" >> files? After all, you deserve the credit as well ;-). >> >> Other than that, it's ready for upload. Let me know when you make the >> change, and I'll upload it. > > I have added myself in debian/copyright and reuploaded the package to > Mentors: > > https://mentors.debian.net/package/gpp > > Thanks for sponsoring the upload! Thank you. I've uploaded it now. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Re: Salsa repository request (gpp)
On Mon, May 14, 2018 at 10:16:42PM -0400, Sergio Durigan Junior wrote: > Hey Fabian, > > Can you add yourself on d/copyright, under the entry for the "debian/*" > files? After all, you deserve the credit as well ;-). > > Other than that, it's ready for upload. Let me know when you make the > change, and I'll upload it. I have added myself in debian/copyright and reuploaded the package to Mentors: https://mentors.debian.net/package/gpp Thanks for sponsoring the upload! Best regards, Fabian
Re: Salsa repository request (gpp)
On Monday, May 14 2018, Fabian Wolff wrote: > On Mon, May 14, 2018 at 06:39:47PM +0200, Geert Stappers wrote: >> There is now https://salsa.debian.org/debian/gpp >> Account wolff-guest has developer privilege. >> >> Take it for a spin ( slang for testdrive ) >> and come with your feedback :-) > > Great, thank you! > > Would you, by any chance, be interested in sponsoring the QA upload? > > I have pushed my changes to the Salsa repository, and I've also > uploaded the package on Mentors: > > https://mentors.debian.net/package/gpp > https://mentors.debian.net/debian/pool/main/g/gpp/gpp_2.25-1.dsc > > I would be glad if you could have a look at it! Hey Fabian, Can you add yourself on d/copyright, under the entry for the "debian/*" files? After all, you deserve the credit as well ;-). Other than that, it's ready for upload. Let me know when you make the change, and I'll upload it. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Re: Salsa repository request (gpp)
On Monday, May 14 2018, Fabian Wolff wrote: > On Mon, May 14, 2018 at 06:39:47PM +0200, Geert Stappers wrote: >> There is now https://salsa.debian.org/debian/gpp >> Account wolff-guest has developer privilege. >> >> Take it for a spin ( slang for testdrive ) >> and come with your feedback :-) > > Great, thank you! > > Would you, by any chance, be interested in sponsoring the QA upload? > > I have pushed my changes to the Salsa repository, and I've also > uploaded the package on Mentors: > > https://mentors.debian.net/package/gpp > https://mentors.debian.net/debian/pool/main/g/gpp/gpp_2.25-1.dsc > > I would be glad if you could have a look at it! I can take a look at this later if you want. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Re: Salsa repository request (gpp)
On Mon, May 14, 2018 at 07:16:41PM +0200, Fabian Wolff wrote: > On Mon, May 14, 2018 at 06:39:47PM +0200, Geert Stappers wrote: > > There is now https://salsa.debian.org/debian/gpp > > Account wolff-guest has developer privilege. > > > > Take it for a spin ( slang for testdrive ) > > and come with your feedback :-) > > Great, thank you! OK, works. That is good for https://lists.debian.org/debian-mentors/2018/05/msg00150.html > Would you, by any chance, be interested in sponsoring the QA upload? E_OTHERPRIO Groeten Geert Stappers DD -- Leven en laten leven signature.asc Description: Digital signature
Re: Salsa repository request (gpp)
On Mon, May 14, 2018 at 06:39:47PM +0200, Geert Stappers wrote: > There is now https://salsa.debian.org/debian/gpp > Account wolff-guest has developer privilege. > > Take it for a spin ( slang for testdrive ) > and come with your feedback :-) Great, thank you! Would you, by any chance, be interested in sponsoring the QA upload? I have pushed my changes to the Salsa repository, and I've also uploaded the package on Mentors: https://mentors.debian.net/package/gpp https://mentors.debian.net/debian/pool/main/g/gpp/gpp_2.25-1.dsc I would be glad if you could have a look at it! Best regards, Fabian
Re: Salsa repository request (gpp)
On Mon, May 14, 2018 at 04:40:32PM +0200, Fabian Wolff wrote: > Dear mentors, > > I am currently preparing a QA upload for the gpp package. > > The gpp package is not yet maintained in any VCS repository, so I > think it might be a good idea to create a Git repository in the Debian > group on Salsa for gpp packaging. > > However, I don't have access to the Debian group on Salsa, so could > someone please create a gpp repository there and give me (wolff-guest) > write access to it? An empty repository will suffice, I will populate > some history (i. e., what I found on snapshot.debian.org) along with > the changes I've made for the upcoming QA upload. There is now https://salsa.debian.org/debian/gpp Account wolff-guest has developer privilege. Take it for a spin ( slang for testdrive ) and come with your feedback :-) Cheers Geert Stappers DD What follows might help, otherwise consider it noise ... Create a new repository git clone g...@salsa.debian.org:debian/gpp.git cd gpp touch README.md git add README.md git commit -m "add README" git push -u origin master Existing folder cd existing_folder git init git remote add origin g...@salsa.debian.org:debian/gpp.git git add . git commit -m "Initial commit" git push -u origin master Existing Git repository cd existing_repo git remote rename origin old-origin git remote add origin g...@salsa.debian.org:debian/gpp.git git push -u origin --all git push -u origin --tags signature.asc Description: Digital signature
Salsa repository request (gpp)
Dear mentors, I am currently preparing a QA upload for the gpp package. The gpp package is not yet maintained in any VCS repository, so I think it might be a good idea to create a Git repository in the Debian group on Salsa for gpp packaging. However, I don't have access to the Debian group on Salsa, so could someone please create a gpp repository there and give me (wolff-guest) write access to it? An empty repository will suffice, I will populate some history (i. e., what I found on snapshot.debian.org) along with the changes I've made for the upcoming QA upload. Thank you! Best regards, Fabian
Re: Salsa repository request (link-grammar)
On Thursday, April 26 2018, Fabian Wolff wrote: > Dear mentors, Hey, Fabian, > I am currently preparing a QA upload for the link-grammar Debian > package. The link-grammar packaging Git repository is currently still > hosted on Alioth: > > https://anonscm.debian.org/git/collab-maint/link-grammar.git > > I would like to migrate the repository to Salsa, but since I am not a > Debian Developer, I do not have access to the Debian group on Salsa. > Therefore, I would like to ask for someone to create a "link-grammar" > packaging repository in the Debian group on Salsa and grant me > (wolff-guest) write access to it. An empty repository will suffice; > I'll take care of the rest (including a Merge Request for > AliothRewriter). There you go: https://salsa.debian.org/debian/link-grammar > Once the new repository is in place, it would be a good idea to lock > the old Alioth repository, which can be achieved by creating the file > /git/collab-maint/link-grammar.git/hooks/pre-receive with the > following content, which I would also like to ask you to do, since I > do not have write access in that location: > > """ > #!/bin/sh > > cat < > This repository has been moved to salsa.debian.org: > https://salsa.debian.org/debian/link-grammar > > EOF > > exit 1 > """ Done as well. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Salsa repository request (link-grammar)
Dear mentors, I am currently preparing a QA upload for the link-grammar Debian package. The link-grammar packaging Git repository is currently still hosted on Alioth: https://anonscm.debian.org/git/collab-maint/link-grammar.git I would like to migrate the repository to Salsa, but since I am not a Debian Developer, I do not have access to the Debian group on Salsa. Therefore, I would like to ask for someone to create a "link-grammar" packaging repository in the Debian group on Salsa and grant me (wolff-guest) write access to it. An empty repository will suffice; I'll take care of the rest (including a Merge Request for AliothRewriter). Once the new repository is in place, it would be a good idea to lock the old Alioth repository, which can be achieved by creating the file /git/collab-maint/link-grammar.git/hooks/pre-receive with the following content, which I would also like to ask you to do, since I do not have write access in that location: """ #!/bin/sh cat
Re: Salsa repository request
On Mon, Apr 02, 2018 at 04:04:32PM +0200, Fabian Wolff wrote: > > It would probably be a good idea to lock the Alioth repository. I > seem to lack the necessary permissions to create a pre-receive hook > for the eqonomize Alioth repository, so perhaps someone could create > /git/collab-maint/eqonomize.git/hooks/pre-receive on alioth.debian.org > with the following content: > > """ > #!/bin/sh > > cat < > This repository has been moved to salsa.debian.org: > https://salsa.debian.org/debian/eqonomize > > EOF > > exit 1 > """ done > Thanks! >
Re: Salsa repository request
On Mon, Apr 02, 2018 at 09:27:26AM +0200, Tobias Frost wrote: > Done, created empty repoisotry. (Please populate the complete history) > https://salsa.debian.org/debian/eqonomize Great, thank you! > Please also add an MR for the AliothRewriter @ > https://salsa.debian.org/salsa/AliothRewriter https://salsa.debian.org/salsa/AliothRewriter/merge_requests/250 It would probably be a good idea to lock the Alioth repository. I seem to lack the necessary permissions to create a pre-receive hook for the eqonomize Alioth repository, so perhaps someone could create /git/collab-maint/eqonomize.git/hooks/pre-receive on alioth.debian.org with the following content: """ #!/bin/sh cat
Re: Salsa repository request
On Sun, Apr 01, 2018 at 04:42:09PM +0200, Fabian Wolff wrote: > Dear mentors, > > I am currently preparing a QA upload for the eqonomize Debian package. > > I have based my work on top of the existing packaging Git repository, > which is currently still hosted on Alioth [0]. > > However, with Alioth being replaced by Salsa, I think it would be a > good idea to migrate the repository to Salsa. Based on [1], I'd say > that the Debian group on Salsa would be a good location. > > Because I am not a Debian Developer and, therefore, do not have access > to the Debian group on Salsa, I would hereby like to ask for someone > to create an "eqonomize" packaging repository in the Debian group and > grant me (wolff-guest) write access to it. > > An empty repository will suffice; I'll take care of the rest. Done, created empty repoisotry. (Please populate the complete history) https://salsa.debian.org/debian/eqonomize Please also add an MR for the AliothRewriter @ https://salsa.debian.org/salsa/AliothRewriter Thanks, tobi > > Thank you! > > Best regards, > Fabian > > [0] https://anonscm.debian.org/cgit/collab-maint/eqonomize.git > [1] https://wiki.debian.org/Salsa/Doc#Groups >
Salsa repository request
Dear mentors, I am currently preparing a QA upload for the eqonomize Debian package. I have based my work on top of the existing packaging Git repository, which is currently still hosted on Alioth [0]. However, with Alioth being replaced by Salsa, I think it would be a good idea to migrate the repository to Salsa. Based on [1], I'd say that the Debian group on Salsa would be a good location. Because I am not a Debian Developer and, therefore, do not have access to the Debian group on Salsa, I would hereby like to ask for someone to create an "eqonomize" packaging repository in the Debian group and grant me (wolff-guest) write access to it. An empty repository will suffice; I'll take care of the rest. Thank you! Best regards, Fabian [0] https://anonscm.debian.org/cgit/collab-maint/eqonomize.git [1] https://wiki.debian.org/Salsa/Doc#Groups
