On 14.03.20 22:41, Roberto C. Sánchez wrote:
> On Sat, Mar 14, 2020 at 09:18:48PM +, Neil McGovern wrote:
>> Hi debian-project and ftpmaster folks,
>>
>> On Sat, Mar 14, 2020 at 01:37:59PM -0700, Sean Whitton wrote:
>>> - cope well with flames in response to your decisions
>>
>>> - after tr
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry
* Package name: metview-python
Version : 1.1.2
Upstream Author : European Centre for Medium-Range Weather Forecasts (ECMWF)
* URL : https://github.com/ecmwf/metview-python
* License : Apache-2
Program
Witaj,
Kiedy jest najlepszy moment na organizację pracy, przygotowanie nowych akcji do
Klientów, dotarcie do nowych firm i osób? Właśnie teraz - teraz jest wreszcie
czas na zaplanowanie tych działań. I jest to także najwyższy czas, bo jak
wszystko wróci do normy to będzie już za późno.
Nie sz
Hello!
I would like to suggest to replace vim-tiny with nano as the default minimal
editor installed with debootstrap and therefore debian-installer.
The rationale behind that suggestion is that the vim package is becoming more
and more complex and hence more prone to build failures as can be see
On Sat, Mar 14, 2020 at 05:41:38PM -0400, Roberto C. Sánchez wrote:
> The fact is that given the length of time packages can wait for NEW
> processing and the amount of effort package maintainers put into
> packaging, it is understandable that they would be frustrated at the
> rejection of a packa
On 16.03.20 11:06, John Paul Adrian Glaubitz wrote:
> I would like to suggest to replace vim-tiny with nano as the default minimal
> editor installed with debootstrap and therefore debian-installer.
+1
On Mon, 16 Mar 2020 at 11:06:11 +0100, John Paul Adrian Glaubitz wrote:
> Thus, my suggestion would be to replace vim-tiny with nano in the list of
> essential packages
Neither vim-tiny nor nano is Essential.
They are currently both Priority: important, which I think means
debootstrap will usuall
Hi Scott,
On Sat, Mar 14, 2020 at 10:43:33PM +, Scott Kitterman wrote:
> As long as there are people involved, a certain amount of it is
> inevitable. Putting it in the requirements is bowing to reality. The
> FTP Team sometimes has to make unpopular decisions and it's inevitable
> that peop
On Mar 16, Simon McVittie wrote:
> `busybox vi` is rather limited, but is reasonable as an editor of last
> resort; busybox is smaller than either nano or vim-tiny; full systems
Agreed: this is a very good idea since I really think that every default
install must provide something enough vi-comp
On Mon, 16 Mar 2020 at 12:29:51 +0100, Marco d'Itri wrote:
> On Mar 16, Simon McVittie wrote:
>
> > `busybox vi` is rather limited, but is reasonable as an editor of last
> > resort
>
> Agreed: this is a very good idea since I really think that every default
> install must provide something enou
John Paul Adrian Glaubitz wrote:
> I would like to suggest to replace vim-tiny with nano as the default minimal
> editor installed with debootstrap and therefore debian-installer.
Would you consider nvi as an alternative to vim-tiny? It is quite small
and is functional enough to edit the occasiona
On 16.03.20 12:29, Marco d'Itri wrote:
> On Mar 16, Simon McVittie wrote:
>
>> `busybox vi` is rather limited, but is reasonable as an editor of last
>> resort; busybox is smaller than either nano or vim-tiny; full systems
> Agreed: this is a very good idea since I really think that every default
On Mar 16, Tomas Pospisek wrote:
> > Agreed: this is a very good idea since I really think that every default
> > install must provide something enough vi-compatible.
> I'd disagree. vi is very newbie unfriendly. OTOH I expect people that
Even if this were true (using vi is one of the most basic
On Mar 16, Thomas Pircher wrote:
> Would you consider nvi as an alternative to vim-tiny? It is quite small
Maintainer: Debian QA Group
Installed-Size: 1.605 kB
I think that busybox still wins.
> A user who does a lot of editing will probably install a better editor
> than {vim-tiny,nvi} anyway
Hi Thomas!
On 3/16/20 12:31 PM, Thomas Pircher wrote:
> John Paul Adrian Glaubitz wrote:
>> I would like to suggest to replace vim-tiny with nano as the default minimal
>> editor installed with debootstrap and therefore debian-installer.
>
> Would you consider nvi as an alternative to vim-tiny? I
Hi,
John Paul Adrian Glaubitz 于2020年3月16日周一 上午8:15写道：
>
> Hi Thomas!
>
> On 3/16/20 12:31 PM, Thomas Pircher wrote:
> > John Paul Adrian Glaubitz wrote:
> >> I would like to suggest to replace vim-tiny with nano as the default
> >> minimal
> >> editor installed with debootstrap and therefore deb
Boyuan Yang wrote:
> At least someone please adopt nvi first... we cannot introduce a
> package into d-i without a maintainer [2].
>
> Besides, nvi does not have an active upstream.
Ack; or use busybox, as others suggested in the thread.
On 2020-03-16 12:42 +0100, Marco d'Itri wrote:
> On Mar 16, Thomas Pircher wrote:
>
> > Would you consider nvi as an alternative to vim-tiny? It is quite small
> Maintainer: Debian QA Group
> Installed-Size: 1.605 kB
>
> I think that busybox still wins.
If we are thinking about minimal editors
Hello,
I am requiring your mentorsip help to publish this package.
I have received some feedback from Adam, but not much since then. Our
discussion about the package can be followed on the ITP bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952954
The package has been released to -2 Debia
Hi Wookey,
On Mon, Mar 16, 2020 at 01:02:47PM +, Wookey wrote:
> If we are thinking about minimal editors, zile is a good candidate: no
> deps, remarkably small and functional.
The main advantage of nano over vi and zile is that it shows you how to
save and exit, always, so it is a safe choi
On Mon, 16 Mar 2020 at 08:28:19 -0400, Boyuan Yang wrote:
> P.S. Anyone know why we did not use the vanilla vi at the very beginning?
Bill Joy's AT&T Unix vi wasn't Free Software when Debian started, so
1990s Debian had to use a Free clone like elvis, nvi or vim. According
to Wikipedia, the BSDs u
Hi
I am building debian disk images for the Vagrant tool, distributed at
https://app.vagrantup.com/debian/
For extended functionality, I build some of the disk images with a
package from contrib, namely virtualbox-dkms
Due to having this virtualbox-dkms from contrib, the disk images are
labelled
On Mon, 16 Mar 2020 12:45:35 +0100, Marco d'Itri wrote:
>On Mar 16, Tomas Pospisek wrote:
>
>> > Agreed: this is a very good idea since I really think that every default
>> > install must provide something enough vi-compatible.
>> I'd disagree. vi is very newbie unfriendly. OTOH I expect people
On Mon, 16 Mar 2020 18:25:17 +0100
Emmanuel Kasper wrote:
> Am I right in keeping these disk image as "contrib", or I am
> overcomplicating by keeping these multiple disk image builds ?
Yes, this seems logical. It matches how we handle other packages; if it
requires non-free to build, then it's
On 16/03/2020 12:15, John Paul Adrian Glaubitz wrote:
Hi Thomas!
On 3/16/20 12:31 PM, Thomas Pircher wrote:
John Paul Adrian Glaubitz wrote:
I would like to suggest to replace vim-tiny with nano as the default minimal
editor installed with debootstrap and therefore debian-installer.
Would yo
"Andrew M.A. Cater" writes:
> +1 for nvi - it's a very good editor of last resort.
nvi is orphaned both upstream and in Debian and is quite buggy (probably
all minor stuff or less common stuff like non-ASCII support, but I
wouldn't count on it given the code). I would not recommend it unless
so
On Mon, Mar 16, 2020 at 01:02:47PM +, Wookey wrote:
> I hadn't realised how fat nano is (not the only consideration of
> course, but zile is very good on this measure and surprisingly
> functionfull).
You are comparing apples with oranges! The nano package comes with a lot
of help files and t
so maybe we just add nano-tiny as an option to vim-tiny.
because we understand vim is not newbie friendly, but for all the old
hands, nano is not friendly to us.
234K is a small price to pay.
On Mon, Mar 16, 2020 at 7:27 PM Guus Sliepen wrote:
> On Mon, Mar 16, 2020 at 01:02:47PM +, Wookey w
On Mon, Mar 16, 2020 at 11:06:11AM +0100, John Paul Adrian Glaubitz wrote:
> The rationale behind that suggestion is that the vim package is becoming more
> and more complex and hence more prone to build failures as can be seen from
> the current build logs [1]
I'd love any help fixing the test fa
Package: wnpp
Severity: wishlist
Owner: Diane Trout
* Package name: python-get-version
Version : 2.1
Upstream Author : Philipp Angerer
* URL : https://github.com/flying-sheep/get_version
* License : GPL-3+
Programming Lang: Python
Description : A versi
Package: wnpp
Severity: wishlist
Owner: Diane Trout
* Package name: legacy-api-wrap
Version : 1.2
Upstream Author : Philipp Angerer
* URL : https://github.com/flying-sheep/legacy-api-wrap
* License : GPL-3+
Programming Lang: Python
Description : Legacy
On Mon, Mar 16, 2020 at 07:40:40PM -0400, Peter Silva wrote:
> On Mon, Mar 16, 2020 at 7:27 PM Guus Sliepen wrote:
> > On Mon, Mar 16, 2020 at 01:02:47PM +, Wookey wrote:
> >
> > > I hadn't realised how fat nano is (not the only consideration of
> > > course, but zile is very good on this measu
On 3/16/20 12:25 PM, Emmanuel Kasper wrote:
> For extended functionality, I build some of the disk images with a
> package from contrib, namely virtualbox-dkms
Could you use KVM (and if necessary, libvirt) instead?
--
Richard
signature.asc
Description: OpenPGP digital signature
On 3/17/20 3:21 AM, James McCoy wrote:
> On Mon, Mar 16, 2020 at 11:06:11AM +0100, John Paul Adrian Glaubitz wrote:
>> The rationale behind that suggestion is that the vim package is becoming more
>> and more complex and hence more prone to build failures as can be seen from
>> the current build lo
34 matches
Mail list logo
