Tobias, Thanks for the response by the way - I appreciate more than just me taking a look at this, and I definitely appreciate everyone being willing to read
On 7/13/19 7:41 AM, Tobias Frost wrote: > Hi Thomas, > > thanks for this ITS! > > On Wed, Jul 10, 2019 at 12:37:30PM -0400, Thomas Ward wrote: >> Also note that because of the package being out of date, and no response >> from maintainer yet, downstream in Ubuntu the packages have diverged so >> that this can be updated downstream from Debian. This is visible at >> https://launchpad.net/ubuntu/+source/xca/2.1.2-0ubuntu1 if you wish to >> see the package properly. Just as an FYI, https://launchpad.net/ubuntu/+source/xca/2.1.2-0ubuntu2 was recently uploaded to Ubuntu, and move the PostgreSQL and MySQL bits over to a Recommends instead of a full dependency (though the sqlite bits are still a requisite for it to 'just function normally' for local operation). This was in recommendation from another MOTU downstream. (But has no impact on the fact we are diverged downstream until we come up with a solution here in Debian for this package). >> NOTE: there is no 'source' package Vcs store anymore that can be >> publicly used, so this package drops the Vcs-Git line in control. >> Eventually I'd like to include this in Salsa, but that's not yet doable. > Yes, it is unfortunate that the repo is gone… > Can you elaborate why salsa is not doable? Can we help? Help would definitely be nice, the main reason I said 'salsa is not doable' is because I'm still figuring out some quirks of git-buildpackage (gbp from hereon out in this email). But I think I figured out the headache I was running into here regarding Salsa. The Salsa specific headaches I was running into was because of a combination of problems, actually. Firstly, I was trying to create a local Git repo on a system that was APPARENTLY set up to use Linux home dirs on a Samba share that was being stupid. This was at work. Secondly, my Internet decided to consider Salsa unreachable for some reason on my residential class network. Thirdly, when I used the business static connection I have at my home, IDS triggered. Which is annoying. Finally can get to Salsa's "Create Repository" function now. Finally, note that I am not a DM or a DD yet - I do not have direct upload rights to Debian, and on Salsa I am only a 'guest' user at the moment. Also note that downstream from Debian, in Ubuntu, I have Core Developer rights, which give me full upload to all pockets (Main, Universe, Multiverse, etc.) in Ubuntu, if this gives any impact on whether my keys need to be included in Debian's keyrings or not or whether this can be utilized as a mechanism to assist me in getting a standard developer account on Salsa rather than the guest account I am currently using, that'd be great. > (Appologizes if I tell you something you know already: gitbuildpacakge > has an import feature for all previous Debian versions from snapshot.d.o > .. If you make a git repo, would be nice if you could include all > previpous versions) This is where some help would be nice - I'm still learning gbp as it isn't part of my USUAL downstream process in Ubuntu for the packages I work with (nginx primarily, with countless drive-by fixes and uploads I've done in other packages). Is this automatic, or is this a flag in gbp that I have to provide to gbp? > -- > tobi
