Re: spohr.debian.org not sending email
Ryan Murray <[EMAIL PROTECTED]> writes: > exim treats 45x errors to be per host, rather than per address. That depends on when it gets the error. If exim gets a timeout or an error message after sending RCPT TO, it is treated as a recipient error, and not a host error. http://exim.org/exim-html-4.30/doc/html/spec_43.html#SECT43.2 -- Stig Sandbeck Mathisen <[EMAIL PROTECTED]> pgpgQvpKOU9ZV.pgp Description: PGP signature
Re: What's the best directory to put a local Debian repository?
Maurits van Rees <[EMAIL PROTECTED]> writes: > - /srv/debian > > According to the Filesystem Hierarchy Standard the /src dir is for > Data for services provided by this system, which seems to fit the > bill. /srv is a good place for local data which does not fit into any other hierarchy, so I'd go for /srv/debian. -- Stig Sandbeck Mathisen <[EMAIL PROTECTED]> pgpw5MjLrFY3P.pgp Description: PGP signature
Intent to package inorwegian, norwegian words for ispell. (and a bit about wnorwegian)
The subject says it all, I think. I've been in touch with the author, ([EMAIL PROTECTED]), and all that's left is the copyright document, and actually packaging the thing. :-) As for the norwegian wordlist "wnorwegian", I've been unable to produce a copyright, seems that this just evolved on the net. Does anyone know what to do? Will it be "safe" to package? -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpP2uRePN5ZP.pgp Description: PGP signature
Re: /usr/lib vs /usr/libexec
Russell Coker <[EMAIL PROTECTED]> writes: > Should we change some of these to /usr/libexec? Debian strives to follow the FHS (http://www.pathname.com/fhs), and this standard does not include /usr/libexec. See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146023, which mentions the use of /usr/lib/ for storing support binaries out of the way. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /usr/lib vs /usr/libexec
Miles Bader <[EMAIL PROTECTED]> writes: > I don't know if there's an argument for it other than clarity and > warm fuzzies. Not that there is anything wrong with warm fuzzies. I prefer that to a file hierarchy layout that gives me the chills. > [I personally think that if a good idea is "against the FHS", the > right answer is to change the FHS.] Since Debian's file system layout is based on FHS, that seems to be the "correct" way to change things. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Storage (was: Canonical and Debian)
Peter 'p2' De Schrijver <[EMAIL PROTECTED]> writes: > That sounds retarded in an age where a 200GB HD cost less then 100 > Euro... Regarding storage: "Fast, cheap and secure; pick any two". Good Storage have more costs than the price of the cheapest disks on the market. For a file server, especially a software mirror for Internet users, you'll want "fast" and "secure", you can't have "cheap". Sorry. :P -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Santiago Vila <[EMAIL PROTECTED]> writes: > Now that we have released sarge, I would like to ask debian-admin > and the Project Leader to consider seriously doing something to > reduce the level of spam we have to receive, store, and filter in > our @debian.org addresses. > > For example, we could use greylisting. Greylisting scales well. Combined with a liberal set of whitelisted clients, you also reduce complaints about greylisting. I've got experience with use of greylisting for a mail platform with over 1M accounts. Enabling greylisting for this platform reduced delivered spam with 80-90%. This is simply because most of the infected machines does not attempt a second delivery of a mail connection terminated with a 4xx (temporary) error message. For the MX for lists.debian.org, murphy.debian.org, which runs postfix, the "postgrey" daemon seems to run well, althoug I have not used this for large installations yet. master.debian.org runs exim, which also have greylisting > Or we could reject messages that are known to come directly from > trojanized windows machines acting as open proxies. Or even better, > we could do both things. sbl+xbl seems to have a list with a short timeout, for servers sending out spam, in addition to the ROKSO list. However, I would rather use this list inside SpamAssassin, instead of using just the list to deny SMTP connections. Also, any technical means used to reduce spam will be temporary, since spammers continuously adapt to changes in the environment they abuse to earn money. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Kalle Kivimaa <[EMAIL PROTECTED]> writes: > How many complaints for messages not delivered did you get? We whitelisted about every client we received mail from the past year, so the number of complaints was pretty low. If you also follow the logs closely for a while, you'll find a few sites you'll have to whitelist, particularly mailing list hosts. Greylisting without massive whitelisting _will_ give you complaints. > I do _not_ want to have my debian.org mail forwarding go through a > greylisting "service". I've had to deal with one too many user > complaints due to greylisting. If it is a configurable service, then > fine, other people may have different experiences, but if > greylisting becomes a mandatory feature, I guess I have to start > using non-greylisted (ie. non-Debian) addresses in my Debian > correspondence. Sounds like you've been a victim of a poorly implemented greylisting service. However, your idea of having a user-configurable greylisting would be a definite bonus. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Pierre Habouzit <[EMAIL PROTECTED]> writes: > I do. I know personnaly some admins of big MX (not necessarily ISPs, > french schools/universities in my case) that have a special rule for > domain that they know practicing greylisting, and that *force* the > delay to be of 30 to 60 minutes. and they increase that time if > their queue is big A novel, but not particularly clever use of greylisting. Those delays seem excessively big. >From experience, there only needs to be one 4xx message, and a short delay. 5 minutes is common, a few seconds is sufficient. Todays spambots do not try again after the first 4xx. However, this _will_ change, if enough sites start to greylist. Spammers adapt. > IMHO, rbls, SPF and others techniques that induce false positives > have to be used upside down : use the rbls, SPF, ... to clean > mail. that means, that a mail that is 100% correct wrt dnsRBLs, SPF > records, ... can come in. any other mail, then, can go through > "evil" treatments like greylisting. It's a way to select mails that > are suspicious, and let them be delayed. > > With that, it's quite easy to avoid greylisting if you are a real > ISP/MX/... : you only have to try to be removed from RBLs, or fix > your domain wrt SPF if you use it and use it badly. > > I've written a little postfix POLICY daemon that does what I > explained here. It's called whitelister, and it's in the > repo. Though, it has not been (AFAIK) used in a big queue, but I > plan to. These are sound ideas, and a piece of code is worth more than a thousand arguments. I'll give it a try. :D -- Stig Sandbeck Mathisen Linpro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Pierre Habouzit <[EMAIL PROTECTED]> writes: > I fully disagree, greylisting is really painful Since this is contrary to my experience with greylisting, I'd like to hear more about your experiences with it, and why you consider greylisting "really painful". I'm also interested in hearing about the size of the mail platforms you've used it on, and wether the mail platforms are list-heavy or user-heavy, and mostly incoming or outgoing traffic. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HashKnownHosts
On Jul 2, 2005, at 19:40, Olaf van der Spek wrote: On 7/2/05, Marco d'Itri <[EMAIL PROTECTED]> wrote: What is the rationale for changing the default setting? I find it very annoying, and from a brief discussion on #debian- devel I see that I'm not alone. What causes this annoyance? It looks like it will make the TAB hostname completion break, if you use bash_completion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Florian Weimer <[EMAIL PROTECTED]> writes: > On list servers, where most mail is outgoing? This would be really > suprising. Assume that the majority of the outgoing mail volume from a list server depends on incoming mail to this list server. If you reduce the incoming volume to this list server, there should also be less outgoing volume. One can also assume that delivering spam[0] to a will be more expensive than delivering non-spam, since some servers use delaying tactics when they receive the former. [0] - As decided by the receiving server. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382451: ITP: varnish -- High-performance HTTP accelerator
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen <[EMAIL PROTECTED]> * Package name: varnish Version : 0.9 Upstream Author : Varnish Project <[EMAIL PROTECTED]> * URL : http://varnish.projects.linpro.no/ * License : Two-clause BSD license Description : High-performance HTTP accelerator Varnish is a HTTP accelerator, also called "reverse proxy", that stores (caches) documents that have been requested over the HTTP protocol. Vanish is targeted primarily at the FreeBSD 6 and Linux 2.6 platforms, and will take full advantage of the advanced I/O features offered by these operating systems. -- System Information: Debian Release: 3.1 Architecture: i386 (x86_64) Kernel: Linux 2.6.12-11-amd64-k8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of inetd for etch
"Matthew R. Dempsky" <[EMAIL PROTECTED]> writes: > On Sat, Aug 12, 2006 at 10:21:50AM -0700, Steve Langasek wrote: >> We don't allow multiple mtas because a mail-transport-agent is >> *required* to provide /usr/sbin/sendmail. > > Why can Debian's alternatives system not alleviate this conflict? It could be done that way. The alternatives system provides the needed functionality to link the commands and files, but there is more. These are thoughts and ramblings on now to have two MTAs on a system. Let's call these the "system mta" and the "service mta". * The "system mta" should provide /usr/sbin/sendmail, as well as mailq, runq, and man pages. The alternative system is able to link several alternatives. We might want to add /usr/sbin/sendmail.system and /usr/sbin/sendmail.service, as well as corresponding mailq, runq, newaliases, man pages etcetera. * The "service mta" should provide a listening socket, on one or more specified IP addresses. I'm not sure if it's a good idea to bind to *:25. The "system mta" might need to bind to 127.0.0.1:25. * The "system mta" may use the "service mta" as a smarthost, mailhost, mail relay, or whatever you'd like to call it. When installing an MTA on Debian, the administrator is prompted for an installation profile, where "system mta" and "service mta" could be added. Problems: Having the same MTA as both system and service MTA may not be trivial. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of inetd for etch
Andreas Metzler <[EMAIL PROTECTED]> writes: > This seems to be totally overengineered. What, moreso than the exim4 configuration? :D (Ok, I've grown used to it, even like it. But at first, it seemed overengineered) > Having MTA a provide sendmail which uses MTA b for remote deliveries > is no common usage scenario on which any effort should be spent in > the Debian packaging infrastructure. Several antispam programs and daemons, available in Debian, use this technique explicitly to filter spam. They are just not seen as an MTA. Today, you often need to add a lot of configuration by hand to send mail off to tcp/10024 and accept from it at tcp/10025. > Actually the only sane explanation for wanting to install two MTAs I > ever heard of was "I am running X now and want to switch to Y. - I'd > like to test Y in the real system before going live." If you have only one box, and don't want to run vservers on it, it's one reason to have several MTAs installed. Your needs also depends on the number of servers (and sites) you have. Here are two scenarios off the top of my head. Service provider Mail is used extensively for reporting and perhaps even as an application data transport when running a large number of servers. Using one homogenous mail setup for all servers makes sense, perhaps less so if you just have a few servers, but when you have a couple of hundred, you have a _great_ need to keep things similar and predictable across all servers. You might need or want annoyance filters for the service provider mail, but you don't want anything to interfere with the system mail service. If one also provides mail service to a large number of customers and domains, you have another, different, type of mail server. If you have a homogenous system mail service, you could treat the provider mail service as just another application runing on this set of servers, listening on tcp/25 and friends. Special applications One may like running a mailing list manager like ezmlm, but don't want to expose qmail to the big, bad internet. (accept-then-bounce is not a good thing combined with brute force spam attempts). Then again, qmail might be too politically incorrect to care about, and there might not be enough mail service providers using Debian in order for this to be worthwile. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
planet.debian.net and DWN (was: HI, I am a honest user of China, I love linux especially Debian distribution , I think Debian is the greatest linux distribution , but nowdays, the debian weekly news w
Ron Johnson <[EMAIL PROTECTED]> writes: > IIRC, he sent an email out a few days ago saying that > http://planet.debian.net/ now serves most of the purpose of DWN. Unfortunately, at least for me, planet.debian.net contains an aggregation of more than just debian-related blog entries. planet.debian.org may contain what DWN originally did, but there is also a _lot_ of other things I'd rather not wade through to get at it. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
Andreas Metzler <[EMAIL PROTECTED]> writes: > This in an extreme setup, ...or a setup designed to be used as an argument against greylisting. -- Stig Sandbeck Mathisen <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
Jon Dowland <[EMAIL PROTECTED]> writes: > I suggest having __two__ lists: a wishlist and a worklist (with the > latter being the existing TODOlist) A decent idea, since items can be moved back and forth as needed. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lsb-base
Andreas Barth <[EMAIL PROTECTED]> writes: > It would be better if there would be some configureable option in > lsb-base. , | Angry Fruit Salad? | | [yes] [no] ` Anyway, I like the pretty colours. It makes it very easy to see if something is wrong during boot or service startup with just a glance. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Key replacement request for [EMAIL PROTECTED]
Junichi Uekawa <[EMAIL PROTECTED]> writes: > It seems like my mail is getting dropped somewhere for some reason. It's likely hiding somewhere, along with other keyring related mail. I've yet to see a reply to the mail I sent to keyring-maint 10 months ago. > I'm Cc'ing debian-devel so that I don't have to go and hunt for this > mail every month I decide to resend. debian-private might be a better place, I'm not sure. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Dogme05: Team Maintenance
"W. Borgert" <[EMAIL PROTECTED]> writes: > Sorry, if people thought I want to propose enforcement of "team > maintenance policy". However, team maintenance for all essential > and standard is worthwhile and not un-realistic. It's a good idea to discuss it, unless it's been discussed to death already. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unnecessary "Conflicts" with imap-server packages
On Aug 30, 2005, at 10:31, Brian May wrote: Would it be feasible to have something like "update-alternatives", but instead of managing files in the file system, it allocates port numbers? That way every service that listens on port, for example 143, will be registered, but only one will be "active" at one time. Please bear in mind that a single computer also can have a lot of IP addresses. For example, I can have apache2 on one address, and squid reverse proxy on another, both listening on the same port. -- SSM - Stig Sandbeck Mathisen <[EMAIL PROTECTED]> - http://fnord.no Trust the Computer, the Computer is your Friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Spam on this list
"Roberto C. Sanchez" <[EMAIL PROTECTED]> writes: > The problem is that being too restrictive on spam also means getting > more false positives. Therefore one must find out how much more restrictive one can be without getting too restrictive. :D -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: spam in wiki.debian.net
Carlos Parra Camargo <[EMAIL PROTECTED]> writes: > I've restored to the last revision all of them, is the first time > that happens? No, I did a "cleanup" of a group of pages a while ago, with new revisions with the spam content removed instead of reverting to earlier revisions. This means unfortunately that those revisions still exists with spam links, and would still be available from google. If you have decent logs, search for changes done by StigSandbeckMathisen. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: spam in wiki.debian.net
Benjamin Mesing <[EMAIL PROTECTED]> writes: > After having read this - wouldn't it be easier to report the user > doing the spamming, and simply reverting all changes done by this > user. There are a limited number of wiki which have this functionality. Neither the current nor the new wiki have that, as far as I know. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: localhost.localdomain
Gabor Gombas <[EMAIL PROTECTED]> writes: > Ok, after a quick googling I found that this bug has already been > reported for MySQL: http://bugs.mysql.com/11822 and is fixed in > MySQL 5.0.11. So if it bothers you, you should upgrade. Changing the canonical name of localhost is an arbitrary change that breaks more than MySQL. It also violates the principle of least astonishment. "We've changed something, we're not sure why, but it breaks MySQL. If it bothers you, you should upgrade MySQL" Nah, I don't think that is what we want to tell our users. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: localhost.localdomain
Pierre Machard <[EMAIL PROTECTED]> writes: > Anyway I do not understand why this issue is a problem since we > simply add an alias to localhost. Nobody say that we will remove > localhost and exchange it by localhost.localdomain. If what you wanted to do was to add an alias, you should have read the documentation on how to add an alias without changing the canonical hostname for 127.0.0.1. This documentation is available in hosts(5). # This manual page describes the format of the /etc/hosts file. This # file is a simple text file that associates IP addresses with # hostnames, one line per IP address. For each host a single line # should be present with the following information: # # IP_address canonical_hostname aliases Changing the canonical hostname changes the output of everything that resolves IP address, including "lsof" and "netstat". Any script or program dependent on this output need to be checked and possibly changed if it is to behave as it should. This includes local scripts created by our users. It should also be consistent with bind9, and I do _not_ think that changing bind is the correct way to do things. iostat:~# getent hosts 127.0.0.1 127.0.0.1 localhost.localdomain localhost iostat iostat:~# dig -x 127.0.0.1 @localhost ; <<>> DiG 9.2.4 <<>> -x 127.0.0.1 @localhost ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11671 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;1.0.0.127.in-addr.arpa.IN PTR ;; ANSWER SECTION: 1.0.0.127.in-addr.arpa. 604800 IN PTR localhost. ;; AUTHORITY SECTION: 127.in-addr.arpa. 604800 IN NS localhost. ;; ADDITIONAL SECTION: localhost. 604800 IN A 127.0.0.1 ;; Query time: 3 msec ;; SERVER: 127.0.0.1#53(localhost) ;; WHEN: Fri Oct 7 07:19:19 2005 ;; MSG SIZE rcvd: 93 -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: localhost.localdomain
Gabor Gombas wrote: Then fix those other broken things as well. Contrary to popular belief among our users, system administrators does not have access to every server on the internet. Therefore, I can not help you solve this issue in this way. Instead, I propose we return the content of the Debian /etc/hosts file to the way it was before the change. If you want localhost-style authentication, you _should_ do the comparison on the IP address rather than the resolved name for several reasons: [snip good reasons] I don't trust client address/name resolving for any authentication of clients. I resent the implication that I do. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: localhost.localdomain
Thomas Hood wrote: OK, I have modified netcfg so that it writes 127.0.0.1localhost to /etc/hosts. Excellent. Thank you. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Bug#334632] Your message to Pkg-openssl-devel awaits moderator approval
On Oct 22, 2005, at 10:04, Petter Reinholdtsen wrote: I maintain one such list on alioth, and I have not been able to find a way to let bug reports and other debian-related messages get into the lists unmoderated without also accepting a lot of spam. If you or anyone else can give me a recipe on how I can set up the list to avoid the moderation of bug messages, I am very interested. Mailman has a set of content filters, which decide what to do with messages if header or body matches a regexp string. I've mostly used it for tossing mail with the header "X-Spam: YES, ", but there's no reason you can't say that if the header or body matches "Package: ", it gets passed right on to the list members. So, you may not be able to identify what you don't want sent to the list, but you may be able to identify what you _want_ to be sent to the list without moderator intervention. -- SSM - Stig Sandbeck Mathisen <[EMAIL PROTECTED]> - http://fnord.no Trust the Computer, the Computer is your Friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is the Debian mail server healthy?
On Oct 30, 2005, at 10:52, Marc Haber wrote: I can confirm that master sits on some messages for days, such as this one, for example: |Received: from master.debian.org ([146.82.138.7]) |by torres.zugschlus.de with esmtp (Exim 4.54) |id 1EVmC6-lm-8a |for [EMAIL PROTECTED]; Sat, 29 Oct 2005 10:36:07 +0200 |Received: from qa by master.debian.org with local (Exim 3.35 1 (Debian)) |id 1EUOw2-0003y4-00; Tue, 25 Oct 2005 08:33:50 -0500 So, there might be a problem, because these things happen quite regularly in the last few weeks. That does not mean that master has not tried to deliver it to you during these days. Logs from master might shed some light over this issue. -- SSM - Stig Sandbeck Mathisen <[EMAIL PROTECTED]> - http://fnord.no Trust the Computer, the Computer is your Friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /var/www is depracated, which directory to use?
Holger Levsen writes: > http://lintian.debian.org/tags/dir-or-file-in-var-www.html nor > debian-policy is helpful to resolve this issue - so I would like to > discuss this here and come up with a good solution. > > Suggestions? No package may touch /srv, but we could perhahs recommend its usage in documentation or examples. The package should generate html and graphs somewhere in /var/lib/munin, possibly /var/lib/munin/html, and provide configuration examples for the most common web servers. A possible conflict: Munin uses /var/lib/munin as the root of its dbdir, and if someone makes a "html" domain for web servers, confusion may occur, as that directory will store both the RRD files for that domain, as well as the generated HTML. Moving old data: There should be no need to move old data. munin-graph should re-create missing graphs on the first run. munin-html updates all web pages every run. We'll add a notice to NEWS.Debian: ,[ NEWS.Debian ] | The munin web root default location has moved from /var/www/munin to | /var/lib/munin/html. To do this manually, you can: | | * Update "htmldir" in /etc/munin/munin.conf to point to | /var/lib/munin/html. | | * Add configuration to your web server, see fragments in | /usr/share/doc/munin/examples for your web server | | * Remove /var/www/munin when convenient. ` Configuration examples for common web servers: The following configuration fragments could be placed in /usr/share/doc/munin/examples/ This is for apache httpd. Add to /etc/apache2/conf.d/ to cover all virtual hosts, or include in a virtual host: ,[ /etc/apache2/conf.d/munin.conf ] | Alias /munin /var/lib/munin/html | | Order allow,deny | Allow from localhost 127.0.0.0/8 ::1 | Options None | ` For nginx, you will have to add the following to an existing virtualhost. nginx in sid has ipv6 support, and this was enabled in the upload yesterday, I guess an extra "allow ::1;" (or "allow [::1];") would do the trick. ,[ /etc/nginx/sites-enabled/default ] | location /munin { | alias /var/lib/munin/html; | allow 127.0.0.0/8; | deny all; | } ` For lighttpd, we need something like the following. Note that this acl example may not work with IPv6 enabled, since lighttpd does not do subnet matching on IPv6 (http://redmine.lighttpd.net/issues/385) ,[ /etc/lighttpd/conf-enabled/munin.conf ] | alias.url += ( "/munin" => "/var/lib/munin/html" ) | | $HTTP["url"] =~ "^/munin" { | $HTTP["remoteip"] != "127.0.0.0/8" { | url.access-deny = ( "" ) | } | } | ` -- Stig Sandbeck Mathisen pgpLlS9WfGa1A.pgp Description: PGP signature
Re: /var/www is depracated, which directory to use?
sean finney writes: > there is, it's called webapps-common[1]. unfortunately what *is* > missing is developers with time to put into maintaining it, which is > why it has not been uploaded or integrated with support for more httpd > services. That looks useful. What can I do to help? -- Stig Sandbeck Mathisen pgpjVAz7pxd5M.pgp Description: PGP signature
Re: /var/www is depracated, which directory to use?
Manoj Srivastava writes: > As I mentioned on IRC, look at trac. The trick is put configuration > files in /etc/munin/, and symlink it back into /var/lib/munin if munin > needs that. All munin needs is a place to write static html and png files. * /var/lib/munin is already used as top level for munin's data files. If we add a web root there, it may cause collisions. * /var/cache may not be the best place, since FHS says that data here can be deleted with little consequence, and the generated web pages will be gone until the next time munin-graph and munin-html runs. One could ask via debconf, and suggest /var/www/munin as a default, would that be acceptable? -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: /var/www is depracated, which directory to use?
Tom Feiner writes: > Is /var/cache really such a bad option? I mean, the entire web content > is re-generated from templates & graphs are re-generated from the rrd > databases every 5 minutes. So even if someone did delete the > directory, it'll just be recreated up to 5 minutes later. Apart from "it feels wrong", no. >> One could ask via debconf, and suggest /var/www/munin as a default, >> would that be acceptable? > > Users might not know a good answer such a question and will probably > just stick with the defaults, so suggesting /var/www/munin will just > keep the current non FHS complaint status quo. Ok, debconf question with /var/cache/munin/html as default, then. The admin then have the option to use /srv/foo/whatever or /var/www/munin. By debconf, we have a path which we'll add to /etc/munin/munin.conf, and to the web server configuration snippets. Should the web configuration be enabled by default? Assume apache2, and add configuration to /etc/apache2/conf.d/munin.conf? -- Stig Sandbeck Mathisen pgpSv2ogmer7z.pgp Description: PGP signature
Re: /var/www is depracated, which directory to use?
Mike Hommey writes: > * /usr/share/munin. Would not work well for variable data, I think. The graphs and HTML is updated every 5 minutes. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: /var/www is depracated, which directory to use?
Neil McGovern writes: > Have a read of > http://webapps-common.alioth.debian.org/draft/html/ch-httpd.html Useful, thanks. :) -- Stig Sandbeck Mathisen pgph88QZYVl0o.pgp Description: PGP signature
Re: /var/www is depracated, which directory to use?
Tom Feiner writes: > Sorry for the newbie question (I'm not that familiar with debconf). > Will debconf be able to manage upgrade from current munin version? > Changing the current 'htmldir /var/www/munin' to the new user > specified one? Debconf asks questions and stores them. However, with the power of sed, you can do anything. :) > In phpmyadmin package they raise a debconf question, asking which web > server the user wants to configure phpmyadmin to run under (and they > give apache2,lighttpd options), maybe we can do the same in munin? > > Can you help me implement this for the munin 1.4~svn release for > debian experimental? Yes, I'll start looking at it tomorrow. -- Stig Sandbeck Mathisen pgprJ1xxt1YEf.pgp Description: PGP signature
Re: Installation of Recommends by default on October 1st
Neil Williams <[EMAIL PROTECTED]> writes: > And a script to implement that in every box I have to install. Again > and Again and Again and Puppet is > that way. If you have several machines, you may want to to handle them centrally anyway, and this is a good reason to start. You could begin with the following in /etc/puppet/manifests/site.pp: node default { include apt } class apt { file { "/etc/apt/sources.list": source => "puppet://puppet.example.com/common/apt/sources.list", notify => Exec["apt-get update"], } file { "/etc/apt/conf.d/install-recommends": content => 'APT::Install-Recommends "true";', notify => Exec["apt-get update"], } exec { "apt-get update": command => "/usr/bin/apt-get update", refreshonly => true, } } If you have more than one distribution, sprinkle lightly with variables and case statements. > You almost forcing me into maintaining a fork of apt that restores > the current behaviour from the very start. You may find that using your energies elsewhere may be a bit more rewarding in the long term. :P -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#435884: ITP: rsyslog -- enhanced multi-threaded syslogd
Pierre Habouzit <[EMAIL PROTECTED]> writes: > The syslog daemon shall not eat anymore than 0.01% of your CPU. That's just silly. :P For a cluster of syslog servers, the syslog daemon shall use whatever CPU time it needs. If it needs more than one CPU, and more than one CPU is available, then it's a good idea for the syslog daemon to use more than one CPU. You have multiple ways for logs to enter: 514/udp - the good old standard. /tcp - tcp syslog, queued on the client side, ensured on the server side, possibly encrypted if data passes external networks. local sockets, doors, etc... Logs may be filtered and classified according to priority, network, server group, application, or facility. You have several places where the log data will go: Disk Database Some analysis application Custom statistics software with realtime graphs. IDS (Big, horrible, expensive, java-thingy. Prints Pretty Pictures) Local antispam-daemons. > Why would you need to bloat it for god's sake? It reminds me of so > called network monitors that are so huge, that they mostly measure > their own fat. A multi-foo syslog daemon is just plain silly. Not if you run a large network, cluster, server group or if you're an internet service provider. If you get tens or hundreds of gigabytes of logs every day, you need a good framework. A mail service for just 1M users alone lots 1GB every few hours. Some of that is interesting, and everything must be kept for a while. For your own laptop? Naah, you can keep sysklogd, as it's probably good enough for your needs. Remember that Debian is used by more than just you, so calling the needs of others "silly" may be perceived as short-sighted. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#449335: ITP: libspread-ruby -- Ruby bindings for the Spread message bus client API
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen <[EMAIL PROTECTED]> * Package name: libspread-ruby Version : 2.0 Upstream Author : Neil Conway <[EMAIL PROTECTED]> * URL : http://rbspread.sourceforge.net/ * License : Perl Artistic License Programming Lang: Ruby Description : Ruby bindings for the Spread message bus client API rb_spread provides a set of Ruby bindings for the client API provided by the Spread Group Communication System. Spread is a toolkit that provides a messaging service across external or internal networks. Spread functions as a unified message bus for distributed applications, and provides application-level multicast and group communication support. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#588526: ITP: cpm -- Console Password Manager
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: cpm Version : 0.25.~beta-2 Upstream Author : Kacper Wysocki , harr...@eml.cc * URL : http://github.com/comotion/cpm * License : GPLv2+ Programming Lang: C Description : Console Password Manager This program is a ncurses based console tool to manage passwords and store them public key encrypted in a file - even for more than one person. The encryption is handled via GnuPG so the programs data can be accessed via gpg as well, in case you want to have a look inside. The data is stored as zlib compressed XML so it's even possible to reuse the data for some other purpose. The software uses CDK (ncurses) to handle the user interface, libxml2 to store the information, the zlib library to compress the data and the library GpgMe to encrypt and decrypt the data securely. Note: This supersedes bug #55, which is the old ITP for cpm. I'll close both when uploading. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100709105334.9035.52775.report...@fsck.linpro.no
Re: Bug#588526: ITP: cpm -- Console Password Manager
Peter Samuelson writes: > Why public key? That's useful if a certain class of people need to be > able to write but not read the file, or vice versa. It's the other way around. Anyone with write access to the location to the cpm directory used will be able to encrypt (changes to) the keyring so it is readable by a number of GnuPG keys belonging to, for instance, a group of system administrators. If the same class of people hold the private keys as well as the read/write permissions for the cpm directory, you have a shared and hopefully secure storage for passwords. > I can't figure out how that could be useful for a password manager. It would be impolite to agree here. :) > Aside from that, can it use or import password from 'pwsafe', > 'gnome-keyring' or 'kwallet'? Through a wetware bridge, sure. > Is there a reason this app isn't just a frontend to one or more of > those? Possibly, but I won't speculate about that. You should ask the author. The reason for looking at "cpm" was because it filled a need not satisfied by 'pwsafe', 'gnome-keyring' or 'kwallet', which was "shared, console-based storage for secret information". -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xsk3rsg5n@fsck.linpro.no
Bug#601966: ITP: nagios-plugin-check-multi -- run nagios checks as a group
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: nagios-plugin-check-multi Version : 0.24 Upstream Author : Matthias Flacke * URL : http://my-plugin.de/wiki/projects/check_multi/start * License : GPL Programming Lang: Perl Description : run nagios checks as a group This plugin can run other plugins, and present the results as a group, with a single status code reported back -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101031121044.27089.5779.report...@mavis.fnord.no
Re: Bug#601966: ITP: nagios-plugin-check-multi -- run nagios checks as a group
Marc Haber writes: > I have an internal package of this available and obviously forgot to > ITP it. Do you want to base your work on my preparations, or is your > project far enough that my work won't be of any help for you? I finished packaging before posting the ITP. The packaging I made is available at http://git.debian.org/?p=pkg-nagios/pkg-check_multi.git If you have extra documentation, configuration examples, or anything else you've done to complement the upstream software, I'd be happy to include this. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xy69arao6@fsck.linpro.no
Bug#605385: ITP: mod-gearman -- Distribute active Nagios checks across your network
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: mod-gearman Version : 0.8 Upstream Author : Sven Nierlein * URL : http://labs.consol.de/nagios/mod-gearman/ * License : GPL-3+, some BSD and GPL-2 Programming Lang: C Description : Distribute active Nagios checks across your network Mod Gearman provides a way of distributing active Nagios checks across your network. It consists of two parts: One part is a nagios event broker module which resides in the Nagios core. This module adds servicechecks, hostchecks and eventhandlers to a Gearman queue. There can be multiple equal gearman servers. The counterpart is one or more worker clients for the checks itself. These clients can be bound to host and servicegroups. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101129142448.5088.64735.report...@fsck.linpro.no
Re: enable/disable flags in /etc/default
Sean Finney writes: > imho i think we need to step back and re-think the entire way we're > currently handling init scripts, both from the packaging point of view > and from the end-user/admin point of view. Yes. There are two issues here. The "short term" issue is figuring out if the current practice of DONT_DISABLE_ENABLEMENT=false and friends in /etc/default is something we want to keep doing. The "long term" issue is having a toolset, for the end user, for starting and stopping services, enabling and disabling services when booting, installing and upgrading, and setting a global policy for what the initial status of an installed service should be. The end user wants to select which services start at boot, and also directly control (start,stop,restart,status,foo,bar) services, regardless of whether the service is set to be started at boot. Having the enable/disable functionality inside the /etc/default/example script ensures that the service does not start in any case, not even when started manually, or from another service manager. Just this fact would make it a poor solution. The package maintainer scripts will need a way to stop a service on uninstall or upgrade, and start after configuration, unless prevented by policy-rc.d. Currently, our packaged services start automatically, unless explicitly disabled in /etc/default/, or by missing configuration. Compare this to the policy of RHEL, which does not enable or start its services on package install. A RHEL service can be started manually, but will not be started at system boot unless explicitly configured to do so with "chkconfig". What I'd like to be able to do, is to set a policy after system install, and have all packages _obey_ this policy. :) -- Stig Sandbeck Mathisen ooo, shiny! pgpWObDPnfscO.pgp Description: PGP signature
Re: Disable ZeroConf: how to ?
Bastien ROUCARIES writes: > some package announce their existance to the world without any admin > decision It should be a site policy. > It is not a fud and a security hole! I disagree. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xmxlcs288@fsck.linpro.no
Re: Ruby changes for Wheezy
Philipp Kern writes: > On 2011-03-04, Stefano Zacchiroli wrote: >>=== Generation of ri and rdoc documentation === >> >> We decide not to generate the ri and rdoc documentation, as there are >> good online services providing it (like rdoc.info). We might change >> our mind later. :) > > Are you sure about that? Not that I do much Ruby nowadays, but for > other languages I find it incredibly helpful that there are actually > useful doc packages for the times when I'm disconnected from the net > (longer train sessions, lodges without internet access). Back then ri > was a very nice tool to lookup most functions you need. If ri and rdoc generation is handled by a post install hook, this hook can check a local configuration variable to generate documentation, or silently exit. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xbp1r5bef@fsck.linpro.no
Re: new scripts and patches for devscripts
Ian Jackson writes: > udt-* for all applicable *, where "udt" stands for "ubuntu-dev-tools". > [...] > udt-mk-sbuild This command creates a schroot with a named debian or ubuntu release, and adds a useful section to schroot.conf. Adding "udt-" does not make it any less misnamed. :) -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xvczrz2bt@fsck.linpro.no
Re: Switching the default /bin/sh to dash
Mike Hommey writes: > I'd say if /bin/sh points to the current default (/bin/bash), then it > should be modified. OTOH, if it was modified locally by the admin to > point somewhere else, leave it alone. That would potentially break locally written or installed scripts. Not touching the /bin/sh link on upgrade seems less harmful. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#769851: ITP: puppetlabs-spec-helper -- Ruby library for puppet module testing
Jordan Metzmeier writes: > * Package name: puppetlabs-spec-helper This is already packaged as https://packages.debian.org/sid/ruby-puppetlabs-spec-helper -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvdhyl7f@dagon.fnord.no
Re: Being part of a community and behaving
Shachar Shemesh writes: > Please try to refrain from jokes other will find offending. That joke is in very poor taste, sir. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87d28ln3av@dagon.fnord.no
Bug#669886: ITP: libdevel-pragma-perl -- helper functions for developers of lexical pragmas
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: libdevel-pragma-perl Version : 0.54 Upstream Author : chocolateboy * URL : http://search.cpan.org/dist/Devel-Pragma/ * License : Artistic or GPL-1+ Programming Lang: Perl, XS Description : helper functions for developers of lexical pragmas Devel:Pragma provides helper functions for developers of lexical pragmas. These can be used both in older versions of perl (from 5.8.1), which have limited support for lexical pragmas, and in the most recent versions, which have improved support. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421181852.25056.16549.report...@dagon.fnord.no
Bug#669887: ITP: libmethod-signatures-perl -- method and function declarations with signatures and no source filter
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: libmethod-signatures-perl Version : 2025 Upstream Author : Michael G Schwern * URL : http://search.cpan.org/dist/Method-Signatures/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : method and function declarations with signatures and no source filter Method::Signatures provides two new keywords, func and method, so that you can write subroutines with signatures, very similar to perl6 signatures. It also does type checking, understanding all the types that Moose (or Mouse) would understand. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421181851.25069.30592.report...@dagon.fnord.no
Bug#669888: ITP: libb-hooks-op-check-entersubforcv-perl -- Invoke callbacks on construction of entersub OPs for certain CVs
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: libb-hooks-op-check-entersubforcv-perl Version : 0.09 Upstream Author : Florian Ragwitz * URL : http://search.cpan.org/dist/B-Hooks-OP-Check-EntersubForCV/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : invoke callbacks on construction of entersub OPs for certain CVs B::Hooks::OP::Check::EntersubForCV is a perl module to register and unregister handlers to be executed when an entersub opcode for a given CV is compiled. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421181856.25017.69805.report...@dagon.fnord.no
Bug#669889: ITP: libdevel-beginlift-perl -- make selected sub calls evaluate at compile time
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: libdevel-beginlift-perl Version : 0.001003 Upstream Author : Matt S Trout * URL : http://search.cpan.org/dist/Devel-BeginLift/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : make selected sub calls evaluate at compile time Devel::BeginLift 'lifts' arbitrary sub calls to running at compile time - sort of a souped up version of "use constant". It does this via some slightly insane perlguts magic. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421181854.25043.12371.report...@dagon.fnord.no
Bug#669890: ITP: libconst-fast-perl -- Facility for creating read-only scalars, arrays, and hashes
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: libconst-fast-perl Version : 0.011 Upstream Author : Leon Timmermans * URL : http://search.cpan.org/dist/Const-Fast/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : facility for creating read-only scalars, arrays, and hashes Const::Fast is a perl module for creating read-only scalars, arrays, and hashes. It enables you to set a variable to the given value and subsequently make it readonly. Arrays and hashes will be made deeply readonly. This module uses the builtin readonly feature of perl, making access to the variables just as fast as any normal variable without the weird side-effects of ties -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421181855.25030.90697.report...@dagon.fnord.no
Bug#672777: ITP: grok -- powerful pattern-matching and reacting tool
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: grok Version : 1.20110708.1 Upstream Author : Jordan Sissel * URL : http://code.google.com/p/semicomplete/wiki/Grok * License : BSD Programming Lang: C Description : powerful pattern-matching and reacting tool The grok program can parse log data and program output. You can match any number of complex patterns on any number of inputs (processes and files) and have custom reactions. Grok is simple software that allows you to easily parse logs and other files. With grok, you can turn unstructured log and event data into structured data. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120513151947.29335.65010.report...@dagon.fnord.no
Bug#673515: ITP: puppetdb -- Puppet data warehouse
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: puppetdb Version : 0.9.0 Upstream Author : Puppet Labs * URL : http://docs.puppetlabs.com/puppetdb/0.9/ * License : Apache 2.0 Programming Lang: Clojure Description : Puppet data warehouse PuppetDB is a Puppet data warehouse; it manages storage and retrieval of all platform-generated data. Currently, it stores catalogs and facts; in future releases, it will expand to include more data, like reports. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120518171419.26484.16245.report...@dagon.fnord.no
Bug#710385: ITP: ruby-rgen -- Ruby modelling and generator framework
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: ruby-rgen Version : 0.6.2 Upstream Author : Martin Thiede * URL : http://ruby-gen.org/ * License : MIT Programming Lang: Ruby Description : Ruby modelling and generator framework RGen is a framework for Model Driven Software Development (MDSD)in Ruby. This means that it helps you build Metamodels, instantiate Models, modify and transform Models and finally generate arbitrary textual content from it. RGen is a dependency for the new "future" parser in puppet 3.2.x -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130530122019.15253.70847.report...@turbotape.w.bitbit.net
Bug#712765: ITP: ruby-safe-yaml -- Safe implementation of YAML.load
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: ruby-safe-yaml Version : 0.9.2 Upstream Author : Dan Tao * URL : https://github.com/dtao/safe_yaml * License : MIT Programming Lang: Ruby Description : Safe implementation of YAML.load The SafeYAML gem provides an alternative implementation of YAML.load suitable for accepting user input in Ruby applications. Unlike Ruby's built-in implementation of YAML.load, SafeYAML's version will not expose apps to arbitrary code execution exploits. (The safe_yaml gem was vendored into puppet to fix a recent vulnerability. The packaging of this gem should help this situation.) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130619095355.571.66065.report...@turbotape.w.bitbit.net
Re: Bug#712765: ITP: ruby-safe-yaml -- Safe implementation of YAML.load
Cédric Boutillier writes: > ruby-safe-yml is already in the archive: > > $ rmadison ruby-safe-yaml > > ruby-safe-yaml | 0.9.0-1 | jessie | source, all > > ruby-safe-yaml | 0.9.0-1 | sid| source, all > > It is maintained by the Ruby team: > http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-safe-yaml.git Thanks. Looking at the commandline history, I searched "wheezy" for the precense of the package. -- Stig Sandbeck Mathisen pgpSjxet_l_al.pgp Description: PGP signature
Re: Survey answers part 3: systemd is not portable and what this means for our ports
Henrique de Moraes Holschuh writes: > On Sun, 14 Jul 2013, Russ Allbery wrote: >> I've been administering UNIX systems professionally for 20 years, >> from SunOS and ULTRIX through AIX, HP-UX, IRIX, Solaris, and Linux. >> In my professional, *experienced* opinion, proper deployment of a >> modern init system will make Debian considerably more robust, simpler >> to develop, and simpler to administer. > > How much of that improvement would be realised if we added a > dependable, declarative (i.e. config-based instead of > shell-script-based) service configuration support to sysvinit ? The "declarative configuration" part, of course. :) -- Stig Sandbeck Mathisen (…who really could not resist) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wqortw6z@dagon.fnord.no
Bug#644050: ITP: prads -- pasive realtime asset detection system
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: prads Version : 0.3.0 Upstream Author : Edward Bjarte Fjellskål , Kacper Wysocki * URL : http://github.com/gamelinux/prads * License : GPLv2+ Programming Lang: C Description : pasive realtime asset detection system This program passively listens to network traffic and gathers information on hosts and services it sees on the network. This information can be used to map your network, letting you know what services and hosts are active, and can be used together with your favorite IDS/IPS setup for "event to application" correlation. The prads asset report utility will list this in a human readable format, incuding IP, mac address, and client and server software. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111002094513.21268.79364.report...@fsck.linpro.no
Re: directory under /usr/bin -- Ok or not?
Igor Pashev writes: > Isn't /usr/libexec for "internal use" exetutables? Other places, yes. Not in the FHS. So, being halfway serious: Debian wants FHS to document it before we can use it, and the FHS wants to document current practice. Clearly, we need someone in the Fedora project to start using /usr/libexec first. :) -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vcqzlktc@debian.org
Re: directory under /usr/bin -- Ok or not?
Josselin Mouette writes: > We already have $pkglibdir and $pkgdatadir for those. There is no > technical need for a new directory in /usr, and it doesn’t improve > anything for users. Possibly not for the users, but it _certainly_ improves the environment for system and application administrators. Some applications (for instance: inn and mailman) have a lot of executables which only makes sense when you're in the context of that application user, so having a /usr/libexec/ in the path for that user makes life as an application administrator easier. -- Stig Sandbeck Mathisen pgpREX4hqQHeC.pgp Description: PGP signature
Re: directory under /usr/bin -- Ok or not?
Marvin Renich writes: > How is /usr/libexec/ better than /usr/lib/ in these > cases? Placing executables in /usr/lib/package is just messy, if it contains, for instance, libraries. Having binaries in /usr/lib//bin, as inn2 does, is a bit better at least. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xhb2ehpo8@fsck.linpro.no
Re: Bug#652275: Guided partitioning should not offer separate /usr, /var, and /tmp partitions; leave that to manual partitioning
Simon McVittie writes: > life's too short to spend time booting in single-user mode and > resizing LVs. That's probably why we now have online resizing of LVs and filesystems -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762hgpsli@debian.org
Re: On init in Debian
Samuel Thibault writes: > Because the issue at stake might lie in systemd itself, not the unit > file. And if /bin/sh breaks on an init style system, you can fix it with an editor? -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xsjh0izjw@fsck.linpro.no
Re: On init in Debian
Josselin Mouette writes: > I’ve not seen many people interested specifically in upstart in this > discussion, apart from Canonical employees. When the "People's Front of systemd" have met the "Campaign for a Free sysvinit" on the field of debian-devel, and there are noone left save a few penguins and a wee, confused beastie not quite named Chuck, the "upstart Popular People's Front" will move in and restore order. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ehs92lee@dagon.fnord.no
Re: Canonical pushes upstart into user session - systemd developer complains
Vincent Lefevre writes: > It is more verbose, but I find it as readable (if you have characters > that normally need to be escaped, you can still use CDATA sections, > which is a way to keep the readability). So to keep everyone equally happy, we need: Structure _and_ readability. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wqx4dult@dagon.fnord.no
Re: Canonical pushes upstart into user session - systemd developer complains
Vincent Lefevre writes: > No, you don't have the structure from the XML point of view. I've seen this in production. "We use XML? Check!" -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87lidi52ms@dagon.fnord.no
Bug#698209: ITP: librarian-puppet -- a bundler for your puppet infrastructure
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: librarian-puppet Version : 0.9.7 Upstream Author : Tim Sharpe * URL : https://github.com/rodjek/librarian-puppet * License : MIT Programming Lang: Ruby Description : a bundler for your puppet infrastructure Librarian-puppet is a bundler for your puppet infrastructure. You can use librarian-puppet to manage the puppet modules your infrastructure depends on. It is based on Librarian, a framework for writing bundlers, which are tools that resolve, fetch, install, and isolate a project's dependencies. Librarian-puppet manages your modules/ directory for you based on your Puppetfile. Your Puppetfile becomes the authoritative source for what modules you require and at what version, tag or branch. Once using Librarian-puppet you should not modify the contents of your modules directory. The individual modules' repos should be updated, tagged with a new release and the version bumped in your Puppetfile. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130115082742.27214.33417.report...@dagon.fnord.no
Bug#698210: ITP: ruby-librarian -- a framework for writing bundlers
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: ruby-librarian Version : 0.0.26 Upstream Author : Jay Feldblum * URL : https://github.com/yfeldblum/librarian * License : MIT Programming Lang: Ruby Description : a framework for writing bundlers Librarian is a framework for writing bundlers, which are tools that resolve, fetch, install, and isolate a project's dependencies, in Ruby. Librarian ships with Librarian-Chef, which is a bundler for your Chef-based infrastructure repositories. In the future, Librarian-Chef will be a separate project. A bundler written with Librarian will expect you to provide a specfile listing your project's declared dependencies, including any version constraints and including the upstream sources for finding them. Librarian can resolve the spec, write a lockfile listing the full resolution, fetch the resolved dependencies, install them, and isolate them in your project. A bundler written with Librarian will be similar in kind to Bundler, the bundler for Ruby gems that many modern Rails applications use. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130115082746.26918.11060.report...@dagon.fnord.no
Re: Bug#732041: ITP: libvmod-throttle -- Throttling module for Varnish
On Fri, Dec 13, 2013 at 10:49:15AM +0100, Jérémy Lal wrote: > I'm hacking something ugly meanwhile for my own needs, but you can > count on me to test building against varnish 4 as soon as the > experimental version is out. varnish 4 tech preview 1 is now in debian experimental. I've tested that the main daemon runs, and that I can run varnishlog to see it serve incoming requests. The needed header files, as well as "vmodtool.py" are in the "libvarnishapi-dev" package. I've not tested building a vmod against it yet. A number of useful utilities are not built: /usr/bin/varnishhist /usr/bin/varnishreplay /usr/bin/varnishsizes /usr/bin/varnishtop The services "varnishlog" and "varnishnsca" fail autopkgtests. I've yet to investigate why. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131215092105.ga...@fnord.no
Re: Can we please change the Subject: ?
Andrey Rahmatullin writes: > About The Thread. The Thread That Shall Not Be Named. (to be more precise :) -- Stig Sandbeck Mathisen signature.asc Description: PGP signature
Bug#743194: ITP: ruby-hiera-eyaml -- OpenSSL Encryption backend for Hiera
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: ruby-hiera-eyaml Version : 2.0.1 Upstream Author : Tom Poulton (and others) * URL : https://github.com/TomPoulton/hiera-eyaml * License : Expat Programming Lang: Ruby Description : OpenSSL Encryption backend for Hiera A backend for Hiera that provides per-value encryption of sensitive data within yaml files to be used by Puppet. Only the values are encrypted, allowing files to be swiftly reviewed without decryption. The value of each key is encrypted individually, which means that "git diff" is meaningful. Includes a command line tool for encrypting, decrypting, editing and rotating keys. This makes it almost as easy as using clear text files. Basic asymmetric encryption (PKCS#7) is used by default. This does not require any native libraries to be compiled, and it allows users without the private key to encrypt values that the puppet master can decrypt hiera-eyaml includes a pluggable encryption framework (e.g. GPG encryption (hiera-eyaml-gpg) can be used if you have the need for multiple keys and easier key rotation) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140331110648.21115.13256.report...@turbotape.w.bitbit.net
Re: [Pkg-samba-maint] Default size limits for /run (/var/run) and /run/lock (/var/lock)
Roger Leigh writes: > One reason for doing this is to have a single writable mount on the > system, which might be useful for tiny systems with minimal resources, > where root is r/o. On such a system, it might be useful to pool the > limited writable space (which might not be a tmpfs). Could this case be handled better by the fsprotect package? -- Stig Sandbeck Mathisen pgpZY6Bxgti27.pgp Description: PGP signature
Re: network-manager as default? No!
Timo Juhani Lindfors writes: > I'd be interested in seeing real-life ifupdown configurations that > handle these. Here's an example from one of my servers that handles _some_ of them. (Addresses rewritten to rfc3330 space, and no explicit IPv6 config): * Two bonded ethernet interfaces for redundant layer two networking to distinct switches. (miimon vs arp_ip_target is another discussion). * Interfaces are added to bonding device when discovered. * Two extra VLAN interfaces. , | auto eth0 eth1 bond0 vlan101 vlan102 | | iface eth0 inet manual | bond-master bond0 | bond-primary eth0 eth1 | | iface eth1 inet manual | bond-master bond0 | bond-primary eth0 eth1 | | iface bond0 inet static | bond_slaves none | bond_mode active-backup | bond_miimon 100 | address 192.0.2.2 | netmask 255.255.255.248 | gateway 192.0.2.1 | | iface vlan101 inet static | vlan-raw-device bond0 | address 192.0.2.162 | netmask 255.255.255.248 | | iface vlan102 inet static | vlan-raw-device bond0 | address 192.0.2.170 | netmask 255.255.255.248 ` My major gripe with ifupdown is the lack of CIDR in "address", but I can live with that. :) -- Stig Sandbeck Mathisen ooo, shiny! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87sjtjmxsp@mavis.fnord.no
Re: Alioth status update, take 3
Francesco Poli writes: > I hope that some appropriate re-directions may be set up real soon now, > so that previous URLs can continue to work as before... If you have a specific example of something that does not work, it can be fixed. -- Stig Sandbeck Mathisen ooo, shiny! pgpS25Sqtp03c.pgp Description: PGP signature
Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]
Bernd Zeimetz writes: > On 05/25/2011 01:30 PM, Lucas Nussbaum wrote: >> I must admit that I prefer shorter URLs. Wouldn't it be possible to >> continue using http://{git,svn}.debian.org/ instead (without >> redirection)? >> >> Before: http://git.debian.org/?p=devscripts/devscripts.git >> After: http://anonscm.debian.org/gitweb/?p=devscripts/devscripts.git > > Even better would be http://git.debian.org/devscripts/devscripts.git > which is easy to handle with some rewrites. It is probably easy given enough information, yes. What was that URL used for? Gitweb? Git checkouts over HTTP? Something else? -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7x8vtu6gs8@fsck.linpro.no
Re: UDD access from Alioth(s children)
Tollef Fog Heen writes: > ]] Christian PERRIER > > | Is there a list of these known issues? > > Sure, it's in the topic of #alioth: http://titanpad.com/yyhfwA9Pyr What is the preferred method for submitting a proposed fix? -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y61m1pam@fnord.no
Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]
Tollef Fog Heen writes: > wsvn is already on the list of stuff still to fix as listed on > http://titanpad.com/yyhfwA9Pyr . Added wsvn rewrite config to the pad. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xboy8snrp@fsck.linpro.no
Re: mentors.debian.net runs the debexpo code now
Asheesh Laroia writes: > It's live: http://mentors.debian.net/ Very impressive. Congratulations to all involved parties. :) -- Stig Sandbeck Mathisen pgpJhDoY8uSQp.pgp Description: PGP signature
Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]
"O. Andrew" writes: > I'd like to see hgweb repo browser any time soon, too. It's very > annoying that it doesn't work any more. If you don't make the alioth admins guess which URLs work or not, things may actually be fixed. :) -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7xfwl1leo4@fsck.linpro.no
Bug#642518: ITP: puppet-lint -- Check puppet manifests for style guide conformity
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: puppet-lint Version : 0.1.4 Upstream Author : Tim Sharpe * URL : https://github.com/rodjek/puppet-lint/ * License : MIT Programming Lang: Ruby Description : Check puppet manifests for style guide conformity Puppet-lint will check puppet manifests for conformity with the Puppet Labs style guide. It checks spacing, indentation, whitespace, quoting, conditionals and classes. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110923113055.24998.76994.report...@fsck.linpro.no
Re: About the Hamm Freeze (!)
* James Troup (Sun, Jun 07, 1998 at 07:47:21PM +0100) > > Blah. An even quicker ldd reveals this is already not the case. > > 20:45:[EMAIL PROTECTED]| ~ $ldd /usr/bin/perl | grep gdbm > libgdbm.so.1 => /usr/lib/libgdbm.so.1 (0x40015000) > 20:46:[EMAIL PROTECTED]| ~ $ > > Until _that_ changes, perl can't not Depend on gdbm. What's the greater evil? hAving the gdbm package and the dependency, or linking in libgdbm statically? -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgph4td0lRyQa.pgp Description: PGP signature
Re: VI reasons (was Re: Base Set: Suggested additions & removals.)
* Michael Dietrich (Fri, Jun 19, 1998 at 04:31:52AM +0200) > if you all do not stop this discussion i start writing an editor. easy > to use just as EDIT.EXE. for anybody, especially a beginner. also for > professionals. > :wq Go ahead, it wouldn't hurt, would it? :-) -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: install.txt looks weird
* Maarten Boekhold (Wed, Jun 24, 1998 at 12:50:13PM +0200) > Hi, > > The install.txt that is refered to from the web-site looks weird. I don't > know if this is intentional, but section-titles are displayed like: > > AAddvvaanncceedd PPoowweerr MMaannaaggeemmeenntt > > ie. all letters are duplicated. Looks like "overstrike", try looking at it with "less", and you'll find that the double lettered words are in bold font. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what's after slink
* M.C. Vernon (Mon, Oct 05, 1998 at 04:02:32PM +0100) > How about naming it after species of penguin? > > That should keep us going for a little while... > > "I like my new debian emperor system" ;) This penguin idea, along with the "Hitchhiker's Guide" idea are the two best ideas I have seen in a while. Hmmm... Debian C'thulhu Debian Shoggoth Debian Yog-sothoth Debian Shub-niggurath Debian Yoglonaq Debian Ittaqha Debian Tsathoggua Debian Dhole ... Nah. :-) -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpJccughjfSM.pgp Description: PGP signature
Re: Call for mascot! :-)
* Chris Waters (Thu, Jan 28, 1999 at 10:14:15AM -0800) > 1. Dragon Aye! -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpBVRhU7iSbR.pgp Description: PGP signature
Re: User-selected window-manager in an easy way
* Wichert Akkerman (Sat, May 08, 1999 at 10:17:26PM +0200) > Previously Stig Sandbeck Mathisen wrote: > > The first part was easy (if I got it right, that is), that's just a small > > patch to /etc/X11/Xsession. > > Isn't is easier have some small script check the list of available > window managers and offer to create/update the users .xsession? I don't think it's easier, but it might be a better solution, when it's ready. :-) > This sounds much more flexible (you can also offer to start things > like xscreensaver, ssh-add, etc. etc.). ssh-add is already started from /etc/X11/Xsession, if you have ssh installed. Other than that, you're right, of course. > Also, GNOME already offer this functionality via the gnome-panel and > gnome-session. That requires the user to run Gnome, I suspect. :-) I was thinking of some simple, global solution, available from the menu. I suspect that "simple" and "global" does not belong together on this issue. It might need some more thinking. -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpFfumGhCxm8.pgp Description: PGP signature
FROM envelope rewite (Was: Mail delivery failed: returning message to sender)
* Brian Almeida (Tue, May 18, 1999 at 05:02:13PM -0400) > On Wed, May 19, 1999 at 01:20:03AM +0200, Mail Delivery System wrote: > > This message was created automatically by mail delivery software. > Can we please block this guy? It seems that there is a rewriting in the headers from Return-Path: <[EMAIL PROTECTED]> to Return-Path: I suspect this is done by exim after the fetchmail step, or that the POP3 server doesn't save the FROM address in the envelope, and that the next MTA or MDA tries to fix this by being creative. If the rewriting hadn't been done, the mail had bounced to the list handler, and not to the list itself. Anyone with more skill and experience with header parsing that know? -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpiUsGBKzNyZ.pgp Description: PGP signature
Re: /usr/bin/open now in use through the alternatives system.
Charles Plessy writes: > I went ahead and uploaded to Sid mime-support version 3.68, which > provides /usr/bin/open as a symbolic link to /usr/bin/run-mailcap > using the alternatives system, at a priority of 30. I welcome other > alternatives. This is good news. Thank you. :) I've used "open" as an alias for "xdg-open" for a long time. This command would probably also be appropriate as an alternative for "open". > At the moment the manual page of open is simply the one of > run-mailcap, but I plan to provide a specific one. Given the lack of > answer to my previous email (quoted below), I have not implemented URL > support in /usr/bin/run-mailcap. > >> Le Sat, Oct 10, 2020 at 04:27:17AM +0900, Charles Plessy a écrit : >> > >> > May I ask you for extra information on how important is it to >> > support URLs, and if anything beyond file:/, http:// and https:// >> > would need to be supported ? >> ... >> > Also, can you give me a pointer to an explanation of what file:/ >> > URLs are useful for ? I read RFC 8089, but still did not get the >> > point. When handling various methods for fetching content, being explicit about the scheme ("This is a file") is more robust than being implicit ("As a last resort, this will be regarded as a file"). Using "file" a default scheme makes sense if nothing else is specified. File URIs may be returned by other applications. When using "tracker search" to search the content of my local files, all results are returned with "file:///" URIs. Being able to pipe that output to "open" would be awesome. >> > Since `eog http://example.com/image.png` will open the image, >> > shouldn't an "open" program ask to the server what the media type >> > of the URL is, and pass it to the default program able to handle >> > it, instead of just visualising in the browser ? I would much rather trust the local "file" command and magic database instead. The remote server will most likely return a proper content type, but trusting remote servers to influence which command to open the file locally will have an impact on security. -- Stig Sandbeck Mathisen Debian Developer
Re: /usr/bin/open now in use through the alternatives system.
Josh Triplett writes: > Ignoring the server-provided MIME type and doing content-sniffing is a > historical bug that browsers such as IE have had, and that has caused > *many* problems (including security problems). > [...] Lots of good points. I had thankfully forgotten about how IE had its own rules about how to display things it downloaded, but of course it would still be relevant. (https://web.archive.org/web/20110930155122/http://msdn.microsoft.com/en-us/library/ms775147.aspx) -- Stig Sandbeck Mathisen Debian Developer
Bug#946423: ITP: ruby-optimist -- Commandline option parser for Ruby that just gets out of your way.
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: ruby-optimist Version : 3.0.0 Upstream Author : William Morgan, Keenan Brock, Jason Frey * URL : https://www.manageiq.org/optimist/ * License : MIT/Expat Programming Lang: Ruby Description : Commandline option parser for Ruby that just gets out of your way. Upstream description Optimist is a commandline option parser for Ruby that just gets out of your way. One line of code per option is all you need to write. For that, you get a nice automatically-generated help page, robust option parsing, and sensible defaults for everything you don't specify. Features: - Dirt-simple usage. - Sensible defaults. No tweaking necessary, much tweaking possible. - Support for long options, short options, subcommands, and automatic type validation and conversion. - Automatic help message generation, wrapped to current screen width. Packaging and maintenance - The upstream project name has been changed from trollop to optimist. (https://github.com/ManageIQ/optimist/issues/92) ruby-optimist is a dependency for hiera-eyaml >= 3.0.0, and needs to be available before newer versions of hiera-eyaml can be imported. ruby-optimist will be maintained under the debian-ruby team umbrella.
Re: wiki about block alignment issues
Daniel Pocock writes: > I've started a wiki about block alignment issues: > > https://wiki.debian.org/DiskBlockAlignment > > Can anybody comment on specific packages / tools that may help people > investigate or update their systems, maybe adding links to the wiki? "lsblk" (one of several ls$something commands) in the "util-linux" package is very helpful. It can show multiple fields, and has values for both storage and discard. ceph-osd-123# lsblk --output NAME,TYPE,ALIGNMENT,PHY-SEC,LOG-SEC,DISC-ALN,DISC-GRAN NAME TYPE ALIGNMENT PHY-SEC LOG-SEC DISC-ALN DISC-GRAN sdadisk 0 512 51200B ├─sda1 part 0 512 51200B └─sda2 part 0 512 51200B ├─vg0-swap lvm 0 512 51200B ├─vg0-root lvm 0 512 51200B ├─vg0-srvlvm 0 512 51200B ├─vg0-tmplvm 0 512 51200B ├─vg0-home lvm 0 512 51200B ├─vg0-varbackups lvm 0 512 51200B ├─vg0-varlog lvm 0 512 51200B └─vg0-ceph lvm 0 512 51200B sdcdisk 0 512 51200B ├─sdc1 part 0 512 51200B └─sdc2 part 0 512 51200B sdddisk 0 512 51200B ├─sdd1 part 0 512 51200B └─sdd2 part 0 512 51200B [...] laptop-with-crypto# lsblk --output NAME,TYPE,ALIGNMENT,PHY-SEC,LOG-SEC,DISC-ALN,DISC-GRAN NAME TYPE ALIGNMENT PHY-SEC LOG-SEC DISC-ALN DISC-GRAN sdadisk 0 512 5120 512B ├─sda1 part 0 512 5120 512B ├─sda2 part 0 512 5120 512B ├─sda3 part 0 512 5120 512B └─sda4 part 0 512 5120 512B └─sda4_crypt crypt 0 512 5120 512B sdbdisk 04096 51200B ├─sdb1 part 04096 51200B ├─sdb2 part 04096 51200B ├─sdb3 part 04096 51200B ├─sdb4 part 04096 51200B ├─sdb5 part 04096 51200B ├─sdb6 part 04096 51200B └─sdb7 part 0 4096 51200B -- Stig Sandbeck Mathisen
Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)
Holger Levsen writes: > until your mail I wasn't aware that Puppet is also split into a free > and a commercial version… The Puppet in "Puppet Enterprise" is the same code as in the open source version. A Puppet Enterprise installation consists of additional omnibus-type packaging (puppet plus all dependencies installed in /opt/puppetlabs) for the agent, a similar installer for the master, plus configuration of mcollective and ActiveMQ, a Web application called the "Enterprise Console", as well as professional support. As far as I remember, only the "Enterprise Console" is non-free software. -- Stig Sandbeck Mathisen signature.asc Description: PGP signature
Re: manpages.debian.org has been modernized!
Bernd Zeimetz writes: > On 01/30/2017 05:45 PM, Sean Whitton wrote: >> I agree, they aren't as good. However, they're very nearly as good, >> and it's too common to overstate how good GitHub's workflow is. > > Nearly as good? Where can I click 'merge' in a web gui in Debian??? Just under the "all tests have passed" field, under the list of merge requests, in the "very nearly as good as GitHub" tool he is talking about, but obviously forgot to link to. :) In my experience, GitLab is "very nearly as good as" GitHub regarding workflow. How many good things can I say about that workflow without it being "overstating how good the GitHub workflow is"? Gitlab is free software, and the CE version is good enough to base a large organization around. I am, hovever, somewhat in doubt they would accept merge requests adding free bits to replace the non-free bits they have based their business on selling. I've noted the presence of gogs (https://gogs.io/) and pagure (https://pagure.io/pagure), which look to be completely free projects, but haven't tried any of them yet. https://rocketgit.com/op/doc/compare has a comparison matrix, but with bits missing from all other than rocketgit, which I didn't know about before I found that matrix. Rocketgit ... also seem to have the functionality for maintaining a github workflow, but their project pages (like https://rocketgit.com/user/catalinux/rocketgit) has a _slight_ contrast problem. -- Stig Sandbeck Mathisen https://fnord.no/