On Saturday, 22 December 2018 9:03:34 AM AEDT Oibaf wrote:
> The package fuse3 is available since awhile in sid/buster.
> Their users however are still using old fuse (v2), e.g. sshfs-fuse.
> According to this:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
> fuse3 is not co-installable
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
* Package name: erlang-horse
Version : 0+git20161117.0.4dc81d4
Upstream Author : Loïc Hoguin
* URL : https://github.com/ninenines/horse
* License : ISC
Programming Lang: (Erlang)
Description: Erlang
On Fri, 21 Dec 2018, Dmitry Bogatov wrote:
> I propose to replace current approach with update-alternatives(1)
[…]
> Opinions?
No. update-alternatives is too fragile to handle things like
/bin/sh and init(8).
Also, what Josh Triplett said.
The packages you cited are basically just the hooks to
Josh Triplett ha scritto:
> sysvinit works similarly, with /lib/sysvinit/init
This was in Jessie, but I don't see any /lib/sysvinit/init in Stretch nor
in Sid,
it's /sbin/init now, am I wrong?
Dmitry Bogatov wrote:
>I propose to replace current approach with update-alternatives(1)
>approach. By
The package fuse3 is available since awhile in sid/buster.
Their users however are still using old fuse (v2), e.g. sshfs-fuse.
According to this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
fuse3 is not co-installable with fuse, but a patch is available.
So is there a chance this get
Package: wnpp
Severity: wishlist
Owner: Ruben Undheim
* Package name: python-ifaddr
Version : 0.1.6
Upstream Author : Stefan C. Mueller
* URL : https://pypi.org/project/ifaddr/
* License : MIT
Programming Lang: Python
Description : Pure Python implement
Package: wnpp
Severity: wishlist
Owner: Ruben Undheim
* Package name: python3-zeroconf
Version : 0.21.3
Upstream Author : Jakub Stasiak
* URL : https://github.com/jstasiak/python-zeroconf
* License : LGPL-2.1+
Programming Lang: Python-3
Description : Pu
On Fri, Dec 21, 2018 at 11:31:24AM -0800, Josh Triplett wrote:
> Dmitry Bogatov wrote:
> > Currently, init system packages (sysvinit-core, runit-init,
> > systemd-sysv) are mutually exclusive -- each of them provides,
> > among other, /sbin/init file and as such, conflicts with rest.
> >
> > This
Dmitry Bogatov wrote:
> [ I am not subscribed. Please keep me in CC. ]
[I'm assuming that CCing the various init system @packages.debian.org
addresses suffices?]
> Currently, init system packages (sysvinit-core, runit-init,
> systemd-sysv) are mutually exclusive -- each of them provides,
> among
[ I am not subscribed. Please keep me in CC. ]
Currently, init system packages (sysvinit-core, runit-init,
systemd-sysv) are mutually exclusive -- each of them provides,
among other, /sbin/init file and as such, conflicts with rest.
This scheme has following drawbacks:
* switching between init
Package: wnpp
Severity: wishlist
Owner: Andrej Shadura
* Package name: intellij-openapi
Version : Git
Upstream Author : JetBrains s.r.o.
* URL :
https://github.com/JetBrains/intellij-community/tree/master/java/openapi
* License : Apache-2.0
Programming Lang:
11 matches
Mail list logo