Accepted resolvconf 1.79 (source all) into unstable

hanged-By: Thomas Hood <jdth...@gmail.com> Description: resolvconf - name server information handler Closes: 804976 819498 Changes: resolvconf (1.79) unstable; urgency=low . [ Thomas Hood ] * Use which to test for availability of dnssec-triggerd * [19003cb] Drop obsolete versioned

Accepted resolvconf 1.78 (source all) into unstable

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 787457 Changes: resolvconf (1.78) unstable; urgency=low . [ Marco Nenciarini ] * [dd83369] debian/gbp.conf: Use new-style sections sans git- [ Thomas Hood ] * [f73de5c] Add sysv-rc

Accepted resolvconf 1.77 (source all) into unstable

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.77) unstable; urgency=low . * [0781847] interface-order: match br ifaces at the same priority as eth ifaces (see LP#1446681) * Remove obsolete upgrade code * [00ad4bf

Accepted resolvconf 1.76.1 (source all) into unstable

Changed-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 775356 Changes: resolvconf (1.76.1) unstable; urgency=medium . * [eb81ca0] Eliminate bashisms. Thanks to Michael Gilbert (Closes: #775356) Checksums-Sha1

Accepted resolvconf 1.76 (source all) into unstable

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 749405 Changes: resolvconf (1.76) unstable; urgency=low . * resolvconf.service: Install into sysinit.target, not into network.target (Closes: #749405) Thanks to Martin Pitt and Edward

Accepted resolvconf 1.75 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 700846 718021 718232 718714 737158 Changes: resolvconf (1.75) unstable; urgency=low . * [49dedb8] Update man page re: dns-nameserver (Closes: 718021) * [6195584] Don't give update-rc.d start

Re: getaddrinfo() return value chaos

on in the upstream Bugzilla ticket. Arising from the discussion in that ticket an effort has begun better to describe the desired behavior of getaddrinfo(). Initial results can be seen here: http://sourceware.org/glibc/wiki/NameResolver -- Thomas Hood -- To UNSUBSCRIBE, email to debian-devel-requ

Re: Preventing government subversion in Debian, verification of binary package uploads

. So perhaps the more pertinent question is, what safeguards does Debian have against infiltration? -- Thomas Hood -- 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

Re: Fwd: /etc/hosts and resolving of the local host/domainname - 127.0.0.1 vs. 127.0.1.1

Op 8 aug. 2013 17:49 schreef Tom H tomh0...@gmail.com het volgende: The output below is from Debian Sid with libnss-myhostname installed [...] [root@debdeb:/etc]# cat hostname debdeb [root@debdeb:/etc]# cat hosts 127.0.0.1 localhost [root@debdeb:/etc]# getent hosts 127.0.1.1 192.168.1.250

Re: Fwd: /etc/hosts and resolving of the local host/domainname - 127.0.0.1 vs. 127.0.1.1

Op 7 aug. 2013 10:33 schreef Wouter Verhelst wou...@debian.org het volgende: Historically, localhost has always been 127.0.0.1. It feels wrong to change that, simply because localhost starts showing up in places it was never meant to show up in. To clarify, no one is proposing that 'localhost'

Fwd: /etc/hosts and resolving of the local host/domainname - 127.0.0.1 vs. 127.0.1.1

practice actually causes problems --- problems that can't easily be solved by patching individual packages either to make them listen on 127.0.1.1 on the one hand or to make them talk to localhost on the other. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org

Accepted resolvconf 1.74 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.74) unstable; urgency=low . * [bb84ffc] Tweak the README: * [e3910a7] Recommend use of 'dns-nameserver'. No longer mention the useless deprecated 'dns-domain

Re: getaddrinfo() return value chaos

replies that the hostname does not exist: EAI_FAIL - The nameserver doesn't reply, or replies with a temporary failure: EAI_AGAIN - You used AI_NUMERICHOST or AI_NUMERICSERV and didn't give a number: EAI_NONAME Further discussion can best be carried on in the upstream Bugzilla ticket. -- Thomas Hood

Re: getaddrinfo() return value chaos

It looked to me as if #582916 and roughly duplicate #671789 could have been fixed in libc6 2.17-7 which it includes two commits http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cfde9b463d63092ff0908d4c2748ace648e2ead8

Re: getaddrinfo() return value chaos

On Mon, Jul 8, 2013 at 8:23 AM, Helmut Grohne hel...@subdivi.de wrote: Here are my results: Making resolv.conf empty Results of looking up www.google.com: status = -11, errno = 111 Results of looking up a bogus name: status = -11, errno = 111 Writing nameserver

Re: boot ordering and resolvconf

different findings and I think we should get to the bottom of this difference since it is relevant for how we think about ntpd bug report #683061. Helmut Grohne wrote: On Sun, Jun 30, 2013 at 10:40:03PM +0200, Thomas Hood wrote: A problem is that getaddrinfo() doesn't distinguish in its return

getaddrinfo() return value chaos

Continuing on from the boot ordering and resolvconf thread; cc:ed to Helmut in case this gets filtered again; bcc:ed to 683...@bugs.debian.org since this is relevant for how that issue is addressed... Executive summary: The getaddrinfo() returns different values depending on the OS and on

Re: getaddrinfo() return value chaos

On Sun, Jul 7, 2013 at 2:41 PM, Kurt Roeckx k...@roeckx.be wrote: A related bug is #582916 Thanks. Besides that, #671789 and #713799 are also probably related. The latter was closed by the 2.17-7 release which is the most recent in unstable; I should be testing with that version rather than

Re: Updating /etc/hosts automatically / behavior of sed command

/etc/hosts in 1999 but I hope that no one has to do that any longer. :) -- Thomas Hood

Re: boot ordering and resolvconf

turn out that large numbers of libc resolver clients need to be modified, which so far as I know is not the case. -- Thomas Hood

Re: boot ordering and resolvconf

/resolvconf.8 -- Thomas Hood -- 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/51d43cc2.4030...@gmail.com

Re: boot ordering and resolvconf

Tollef Fog Heen wrote: I think changing /etc/resolv.conf automatically is broken at all. What's the malfunction? We should have a generated /run/resolv.conf that's overridden by the settings in /etc/resolv.conf (if it exists). This allows you to have a consistent set of domains searched for

Re: boot ordering and resolvconf

In addition resolvconf does not properly support mode (A), due to the local forwarding nameserver is running requirement. It can leave /etc/resolv.conf empty until the name server is actually started. Well, you are right that resolvconf was designed to support mode B, and only supports mode A

Re: boot ordering and resolvconf

Helmut Grohne wrote: All that I am aiming for is to declare one of the following practises as broken: * Treating an empty /etc/resolv.conf as a permanent error or failing to discover changes in /etc/resolv.conf later on. * Changing /etc/resolv.conf during startup of a local dns cache.

Re: boot ordering and resolvconf

(see bug report #483098). -- Thomas Hood resolvconf maintainers -- 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/51cda59b.1000...@gmail.com

Accepted resolvconf 1.72 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.72) unstable; urgency=low . * [d3b9390] Fix flag file name in debian/config Checksums-Sha1: ae8b0f3114ffe0e96f66f1f1e1da8c22e62abd2b 1087 resolvconf_1.72.dsc

Accepted resolvconf 1.71 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.71) unstable; urgency=low . [ Thomas Hood ] * [7e4b50a] Accept multiple dns-nameserver options in /e/n/i, allowing at most one address per option line. Requires Jessie

