Package: cupt
Version: 1.0.0~beta1
Severity: important
Hi, cupt fails to parse the following preferences file,
rendering the package unusable for me.
Package: ndisgtk
Pin: release unstable
Pin-Priority: 100
j...@hp:~$ sudo cupt update
W: attempt to set wrong option
On Wed, Sep 23, 2009 at 04:55:20PM +0300, Eugene V. Lyubimkin wrote:
Julian Andres Klode wrote:
Package: cupt
Version: 1.0.0~beta1
Severity: important
Hi, cupt fails to parse the following preferences file,
rendering the package unusable for me.
Package: ndisgtk
Pin:
On Wed, Sep 23, 2009 at 04:07:05PM +0200, Julian Andres Klode wrote:
On Wed, Sep 23, 2009 at 04:55:20PM +0300, Eugene V. Lyubimkin wrote:
Julian Andres Klode wrote:
Package: cupt
Version: 1.0.0~beta1
Severity: important
Hi, cupt fails to parse the following preferences file,
Julian Andres Klode wrote:
On Wed, Sep 23, 2009 at 04:55:20PM +0300, Eugene V. Lyubimkin wrote:
Julian Andres Klode wrote:
Hi, cupt fails to parse the following preferences file,
rendering the package unusable for me.
Package: ndisgtk
Pin: release unstable
Pin-Priority: 100
This is
On Wed, Sep 23, 2009 at 05:19:28PM +0300, Eugene V. Lyubimkin wrote:
Julian Andres Klode wrote:
On Wed, Sep 23, 2009 at 04:55:20PM +0300, Eugene V. Lyubimkin wrote:
Julian Andres Klode wrote:
Hi, cupt fails to parse the following preferences file,
rendering the package unusable for me.
package cupt libcupt-perl
reopen 548051
reassign 548051 libcupt-perl
tags 548051 + pending
thanks
Julian Andres Klode wrote:
It also fails at
Pin: release o=Debian, a=stable
which is clearly documented as well.
Ok, this is true positive. Fixed in master.
--
Eugene V. Lyubimkin aka JackYF,
Julian Andres Klode wrote:
Reading versionmatch.cc it seems that specifying
Pin: release unstable
means that either the codename or the archive is unstable. This probably
is not well-documented, but it is there.
Ok. So document it fairly in the next APT release and then ping me on IRC or
7 matches
Mail list logo
