Re: I resigned in 2004
Russ Allbery writes: > The general principle that I would advocate for here, though, is that if > someone says clearly and explicitly "never contact me again," we should do > what we can to never contact them again. If the message would be signed I'd agree, but for a non-signed message that would open abuse potential. I wouldn't like to find out I've been retired from Debian because someone faked a message like that in my name...
Bug#921076: ITP: pound -- reverse proxy, load balancer and HTTPS front-end for Web servers
Package: wnpp Severity: wishlist Owner: Carsten Leonhardt * Package name: pound Version : 2.8 Upstream Author : Robert Segall * URL : http://www.apsis.ch/pound/ * License : GPL with OpenSSL exemption Programming Lang: C Description : reverse proxy, load balancer and HTTPS front-end for Web servers Pound was developed to enable distributing the load among several Web-servers and to allow for a convenient SSL wrapper for those Web servers that do not offer it natively. Pound can also issue HTTP redirects. This is to reintroduce pound into the archive after it had been removed in February 2018. The problem had been that it didn't build with OpenSSL 1.1, but patches exist now. If the previous maintainer (Cc'ed) is still interested, I suggest a co-maintainership.
Recreating history of a package (was: Re: Reusing source package name of long-removed, unrelated package)
Ian Jackson writes: > There are utilities that will download all revisions of a particular > package from snapshot.d.o and make them into a combined history. Would you care to name those you know of? I have been searching for something like that but I didn't find anything useful. Regards, Carsten
Re: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]
Luca Boccassi writes: > Defaults are defaults, they are trivially and fully overridable where > needed if needed. Especially container and VM managers these days can > super trivially override them via SMBIOS Type11 strings or > Credentials, ephemerally and without changing the guest image at all. That argument goes both ways and I prefer safe defaults. What you/upstream propose are unsafe defaults, as was shown by several comments in this thread. Whoever wants the unsafe defaults of deleting old files and risking OOM situations can than "trivially and fully override" the safe defaults.
Bug#962918: ITP: bacula-libs3 -- S3 library for Bacula
Package: wnpp Severity: wishlist Owner: Carsten Leonhardt * Package name: bacula-libs3 Version : 0~20200523 Upstream Author : Bryan Ischo , modified by Bacula Systems * URL : https://www.bacula.org/downloads/ * License : LGPL 3+ Programming Lang: C Description : S3 library for Bacula This is a C library to access S3 storage with Bacula. This version is modified version of libs3 and maintained by Bacula Systems to work with Bacula. We, the Debian Bacula Packaging Team are packaging and will be maintaining this as an enhancement for Bacula. The possibility to use S3 storage is often asked about on the Bacula mailing lists and is also mentioned in #928343. To not get in the way of the libs3 package, we plan to use a private location for the library.
Re: Proposal: use /usr/bin/open as an alternative for run-mailcap and others.
(Re-added Charles to Cc as he asked in his original mail) Andreas Metzler writes: > On 2020-10-07 Charles Plessy wrote: >> Hello everybody, hello Debian freedesktop.org maintainers, > >> /bin/open has been kindly freed a couple years ago (#732796) and I would >> like to propose to repurpose it as a standard command for opening files, >> like on Mac OS and NextStep before it. > [...] > > I do not get the reason for this change. Surely we do not expect > people to manually type > > open penguin.jpeg > > in an xterm window, because they do not know how to handle the file. > They will usually *klick* on it and some infernal magic will invoke the > correct program, be it named xdg-open or geeqie. Not everybody is an expert, and I think the proposal is for the benefit of those that don't or don't want to know/remember the invocation of the right program for every specific data format and using a short, easy-to-remember name for this purpose. And Re: Stephan's mail: if you want to use a specific program to handle your data for a specific purpose, "open" is not intended for your use case. I'd say you can safely ignore it. Regards, Carsten
Re: Is missing SysV-init support a bug?
Robert Edmonds writes: > I would guess that the vast majority of folks still using sysvinit with > Debian are running wheezy or older, and thus removing sysvinit scripts > from packages in unstable wouldn't affect them. But maybe that still > leaves a reasonable number of testing/unstable + sysvinit users. Considering the past conflicts on the topic of systemd, it should be expected that there is a considerable user base that is staying with sysvinit or another alternative. - Carsten
Re: OpenSSL 1.1.0
Ian Jackson writes: > Reading that bug I think it's a shame that we didn't manage to > effectively identify the issues we've now discussed here on -devel > earlier, despite Kurt's several messages to d-d-a. Concerns were already raised in June, in the subthread starting here: https://lists.debian.org/debian-devel/2016/06/msg00501.html but they were not responded to. - Carsten
Re: intended MBF: wrong redirections in maintainer scripts
Hi, > as announced in our talk at debconf'18 [1] we intend a MBF about wrong > redirections in maintainer scripts. In general these are of the form > > foo 2>&1 1> /dev/null > > Here it was probably intended to send both stderr and stdout to /dev/null. > In reality the effect of this is to send only 1 to /dev/null, and to send > 2 to the file that 1 was sent to before that line. when you file bugs, please also include a correct example. Looking at your talk this seems to be: foo >/dev/null 2>&1 Thanks, Carsten
Re: systemd, ntp, kernel and hwclock
Daniel Pocock writes: > On 27/02/17 21:26, Ben Hutchings wrote: >> But ntpd is also known to have a large amount of code written >> without as much regard for security as one would hope. It seems >> like an unnecessary risk for most systems. > Thanks for that security tip, I'm tempted to get rid of some ntpd > instances now, however a few more questions come to mind before I rush in: Have a look at openntpd, that's coded with security in mind. - Carsten
Re: Whether remotely running software is considered "software" for Debian.
Bernd Zeimetz writes: > On 08/12/2017 07:35 PM, Marco d'Itri wrote: >> On Aug 12, "Dr. Bas Wijnen" wrote: >> >>> Which would be a great example of software that is free interacting with >>> software that is non-free. Thus the package with this as its main purpose >>> should live in contrib. There's nothing wrong with that. >> There is no such requirement for Debian packages and there has never >> been one. >> This was settled about 15 years ago, discussing ICQ clients. >> Even RMS agreed. > > Also nobody will stop you from writing your own server for a protocol > which is implemented by a client. Also nobody stops you from changing > the client code to work with a different/similar kind of server you've > implemented. > > So it is free software, please move on. Mind you, all the software contained in main and contrib's packages is free software. The question is into which of main and contrib the software under discussion should go. Actually, I haven't seen anyone citing the following part of policy 2.2.1: "None of the packages in the main archive area require software outside of that area to function." If we agree that "functioning software" does more than print an error or a usage note, this part makes it rather clear where free client software to non-free server software belongs. In another message Tollef writes about a software's or service's usefulness. That's orthogonal to classification into main, contrib and non-free.
Bug#807242: ITP: bacula-fd5.2 -- legacy bacula file daemon
Package: wnpp Severity: wishlist Owner: Debian Bacula Team * Package name: bacula-fd5.2 Version : 5.2.13 Upstream Author : Kern Sibbald * URL : http://www.bacula.org * License : Mainly GPL, parts LGPL, BSD and others. See http://www.bacula.org/git/cgit.cgi/bacula/tree/bacula/LICENSE?h=Branch-5.2 Programming Lang: C, C++ Description : legacy bacula file daemon Bacula is a set of programs to manage backup, recovery, and verification of data across a network of computers of different kinds. . The file daemon has to be installed on the machine to be backed up. It is responsible for providing the file attributes and data when requested by the Director, and also for the file system-dependent part of restoration. . This package is intended for machines that are backed up from another machine by an older bacula-director (5.x). Once the bacula-director has been upgraded, this package should be replaced by the regular bacula-fd. Bacula directors 5.x and bacula file daemons 7.x aren't compatible, so this package is intended for backup clients on sites where the backup-server is running an older debian release than the client, or don't want to use eventual backported newer bacula packages. This is to address concerns raised in bugs #805306 and #806205. (resent to debian-devel as I missed adding it manually in Cc)
Re: bat: 3 different programms and one name
Michael Biebl writes: > Am 04.02.2016 um 12:06 schrieb Elimar Riesebieter: >> that the upload of alsa-utils/1.1.0-2 doesn't fix the name conflict >> in bacula-console-qt and bareos-bat! > > Please file a bug against the two packages to get this sorted out. No need, bareos-bat conflicts with bacula-console-qt. Bareos is a fork of Bacula.
