On Thu, 2022-10-20 at 10:11 +0200, Johannes Schauer Marin Rodrigues
wrote:
> Hi Debora,
>
> Quoting Debora Velarde Babb (2022-10-20 08:04:35)
> > The upstream package for tss2 has been renamed ibmtss. When the
> > name was
> > changed upstream, the version number convention also
> > changed. Ups
On 21.10.22 20:06, Johannes Schauer Marin Rodrigues wrote:
Is that really the correct statement? Even after excluding all virtual packages
with a single provider, there are literally thousands of source packages for
which their first alternative is a virtual package. Is this "policy" documented
s
On Thu, 20 Oct 2022 at 13:40:56 +0200, Johannes Schauer Marin Rodrigues wrote:
> > Most package managers (including APT, as of 2011-02-21) do not know to
> > replace the old with the new one and will only use the new package if it is
> > installed for some other reason.
>
> That is a rather old ti
Quoting Philipp Kern (2022-10-20 14:29:13)
> On 20.10.22 13:40, Johannes Schauer Marin Rodrigues wrote:
> > Quoting Andreas Henriksson (2022-10-20 12:13:24)
> >> Cannot be used for packages that are used in build dependencies, as several
> >> build tools (like sbuild) do not support virtual package
On 20.10.22 13:40, Johannes Schauer Marin Rodrigues wrote:
Quoting Andreas Henriksson (2022-10-20 12:13:24)
Cannot be used for packages that are used in build dependencies, as several
build tools (like sbuild) do not support virtual packages in those
dependencies by design, to guarantee determin
Quoting Andreas Henriksson (2022-10-20 12:13:24)
> Hello Debora Babb,
>
> On Wed, Oct 19, 2022 at 11:04:35PM -0700, Debora Velarde Babb wrote:
> > Greetings,
> >
> > The upstream package for tss2 has been renamed ibmtss. When the name
> > was changed upstream, the version number convention also
Hello Debora Babb,
On Wed, Oct 19, 2022 at 11:04:35PM -0700, Debora Velarde Babb wrote:
> Greetings,
>
> The upstream package for tss2 has been renamed ibmtss. When the name
> was changed upstream, the version number convention also changed.
> Upstream tss2-1470 was updated to ibmtss-1.3.0. Th
Hi Debora,
Quoting Debora Velarde Babb (2022-10-20 08:04:35)
> The upstream package for tss2 has been renamed ibmtss. When the name was
> changed upstream, the version number convention also changed. Upstream
> tss2-1470 was updated to ibmtss-1.3.0. The current version of ibmtss is now
> 1.6.0.
On Wed, 2022-10-19 at 23:04 -0700, Debora Velarde Babb wrote:
> Initially I attempted to create the package with the new name ibmtss.
> There was some discussion on debian-mentors list and the response was
> that I should NOT change the name to ibmtss and instructed to instead
> use an epoch numbe
Greetings,
The upstream package for tss2 has been renamed ibmtss. When the name
was changed upstream, the version number convention also changed.
Upstream tss2-1470 was updated to ibmtss-1.3.0. The current version of
ibmtss is now 1.6.0. I believe I need to use an epoch number to handle
the ve
10 matches
Mail list logo
