Re: Proposal: plocate as standard for bookworm
On Sat, Feb 13, 2021 at 02:15:17PM -0800, Noah Meyerhans wrote: > On Mon, Feb 08, 2021 at 07:28:56PM +0100, Richard Hartmann wrote: > > I very dimly remember updatedb being a concern when cloud images were > > first discussed. Back then and today, agreed, it does not make sense > > there. > > Agreed, but we don't install all Priority: standard packages on the > cloud images anyway, and I don't see us going out of our way to add it > to them even if plocate is promoted to standard. > > > IMO, it makes sense on both servers and desktops, so rather than > > through tasksel, I would think it's a useful default to have on all > > non-virtual installations. > > Personally I'd rather leave it out of the default install, and I really > don't like the idea of running it on servers by default. First, the > additional IO may impact serving latencies. Second, because servers > (except maybe multi-user shell servers, but they're not the general > case) are purpose-built systems, and the locate utility really doesn't > contribute anything to the system's purpose. All locate variants are a PITA on servers, especially when virtualized. Imagine a 100+ VM hypervisor at 6:30 starting an updatedb job on all VMs in parallel. I debugged stuff like that for customers so yes - This problem is real. My ansible "essential" roles purge all variants of locate. Flo -- Florian Lohoff f...@zz.de signature.asc Description: PGP signature
how to deal with Google Spam on packagen...@packages.debian.org
Hi, some moron has subscribed a...@packages.debian.org to an arabic lanugage Google Group and the package tracker address is therefore swamped with multiple arabic messages per day. There is an unsubscribe link in the messages, but I refuse to create a Google Account for a...@packages.debian.org to be able to unsubscribe (the link leads to a page saying "You don't have permission to access this content - For access, try logging in"). Is it possible to have some filtering functions on @packages.debian.org mail addresses? Who is postmaster for that domain, who can I talk to to address this situation? N.B.: While @lists.debian.org has a pretty solid grasp on spam, really great work, a sizeable amount of my incoming spam that manages to get past my local spam filter comes via @packages.debian.org and @tracker.debian.org addresses. This is a general problem, the unresolvable subscription of package addresses to Google Groups is just the latest incarnation of this problem. Is there a possibilty for a general solution or maybe at least a pain reducing method? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: Proposal: plocate as standard for bookworm
On Fri, 19 Feb 2021 10:34:45 +0100, Florian Lohoff wrote: >All locate variants are a PITA on servers, especially when virtualized. >Imagine a 100+ VM hypervisor at 6:30 starting an updatedb job on all VMs >in parallel. I debugged stuff like that for customers so yes - This >problem is real. We really need such things to run from systemd-cron with a sufficient random spread to defuse this kind of load spikes in virtualized environments, yes. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
sudo RFA
Back in December, I put sudo up for adoption via WNPP. The response has been underwhelming. It was just pointed out to me that since I didn't actually post something explicit about this on debian-devel, some who might be willing and able to work on it perhaps are just unaware that it's up for adoption. Here's the relevant text from bug #976244: I took over the sudo package in August of 1996, and have maintained it since then. The package is in pretty good condition, with very reliable core functionality. Upstream is active and responds promptly to concerns. Despite this, there are a significant number of bugs open against the package, a fair number of which are related to the LDAP interface or other features I don't use, and just don't have the time, facilities, and/or motivation to work on. So, I think that after nearly a quarter century taking care of sudo in Debian, it's time someone else took over the package. Because this package is more or less "essential" to many users despite being marked as 'optional' in our packaging system, I'd like to suggest anyone considering taking it on look over the package, review the open bug list, and then reach out to me for some conversation before making a commitment to take it over. It would be ideal if someone adopts this before the bullseye release. Since I no longer routinely read debian-devel, please reply directly to me if you're interested. Regards, Bdale signature.asc Description: PGP signature
