I'm coming ☺️
On Wed, Aug 21, 2024 at 08:40:15PM +, weepingclown wrote:
> I believe at least some of these packages were probably packaged as
> dependencies for packaging lazygit. I am not sure which all, but I
> remember atleast gocui, pty and termbox-go to be needed by lazygit in
> one way or another. Ther
On Wed, Aug 21, 2024 at 08:40:15PM +, weepingclown wrote:
> Hi,
>
> I believe at least some of these packages were probably packaged as
> dependencies for packaging lazygit. I am not sure which all, but I remember
> atleast gocui, pty and termbox-go to be needed by lazygit in one way or
> a
Am Tue, Aug 20, 2024 at 11:09:31AM +0200 schrieb Helmut Grohne:
>
> I considered adding popcon to the criteria before hitting send. In the
> end, I opted for not including it based on my own cost/benefit analysis.
> While popcon may be a signal for the benefit-of-keeping aspect, it
> provides litt
Hi,
Am Tue, Aug 20, 2024 at 02:51:49PM +0900 schrieb Simon Richter:
> > enigmail
>
> Thunderbird has native GPG support now, including (well-hidden) support for
> calling into the installed gpg binary to use a smartcard.
>
> > mutextrace
>
> Oof, I should fix that finally, because in principle
Hi helmut,
+1
On 20-08-2024 07:28, Helmut Grohne wrote:
* As packages fail to migrate to testing for a long time, a release
team member eventually looks at the package.
I recognize myself here. But to be totally fair, that's *mostly* about
testing, and we have processes for that. Once
Hi Johannes and Bastian,
On Tue, Aug 20, 2024 at 10:35:47AM +0200, Bastian Venthur wrote:
> On 20.08.24 07:55, Johannes Schauer Marin Rodrigues wrote:
> > Hi,
> [...]
> > if I remember correctly, a package can also become a key package by having a
> > high-enough popcon value. If that is correct,
Hello Andrey,
On Wed, 21 Aug 2024 at 16:08, Andrey Rakhmatullin wrote:
> > I have also been wondering if we could take a different approach for
> > packaging libraries for language ecosystems that already have
> > packaging managers to play nicer with Debian packaging
> > maintainability. I find
Hi Salvo,
On Wed, 21 Aug 2024 at 16:19, Salvo Tomaselli wrote:
>
> > maintainability. I find myself when I need to use such libraries I
> > need to build my own bundle to support specific applications since
> > Debian packaged versions don't tend to work well with the application
> > (the same is
* Scott Kitterman [240820 14:35]:
> On August 20, 2024 12:16:47 PM UTC, Andrey Rakhmatullin
> wrote:
> >On Tue, Aug 20, 2024 at 12:12:33PM +, Scott Kitterman wrote:
> >> There are people doing this, we could use more, but it does
> >> happen. I've processed lots of these and it's virtually
On 21 August 2024 3:22:16 pm UTC, Nilesh Patra wrote:
>My last installation of Debian on a laptop was approximately 1.5 years ago and
>it was off by default. It asked me if I want to enable it or not.
>
>Did that change recently in D-I?
>
I don't think it did. I have had a bunch of reinstallation
Hi,
I believe at least some of these packages were probably packaged as
dependencies for packaging lazygit. I am not sure which all, but I remember
atleast gocui, pty and termbox-go to be needed by lazygit in one way or
another. There has been further work on packaging lazygit towards the end o
Noah wrote:
>On Tue, Aug 20, 2024 at 11:09:51AM +0200, Bastian Venthur wrote:
>> I think popcon does give a good approximation of how much percent of people
>> installed a certain package even if not everyone uses it, don't you agree?
>
>No, definitely not. There are hundreds of thousands of Debia
On Tue, Aug 20, 2024 at 11:09:51AM +0200, Bastian Venthur wrote:
> I think popcon does give a good approximation of how much percent of people
> installed a certain package even if not everyone uses it, don't you agree?
>
> Last time I installed Debian it was still enabled by default.
When was it
On Tue, Aug 20, 2024 at 11:09:51AM +0200, Bastian Venthur wrote:
> I think popcon does give a good approximation of how much percent of people
> installed a certain package even if not everyone uses it, don't you agree?
No, definitely not. There are hundreds of thousands of Debian systems
running
On Wed, Aug 21, 2024 at 03:39:11PM +0200, Héctor Orón Martínez wrote:
> I am surprised to not see more of those packages in the list, there
> are many packages in those ecosystems with popcon between 1-10 users.
popcon wasn't used when building this list though (even via the key
packages condition
Hello Helmut,
Thanks for starting this topic.
On Tue, 20 Aug 2024 at 07:29, Helmut Grohne wrote:
> golang-github-bsm-pool
> golang-github-coreos-go-tspi
> golang-github-crewjam-saml
> golang-github-form3tech-oss-jwt-go
> golang-github-go-redis-redis
> golang-github-jesseduffield-asciigraph
> go
On Wed, Aug 21, 2024 at 10:06:38AM +, Holger Levsen wrote:
> Hi,
>
> I also like us to remove more broken and unused packages from unstable.
>
> On Tue, Aug 20, 2024 at 11:20:10AM +0200, Lucas Nussbaum wrote:
> > Maybe we could also reduce the cost of removals for users and potential
> > new
Hi,
I also like us to remove more broken and unused packages from unstable.
On Tue, Aug 20, 2024 at 11:20:10AM +0200, Lucas Nussbaum wrote:
> Maybe we could also reduce the cost of removals for users and potential
> new maintainers, by improving the information provided in various places
> on how
Helmut Grohne left as an exercise for the reader:
> notcurses
i need decide whether i'm putting out a new upstream release
with ffmpeg 7 support, or whether i ought patch it in debian
(thanks to sebastian ramacher for originally bringing the issue
to my attention). i suppose i can do the latter no
Le Tue, Aug 20, 2024 at 07:28:52AM +0200, Helmut Grohne a écrit :
>
> please allow me to open a can of worms. Package removal from unstable.
Hi all,
I think that package removal from Unstable, total or partial (for
instance, 32-bit architectures) should be an automated self-sevice
system for lea
On August 20, 2024 12:16:47 PM UTC, Andrey Rakhmatullin wrote:
>On Tue, Aug 20, 2024 at 12:12:33PM +, Scott Kitterman wrote:
>> >Removing packages that aren't formally orphaned always sounds too bold to
>> >me, though it should be fine if we formalize a process (any process) for
>> >that.
>
On Tue, Aug 20, 2024 at 12:12:33PM +, Scott Kitterman wrote:
> >Removing packages that aren't formally orphaned always sounds too bold to
> >me, though it should be fine if we formalize a process (any process) for
> >that.
> >
> The process currently is file an rm but against ftp.debian.org for
On August 20, 2024 7:46:05 AM UTC, Andrey Rakhmatullin wrote:
>On Tue, Aug 20, 2024 at 07:28:52AM +0200, Helmut Grohne wrote:
>> please allow me to open a can of worms. Package removal from unstable.
>> Deciding when it is time to remove a package from unstable is difficult.
>> There may be use
Hi,
On 8/20/24 18:09, Bastian Venthur wrote:
That's what I thought too: we should somehow incorporate the popcon
value.
I disagree -- the users most affected by a removal are those who
automate installation, and those will not be running popcon.
Can you elaborate on that claim? I probably mi
Hi,
On 20/08/24 at 07:28 +0200, Helmut Grohne wrote:
> There are various QA-related teams looking at packages from other
> maintainers. When it trips a check, that often incurs time from some QA
> person investigating a report or failure. Examples:
> * Lucas Nussbaum, Santiago Vila and a few more
On 2024-08-20 Helmut Grohne wrote:
> Hi fellow developers,
> (modified resend, as first attempt didn't arrive)
> please allow me to open a can of worms. Package removal from unstable.
> Deciding when it is time to remove a package from unstable is difficult.
> There may be users still and it is
On Tue, Aug 20, 2024 at 11:09:51AM +0200, Bastian Venthur wrote:
> I think popcon does give a good approximation of how much percent of people
> installed a certain package even if not everyone uses it, don't you agree?
>
> Last time I installed Debian it was still enabled by default.
Was it?
(t
On 20.08.24 10:45, Simon Richter wrote:
Hi,
On 8/20/24 17:35, Bastian Venthur wrote:
That's what I thought too: we should somehow incorporate the popcon
value.
I disagree -- the users most affected by a removal are those who
automate installation, and those will not be running popcon.
Can y
Hi,
On 8/20/24 17:35, Bastian Venthur wrote:
That's what I thought too: we should somehow incorporate the popcon value.
I disagree -- the users most affected by a removal are those who
automate installation, and those will not be running popcon.
Popcon was introduced to determine which pac
On 20.08.24 07:55, Johannes Schauer Marin Rodrigues wrote:
Hi,
[...]
if I remember correctly, a package can also become a key package by having a
high-enough popcon value. If that is correct, maybe there should also be the
inverse. Looking at your list, about 85% of those packages have a popcon
Helmut Grohne:
Hi fellow developers,
(modified resend, as first attempt didn't arrive)
please allow me to open a can of worms. Package removal from unstable.
Deciding when it is time to remove a package from unstable is difficult.
There may be users still and it is unclear whether keeping the p
On Tue, Aug 20, 2024 at 07:28:52AM +0200, Helmut Grohne wrote:
> please allow me to open a can of worms. Package removal from unstable.
> Deciding when it is time to remove a package from unstable is difficult.
> There may be users still and it is unclear whether keeping the package
> imposes a cos
Hi,
On 20/08/2024 07:28, Helmut Grohne wrote:
[…]
What does a package cost?
[ a lot ]
What does package removal cost?
[…] Sometimes, packages are reintroduced. Doing so incurs a pass
through NEW (and review by the ftp team). […]
That’s the main reason why I usually keep packages around
Hi,
Quoting Helmut Grohne (2024-08-20 07:28:52)
> What do you think about the proposed criteria and suggested set of source
> packages? Is it reasonable to remove these packages from unstable? In a
> sense, it is extending the idea of the testing auto remover to unstable.
> Similarly, a package ca
Hi,
On 8/20/24 14:28, Helmut Grohne wrote:
enigmail
Thunderbird has native GPG support now, including (well-hidden) support
for calling into the installed gpg binary to use a smartcard.
mutextrace
Oof, I should fix that finally, because in principle a debugging layer
to find lock hiera
36 matches
Mail list logo