Accepted resolvconf 1.70 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 513445 697435 Changes: resolvconf (1.70) unstable; urgency=low . [ Thomas Hood ] * [ec06f8d] Add NEWS item about the bind update script being disabled (Closes: #697435) * [ec06f8d

socket-based activation has unmaintainable security?

give me the golden clue? -- Thomas Hood -- 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/5110dcec.4010...@gmail.com

Accepted resolvconf 1.69 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 681623 687507 Changes: resolvconf (1.69) unstable; urgency=low . * [276fc24] Bump Standards-Version; no changes required * [6982da6] README: Name packages that clobber /etc/resolv.conf

Accepted resolvconf 1.68 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 683672 Changes: resolvconf (1.68) unstable; urgency=low . * [1527598] Add sk.po. Thanks to Slavko (Closes: #683672) * [7713764] Update resolvconf's ppp hook also to exit when passed

Accepted resolvconf 1.67 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.67) unstable; urgency=low . [ Thomas Hood ] * [5e645ac] Use more conventional name for record created by resolvconf's pppd hook script * [58da88f] Change

Accepted resolvconf 1.66 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.66) unstable; urgency=low . [ Thomas Hood ] * [ed8ab34] Silence lsattr error message in postinst * [23217c3] resolvconf(8): List allowed dns-* interfaces(5) options

