On Mon, Feb 04, 2019 at 02:39:16PM +0100, Markus Wanner wrote:
> On 2/3/19 10:51 PM, Josip Rodin wrote:
> > If it's an upstream issue that can't be fixed with packaging, then
> > tag it upstream and forward it, as the fine manual teaches you to.
>
> Well, I think of it as a feature, not a bug, so
On 2/3/19 10:51 PM, Josip Rodin wrote:
> If it's an upstream issue that can't be fixed with packaging, then
> tag it upstream and forward it, as the fine manual teaches you to.
Well, I think of it as a feature, not a bug, so I see no reason to
forward anything. Think of authlib as a general abstr
On Sat, Feb 02, 2019 at 09:39:25PM +0100, Markus Wanner wrote:
> I fear that's not possible, as it would mean splitting the library
> itself. Please speak up if you have ideas or wishes on what the
> packaging could do to improve your use case. Otherwise, I'll close this
> issue.
If it's an upst
Control: -1 tags +wontfix
Hello Josip,
On 6/4/18 2:16 PM, Josip Rodin wrote:
> For some reason there exists an expect script in
> /usr/lib/courier/courier-authlib/authsystem.passwd
> which seems to be calling passwd(1),
> which causes courier-authlib to depend on expect(1),
> which in turn has a
Package: courier-authlib
Hi,
For some reason there exists an expect script in
/usr/lib/courier/courier-authlib/authsystem.passwd
which seems to be calling passwd(1),
which causes courier-authlib to depend on expect(1),
which in turn has a bunch of other dependencies,
which in turn gets installed
5 matches
Mail list logo
