Hi all,
As expected, we MiniDebConf Maceió organizers decided postpone the event.
We will wait to rescheduled it on the future.
Best regards,
Em 18/01/2020 16:39, Paulo Henrique de Lima Santana escreveu:
> Hi,
>
> Did you come to DebConf19 last year? It's time you come back, but now
> to know
Gunnar Wolf writes:
>> > Well, yes. But while mostly everybody who reads this will be
>> > moderately proficient with the basic subset of vi, I don't know
>> > anybody who'd know how to drive ed (I have done it, but I surely don't
>> > remember how to).
>>
>> It's not about the size of the editor
John Paul Adrian Glaubitz dijo [Tue, Mar 17, 2020 at 08:40:43PM +0100]:
> >> The only problem you mentioned was vim-tiny (arch: any) depending on
> >> vim-common (arch: all) and these sometimes getting out of sync on Debian
> >> Ports. I don't think that is a good reason to switch editors and ther
On 17.03.20 15:48, Wouter Verhelst wrote:
> Yes. I keep messing that up in production (ln is one of those commands
> that I continually need to read the man page of)
I suggest the `tldr` command for that...
*t
On 3/17/20 8:34 PM, Gunnar Wolf wrote:
> Ansgar dijo [Tue, Mar 17, 2020 at 09:49:49AM +0100]:
>> And Debian ships vim-tiny, not vim, as part of the minimal
>> installation. That the same source package also builds other versions
>> doesn't really matter for vim-tiny.
>>
>> The only problem you ment
Ansgar dijo [Tue, Mar 17, 2020 at 09:49:49AM +0100]:
> And Debian ships vim-tiny, not vim, as part of the minimal
> installation. That the same source package also builds other versions
> doesn't really matter for vim-tiny.
>
> The only problem you mentioned was vim-tiny (arch: any) depending on
>
Package: wnpp
Severity: wishlist
Owner: Diane Trout
* Package name: anndata
Version : 0.7.1
Upstream Author : 2017-8 P. Angerer, F. Alexander Wolf, Theis Lab
* URL : http://github.com/theislab/anndata
* License : BSD 3 clause
Programming Lang: Python
Descri
(I'm not subscribed to debian-devel, please keep me CC'ed)
> It seems to me that this is a large part of the problem here. DAK
> presumably has that feature for good reasons, and if the Ports archive is
> missing features that DAK has, the Ports is going to hit bad situations
> that the maintainer
Package: wnpp
Severity: wishlist
Owner: Timo Aaltonen
* Package name: freeipa-healthcheck
Version : 0.5
Upstream Author : Red Hat Inc.
* URL : https://github.com/freeipa/freeipa-healthcheck
* License : GPL3
Programming Lang: Python
Description : Health
[sorry for the late reply; catching up on email]
On Fri, Feb 21, 2020 at 04:23:15PM -0500, Anthony DeRobertis wrote:
> On 2/21/20 2:00 AM, Wouter Verhelst wrote:
> > Even so, if we want to do so, this can be done correctly by a preinst
> > script in new libc, by way of a script that does the follo
Geert Stappers wrote on 17/03/2020:
> 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
On Tue, 17 Mar 2020 at 10:10:22 +0100, John Paul Adrian Glaubitz wrote:
> And the issue with vim-common being out of sync is not trivially fixable
> with Debian Ports as we don't have the cruft feature that DAK has.
It seems to me that this is a large part of the problem here. DAK
presumably has t
Le 17/03/2020 à 07:26, Richard Laager a écrit :
> 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?
>
I do have KVM/libvirt
On 2020-03-17 07:36:23, John Paul Adrian Glaubitz wrote:
snip
> > As far as priorities, whatever the project/ftp-masters decide is fine
> > with me. I've wanted to drop vim-tiny altogther, but that's been met
> > with resistance.
>
> Sounds like dropping vim-tiny and replacing it with vi from b
On 3/17/20 9:49 AM, Ansgar wrote:
> John Paul Adrian Glaubitz writes:
>> And I assume, once we have fixed vim everywhere, it will be broken again
>> at some point due to the fact vim upstream is continuously adding features
>> which is why it's no longer suitable being an editor to be shipped in a
On Tue, Mar 17, 2020 at 11:50 AM Ansgar wrote:
> John Paul Adrian Glaubitz writes:
> > And I assume, once we have fixed vim everywhere, it will be broken again
> > at some point due to the fact vim upstream is continuously adding features
> > which is why it's no longer suitable being an editor to
John Paul Adrian Glaubitz writes:
> And I assume, once we have fixed vim everywhere, it will be broken again
> at some point due to the fact vim upstream is continuously adding features
> which is why it's no longer suitable being an editor to be shipped in a
> minimal installation.
And Debian shi
Hi Kurt,
On Tue, Mar 17, 2020 at 2:14 PM Kurt Roeckx - Debian Project Secretary
wrote:
> The platforms for all 3 the candidates are now avaiable at:
> https://www.debian.org/vote/2019/platforms/
You might mean: https://www.debian.org/vote/2020/platforms/ :)
Best,
Utkarsh
18 matches
Mail list logo