Accepted resolvconf 1.65 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 662724 Changes: resolvconf (1.65) unstable; urgency=low . [ Thomas Hood ] * [3f0a1a1] Create /etc/resolvconf/run and its target and subdir in the postinst as well as in the preinst (Closes

On init in *Debian*

you see some other approach as more compatible and consistent? -- Thomas Hood -- 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/cajn8kfa5vsjj3osz1cjuwyfwco_fpnamz96aq

Re: upstart: please update to latest upstream version

On Sun, Feb 26, 2012 at 17:24, Goswin von Brederlow goswin-...@web.de wrote: Maybe the solution isn't event base or dependency based. Maybe the right solution is event based and dependency based. In one sense this is obviously right. Any solution has to respond to various kinds of events and

Re: upstart: please update to latest upstream version

On Fri, Feb 24, 2012 at 20:17, Steve Langasek vor...@debian.org wrote: On Thu, Feb 23, 2012 at 11:58:08AM +0100, Goswin von Brederlow wrote: Upstart also does not support Should-Start which makes it impossible to provide corect init scripts for a number of services. For example autofs will

Re: upstart: please update to latest upstream version

in turn starts service daemons. Does this make any sense, and if so, what would be the advantages and disadvantages of this? -- Thomas Hood -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http

Re: upstart: please update to latest upstream version

On Thu, Feb 23, 2012 at 11:58, Goswin von Brederlow goswin-...@web.de wrote: Upstart also does not support Should-Start which makes it impossible to provide correct init scripts for a number of services. For example autofs will not work if it uses nis because nis is not started before autofs.

Eliminating bash scripts?

will not necessarily run faster if it has to be rewritten to run on sh. This is especially true if ${//}s are replaced by pipes to sed. -- Thomas Hood

Accepted resolvconf 1.61 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 642965 Changes: resolvconf (1.61) unstable; urgency=low . * [cbb5105] list-records: Add comment re: extglob; speed up final loop * [4492943] Eliminate bashisms from /sbin/resolvconf. (Other

Accepted resolvconf 1.59 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 633014 635470 635775 Changes: resolvconf (1.59) unstable; urgency=low . * dhclient-enter-hooks.d/resolvconf: Add support for dhclient DHCPv6 (Closes: #635470) * postinst: Fail with message

Accepted resolvconf 1.56 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 629022 629165 629186 629201 629411 Changes: resolvconf (1.56) unstable; urgency=low . [ Thomas Hood ] * Create /etc/resolvconf/run as a directory if no tmpfs is available into which it can

Accepted resolvconf 1.55 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 628524 628669 628719 Changes: resolvconf (1.55) unstable; urgency=medium . [ Thomas Hood ] * Include old update.d/bind script for illustration purposes as /usr/share/doc/resolvconf

Accepted resolvconf 1.53 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 268073 567059 608933 627440 627691 Changes: resolvconf (1.53) unstable; urgency=low . [ Thomas Hood ] * Dpkg trigger is now called 'resolvconf-enable-updates' and is now intended only

Accepted resolvconf 1.54 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Changes: resolvconf (1.54) unstable; urgency=low . [ Thomas Hood ] * Put exit 0 at the end of each maintainer script Checksums-Sha1: 5ba683b9fe5602e296156d5749f49699a86aca44 1044 resolvconf_1.54.dsc

Accepted resolvconf 1.52 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 625623 625786 625896 626030 626302 626675 Changes: resolvconf (1.52) unstable; urgency=low . [ Thomas Hood ] * Add debian/source/format at lintian's suggestion * Update debconf template

Accepted resolvconf 1.51 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 568820 Changes: resolvconf (1.51) experimental; urgency=low . [ Thomas Hood ] * Rename 'TRUNCATE_NAMESERVER_LIST_AFTER_127' to 'TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS

Accepted resolvconf 1.50 (source all)

-By: Thomas Hood jdth...@gmail.com Description: resolvconf - name server information handler Closes: 414692 Changes: resolvconf (1.50) experimental; urgency=low . [ Thomas Hood ] * Also migrate non-symlinked directory /etc/resolvconf/run to /run/resolvconf. * Be interested in own

Re: /run in experimental

Resolvconf 1.49, which makes use of /run instead of /lib/init/rw for storing run-time data, has just been uploaded to experimental. Those testing the experimental initscripts package (2.88dsf-13.4) are invited to test this experimental resolvconf package along with it. -- Thomas Hood resolvconf

Re: /run support for wheezy: final (I hope) call for testing

*saved_names[MAX_NESTED_LINKS + 1]; -- Thomas Hood -- 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/4dab404a.9080...@gmail.com

Re: Only forbid use of old alternatives to /run in wheezy+1?

This is not to say we couldn't remove it on startup though. You should not remove /lib/init/rw on the next reboot. If the upgrade stops due to an error then the system might be rebooted before the upgrade is continued. /lib/init/rw needs to remain present until all packages using it have

Only forbid use of old alternatives to /run in wheezy+1?

the wheezy version of its postinst runs. But this occurs after initscripts's postinst runs. And that is the last chance initscripts has to eliminate /lib/init/rw in wheezy. So I conclude that initscripts should only eliminate /lib/init/rw in wheezy+1. -- Thomas Hood -- To UNSUBSCRIBE, email

Resolvconf trigger? (Re: #567059)

and other pitfalls should I watch out for? 3. What is an appropriate name for the trigger? 4. Does anything have to be approved or discussed on a particular mailing list or can I go ahead and introduce the trigger and then ask the maintainers of caching nameservers to make use of it? -- Thomas

Re: Default size limits for /run (/var/run) and /run/lock (/var/lock)

First of all, thanks to Roger Leigh for leading this effort. Roger Leigh wrote: Proposal: Switch the default for all tmpfs mounts from 50% to 20%; it's still very large, but you have to mount many more to be able to break your system. He should have said ... but you have to mount *and fill*

Re: Default size limits for /run (/var/run) and /run/lock (/var/lock)

I just realized that I misunderstood Roger Leigh's posting and so my previous message was mostly superfluous. My apologies. 1. His statement but you have to mount many more to be able to break your system was correct (and can be made more explicit by adding ... by filling them all). 2. His

openresolv vs. resolvconf

-in replacement for resolvconf then migration from resolvconf to openresolv would be one way of solving this undermaintenance problem. What further pros and cons do people see out there? [0]http://roy.marples.name/projects/openresolv/wiki/OpenResolvReasons [1]http://bugs.debian.org/477723 -- Thomas Hood

How to warn about need to port changes to new configuration file?

. Is there a need to warn the administrator that he should (presumably) re-implement his changes in the new file? If so, what is the best way to warn him? Should debconf notes be used? -- Thomas Hood -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble

Re: libnss-myhostname instead of mangling /etc/hosts

see http://lists.debian.org/debian-glibc/2005/06/msg00173.html for one of the earlier discussions about this issue. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http

Accepted resolvconf 1.42 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 03 Aug 2008 21:27:56 +0200 Source: resolvconf Binary: resolvconf Architecture: source all Version: 1.42 Distribution: unstable Urgency: high Maintainer: resolvconf maintainers [EMAIL PROTECTED] Changed-By: Thomas Hood [EMAIL

Re: Getting resolvconf back into testing

Peter Samuelson wrote: Looks like you just need to wait 4 more days. Lenny isn't frozen yet, not for optional packages. OK, thanks. (I was under the impression that some sort of intervention was required in order to undo a removal.) -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Getting resolvconf back into testing

from the DDs on the resolvconf maintenance team. I hope that some DD who reads d-d can take care of ushering resolvconf back into testing. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted mwavem 2.0-3 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 21 Apr 2008 13:48:14 +0200 Source: mwavem Binary: mwavem Architecture: source i386 Version: 2.0-3 Distribution: unstable Urgency: low Maintainer: Debian mwavem maintainers [EMAIL PROTECTED] Changed-By: Thomas Hood [EMAIL

Accepted resolvconf 1.38 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 31 Dec 2007 12:00:00 +0100 Source: resolvconf Binary: resolvconf Architecture: source all Version: 1.38 Distribution: unstable Urgency: low Maintainer: resolvconf maintainers [EMAIL PROTECTED] Changed-By: Thomas Hood [EMAIL

Accepted thinkpad 5.9-2.1 (source i386)

-By: Thomas Hood [EMAIL PROTECTED] Description: thinkpad-base - Configuration files for thinkpad-modules packages thinkpad-source - Source code for thinkpad-modules packages Closes: 364235 Changes: thinkpad (5.9-2.1) unstable; urgency=low . [ Thomas Hood ] * NMU. Martin Krafft

Accepted resolvconf 1.35 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Jan 2006 23:53:47 +0100 Source: resolvconf Binary: resolvconf Architecture: source all Version: 1.35 Distribution: unstable Urgency: low Maintainer: resolvconf maintainers [EMAIL PROTECTED] Changed-By: Thomas Hood [EMAIL

Interim maintainer needed for thinkpad and tpctl

: critical. Therefore I am seeking an interim maintainer of thinkpad and tpctl, preferably someone who would like to carry on as co-maintainer with Martin. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Emphasize teams, not packages

by Joerg Jaspert (joerg) -- Thomas Hood

Re: Emphasize teams, not packages

of participating in some other project, such as Ubuntu, which does recognize contributions other than package maintenance.) -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted thinkpad 5.9-2 (source i386)

-By: Thomas Hood [EMAIL PROTECTED] Description: thinkpad-base - Configuration files for thinkpad-modules packages thinkpad-source - Source code for thinkpad-modules packages Closes: 353190 Changes: thinkpad (5.9-2) unstable; urgency=low . [ Thomas Hood ] * Note that CONFIG_OBSOLETE_INTERMODULE

Accepted sysvinit 2.86.ds1-14 (source i386 all)

] Changed-By: Thomas Hood [EMAIL PROTECTED] Description: initscripts - Scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities Closes: 356226 357245 357667 357667 Changes: sysvinit (2.86.ds1-14) unstable

Re: dicussion about patches ... ignoring patches make motivation to provide them fall

social norms are not the same as those of everyday life. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: dicussion about patches ... ignoring patches make motivation to provide them fall

. Purely hypothetical case, but it could happen. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted sysvinit 2.86.ds1-13 (source i386 all)

] Changed-By: Thomas Hood [EMAIL PROTECTED] Description: initscripts - Scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities Closes: 352398 352741 353083 353212 353585 355746 356226 Changes: sysvinit

Re: conffile purging and maintainer scripts

reckoning. Is this correct? Again, postrms should not remove files that are currently conffiles. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted thinkpad 5.9-1 (source i386)

-By: Thomas Hood [EMAIL PROTECTED] Description: thinkpad-base - Configuration files for thinkpad-modules packages thinkpad-source - Source code for thinkpad-modules packages Closes: 298652 315293 317496 342256 342458 342865 Changes: thinkpad (5.9-1) unstable; urgency=low . [ Thomas Hood ] * New

Re: /run vs. /lib/run

that was running all the time. Ubuntu is already mounting tmpfs's on /var/lock and /var/run. It's a reasonable thing to do and we should support it. That means that packages using these directories should create any subdirectories they need. Don't forget to set ownership and permissions. -- Thomas

GPL version option

to the granting or non-granting of the GPL version option. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: when and why did python(-minimal) become essential?

is that users not have a stripped down python, then Debian provides a stripped down python-minimal instead. -- Thomas Hood

Re: when and why did python(-minimal) become essential?

-- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Need for launchpad

in Debian and record the patch URL in the debian bug system. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: when and why did python(-minimal) become essential?

: yes in Debian. In any case I am hoping to see python-minimal included in Debian. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: udev naming problems for eth*

* ...tries to rename it to 'eth1', but that name is taken -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: when and why did python(-minimal) become essential?

In any case I am hoping to see python-minimal included in Debian. I now see that it is already in sid. :) $ apt-cache madison python-minimal python-minimal |2.3.5-5 | http://ftp.nl.debian.org sid/main Packages -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: udev naming problems for eth*

it to the temporary name. # Then try several times to rename it to new name Now trying several times, etc., may work, but it's a kludge. There are sound ways of resolving contention for a shared resource. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: Need for launchpad

packages that looked gratuitious, but then I have been comforted by the thought that the perpetrators of gratuitous changes are the ones who have to pay the price for it, because they have to carry such changes forward. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: New experimental sysvinit

base in regarding this to be a candidate for release to unstable. Again, TIA for testing it. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Need for launchpad

developers tried to get their changes into sid. It is certainly not their responsibility to do so, but in my experience Ubuntu developers have been very cooperative when they have been approached. So I don't see a big problem. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: Need for launchpad

in debian and record the patch URL in the debian bug system. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Fwd: Bug#344758: init.d script should create /var/run/dirmngr

, this dir should be removed by the postrm on purge. I would advise not including /var/run/foo in the package since it is superfluous and its presence could hide a bug in your directory-creation code. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble

Re: Fwd: Bug#344758: init.d script should create /var/run/dirmngr

Would it be useful if the initscript that clears /var/run also created a directory hierarchy under /var/run? (There are different ways of implementing thus, but we can talk about details if this feature is deemed worthwhile.) -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Re: How to Increase Contributions from Volunteers

, which should be closed rather than advertized. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to Increase Contributions from Volunteers

it the obscure the point game, because the pairs of statements were meant to illustrate a difference in attitude, not a set of absolute contradictions. But I think you know that. Because you are really playing another game, which I'll dub the innuendo game. -- Thomas Hood -- To UNSUBSCRIBE

Re: How to Increase Contributions from Volunteers

hobby clubs. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to Increase Contributions from Volunteers

of ...developers... (which would also be more accurate since non-DD maintainers are already listed). And so on. Reword with the principle in mind that there are many contributors to Debian who are not Debian Developers®. -- Thomas Hood

Package dependencies due to documentation relationships?

or recommendations about how documentation relationships should be reflected in package dependencies? -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: New experimental sysvinit

A new version of sysvinit is being prepared for release to experimental. OK, sysvinit 2.86.ds1-8 is now in incoming. TIA for testing it. ;) -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: New experimental sysvinit

Henrique de Moraes Holschuh wrote: How well that works with /var in a separate partition? It should work fine because S55bootmisc.sh runs after S45mountnfs.sh. -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: New experimental sysvinit

an existing feature (to make it compatible with a read-only root filesystem) without altering its behavior any more than necessary. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Thoughts on Debian quality, including automated testing

be done to help individual maintainers fix more bugs and fix them better? -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

  1   2   3   4   >