darix
darix
This seems to be caused by the git merge call in TarSCM/scm/git.py line 55. The error goes away, if it is replaced with: ``` self._get_scm_cmd() + ['checkout', self.revision], ``` When...
same here
I usually start packages from scratch using https://build.opensuse.org/. Which can do rpms/debs/archpackages. As you can see [here][0] e.g. For my djv package i am stuck with the glad and FSeq...
(actually i am also curious about the whole: why do we need rapidjson and picojson?)
> Gotcha, so you need to have a release of FSeq since it's a dependency. can we have the FSeq release ready for the next DJV release? then i would...
if you commit the glad files i will do a git snapshot of fseq and djv to test the packaging.
so version would be required true. but stability is not true. you only need to know when to bump. and there are tools for tracking when you need to bump...
This is the workflow after I asked them for release support: https://github.com/processone/eturnal/blob/master/.github/workflows/release.yml background: you can have a custom subscription on GH for release + security but not for tag ^^
i wonder if it makes sense to refactor out something like ``` def _load_policy(policy_file, policy): if policy and policy_file: raise ValueError( "only one of policy or policy_file may be specified")...
@mlschroe do we actually install the locale packages on all distros to support en_US.UTF-8? IIRC for some DB testing i had to manually install even glibc-locale-base on SUSE.