On Sat, Dec 02, 2017 at 09:28:21PM +0500, Andrey Rahmatullin wrote:
On Sat, Dec 02, 2017 at 11:18:53AM +, Ian Campbell wrote:
On Sat, 2017-12-02 at 06:06 +0200, Victor Porton wrote:
> For this I need the upstream versions of "python2.7" and "xsltproc".
The upstream version of a Debian packa
On Sat, Dec 02, 2017 at 11:18:53AM +, Ian Campbell wrote:
> On Sat, 2017-12-02 at 06:06 +0200, Victor Porton wrote:
> > For this I need the upstream versions of "python2.7" and "xsltproc".
>
> The upstream version of a Debian package can be deterministically
> extracted from the package versio
On Sat, 2017-12-02 at 06:06 +0200, Victor Porton wrote:
> For this I need the upstream versions of "python2.7" and "xsltproc".
The upstream version of a Debian package can be deterministically
extracted from the package version, see https://www.debian.org/doc/debi
an-policy/#s-f-version for the fo
On Thu, 2017-11-30 at 12:15 +0100, Geert Stappers wrote:
> Control: tags -1 moreinfo
>
> On Thu, Nov 30, 2017 at 04:25:54AM +0200, Victor Porton wrote:
> > I am writing software which should call a program in specific
> > version range
> > (or fail to call it if the program in this version range i
Control: tags -1 moreinfo
On Thu, Nov 30, 2017 at 04:25:54AM +0200, Victor Porton wrote:
> I am writing software which should call a program in specific version range
> (or fail to call it if the program in this version range is not installed).
Please elaborate the problem you want to solve.
Gr
Package: general
Severity: wishlist
Dear Maintainers,
I propose to add new package header Upstream-Version: to contain the version
as of the upstream of the package.
The header should be optional because not every package has a definite
upstream version.
I am writing software which should call
6 matches
Mail list logo