> You can avoid resetting or forcing anything by increasing the
> repacksuffix. As far as both git and the tooling are concerned, that
> makes it an all new upstream version without conflicts with the
> repo's current content, so pushing to git works just fine.
> First update the excluded files
On Fri, 28 Oct 2022 16:46:51 +0300
Ileana Dumitrescu wrote:
> > I did just notice the upstream release contains several other
> > files worth considering for removal: a bunch of windows
> > executables [1].
>
> I agree and can remove those from the source tarball too. To do that
> with the
Thanks for taking over!
I totally lost interest in maintaining that package and kind of
neglected it because of the vendoring and the package itself or rather
its upstream. Anyways, I thought I've orphaned it long time ago (maybe I
forgot to do that). So thank you for taking over, I'm sure a
> I did just notice the upstream release contains several other files
> worth considering for removal: a bunch of windows executables [1].
I agree and can remove those from the source tarball too. To do that
with the current upstream version in salsa though requires me to git
reset, re-import the
On Wed, 26 Oct 2022 17:29:59 +0300
Ileana Dumitrescu wrote:
> Thank you for the feedback! I made changes as you suggested. There
> is a new upstream version that I also included in the new package.
Great! The copyright stuff is a chore on packages like this, so
thanks alot for seeing that
Hi,
Thank you for the feedback! I made changes as you suggested. There is
a new upstream version that I also included in the new package. New
updates are in salsa, and I will put a RFS on the IRC channel.
Reading debian package policy I noticed that removing files from a
tarball for a repack (as
6 matches
Mail list logo
