> I believe the way to go is to first upload my version, then put your 
> improvement on it but answer to santiago answer
>
> One small step at time is better
>
> rouca

can't we just skip that release? do you have any patches not applied?


> Why are your removing the above? Commit bea8ca3b doesn't contain any
> explanation about the change. v%(version)s still complies with DEP-14
> and the coexistence with upstream git.

Using the upstream-vcs-tag causes the git history to pollute with all the 
upstream commits, imho is just better to remove it so we keep the relevant part 
of the package history. I added a bit more explanation in the commit that 
removes it.


> It is to note that I cannot find most of the above changes in git.

Changes are in the work/3.8.4-1 branch, I created a MR to increase visibility 
here
https://salsa.debian.org/debian/libarchive/-/merge_requests/8

I made a few changes, managed to get the orig tarball signed and fixed some 
(not all) of the (pedantic) lintian warnings.

Regards,
Gabriel

________________________________
From: Bastien Roucaries
Sent: Thursday, December 18, 2025 2:18 AM
To: Gabriel Barrantes; [email protected]; Santiago Ruano Rincón
Subject: Re: Bug#1123373: RFS: libarchive/3.8.4-1 [ITA] -- FreeBSD 
implementations of 'tar' and 'cpio' and other archive tools

Le mercredi 17 décembre 2025, 02:22:00 heure normale d’Europe centrale Santiago 
Ruano Rincón a écrit :
> Hi,
>
> CCing Bastien, that worked on the 3.8.2 version, that was pending to be
> uploaded.

I believe the way to go is to first upload my version, then put your 
improvement on it but answer to santiago answer

One small step at time is better

rouca
>
> El 16/12/25 a las 19:54, Gabriel Barrantes escribió:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "libarchive":
> >
> >  * Package name     : libarchive
> >    Version          : 3.8.4-1
> >    Upstream contact : Tim Kientzle <[email protected]>
> >  * URL              : https://www.libarchive.org/
> >  * License          : Expat, Apache-2.0 or CC0-1.0 or OpenSSL+SSLeay, 
> > BSD-2-clause and Expat, BSD-124-clause-UCB, BSD-2-clause, PD, BSD-2-clause 
> > and BSD-1-clause-UCB, BSD-2-clause and BSD-3-clause-UCB, BSD-4-clause-UCB, 
> > BSD-2-clause and BSD-124-clause-UCB, Apache-2.0
> >  * Vcs              : https://salsa.debian.org/debian/libarchive
> >    Section          : libs
> >
> > The source builds the following binary packages:
> >
> >   libarchive-dev - Multi-format archive and compression library 
> > (development files)
> >   libarchive13t64 - Multi-format archive and compression library (shared 
> > library)
> >   libarchive-tools - FreeBSD implementations of 'tar' and 'cpio' and other 
> > archive tools
> >
> > To access further information about this package, please visit the 
> > following URL:
> >
> >   https://mentors.debian.net/package/libarchive/
> >
> > Alternatively, you can download the package with 'dget' using this command:
> >
> >   dget -x 
> > https://mentors.debian.net/debian/pool/main/liba/libarchive/libarchive_3.8.4-1.dsc
> >
> > Changes since the last upload:
> >
> >  libarchive (3.8.4-1) unstable; urgency=medium
> >  .
> >    * New upstream release.
> >    * Update debian/libarchive13t64.symbols.
> >    * Remove upstream-vcs-tag setting from debian/gbp.conf.
>
> Why are your removing the above? Commit bea8ca3b doesn't contain any
> explanation about the change. v%(version)s still complies with DEP-14
> and the coexistence with upstream git.
>
> >    * Delete debian/README.Debian, as it is no longer applicable.
> >    * Switch debian/watch to version 5.
> >    * Add debian/.gitignore.
> >    * Make minor improvements to debian/upstream/metadata.
> >    * Adopt the package (Closes: #1122503).
> >    * Remove unneeded patches:
> >      - debian/patches/typos.patch
> >      - debian/patches/test-locale-C.UTF-8.patch
> >
>
> It is to note that I cannot find most of the above changes in git.
>
> > Regards,
> > --
> >   Gabriel Barrantes
> >
> >
>
> Cheers,
>
>  -- Santiago
>

Reply via email to