Hi Edmundo, Edmundo Carmona Antoranz, on 2026-08-15: > Hi, Etienne! > > (This mail is not being sent to the mail list, I am mailing you > directly... feel free to loop the mail list if you deem it necessary).
I'm doing that now, so that others in the mailing list may get a chance to look at the matter too. Sorry for the slight delay, I'm in vacations, nearing the end, but I struggle a bit getting back into the stream of Debian activities for now. > So.... A few weeks ago I noticed a few things: > - it looks like OSCAR has moved to a new repository.... _again_. > > It used to be over here: https://gitlab.com/CrimsonNape/OSCAR-code, > which is where you had adjusted the med-team repo to point to. > > But now it is over here: https://gitlab.com/CrimsonNape/oscar-sql > > Not that I am _sure_ that the movement was officially carried out... I > really do not know. What I do now is that when I run OSCAR on my > computer, it tells me about OSCAR 2.0.1 being available _and_ the > second repo I pointed to over there does have that tag, unlike the > _old_ one where v2.0.0 and v2.0.1 are not defined. > > Upon closer examination, it is weird that v1.7.x is not defined in the > "new" repo... check by yourself, just in case: > old: https://gitlab.com/CrimsonNape/OSCAR-code/-/tags > new: https://gitlab.com/CrimsonNape/oscar-sql/-/tags This is curious indeed. I had a quick look at both repositories histories. They seem to be somewhat distinct. The second one seems to contain merged contributions that have been injected to the code repository with a git-rebase(1). This makes both histories somewhat divergent. I would assume upstream would have wanted to preserve the original history somehow of the branch 1.7, but ended up resorting to a separate repository. That's of course just a conjecture of mine and there may be other reasons though. > Anyway, I tried to register myself in salsa.debian.org but when being > asked to _really_ register a new account (instead of trusting a > service where I had already created one account like google... I know, > I know, it's debian), I refrained. > > So, I sent a mail to the mail list almost 2 months ago with a patch to > be applied on the repo to adjust the URL path... but I guess it has > not been processed and, probably, it was rejected because of being a > mail with an attachment. I would not be surprised. > > Well.... I know I haven't been the _best_ maintainer out there :-D But > at least I am keeping an eye on things. You are catching the kind of weird upstream behavior that makes automated version capture non-workable. I think this is very useful. Thank you! :) > What should be the _first_ step in my way to become a maintainer? > Creating an account in salsa? :( Regarding to contribution to Debian Med team, which is the umbrella team for the oscar package, the first step would be to join the team and have a look at the team's policy [1]. I'm afraid that you will need an account on Debian Salsa, since this is the landing pad of the work carried on Debian Med packages. Due to spam, I believe that the registration step is going to require contacting a Salsa administrator. Don't hesitate to reach them, they don't bite. ;) If you justify that you would need the account for contributing to Debian Med and point to the present mail thread in the list archives [2], then I think there should not be any difficulites. [1] : https://med-team.pages.debian.net/policy/ [2] : https://lists.debian.org/debian-med/ > BR! > > PS I also noticed that back in time, when you did the previous URL > change because of my nagging about it, you also _bumped_ the debian > files for OSCAR so I already know that it is not about _just_ updating > the URL repo.... but I guess those are the things I will have to learn > how to do. Sure, there are a few things to carry before bumping a package version in Debian unstable. Those items are described in the team policy ; the document also contains pointers to several other, more generic, Debian documentations about contributing. Have a nice day, :) -- .''`. Étienne Mollier <[email protected]> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `-
signature.asc
Description: PGP signature
