Re: where is /etc/hosts supposed to come from?

OoO En ce doux début de matinée du mardi 29 décembre 2009, vers 08:34, je disais: >> Details in . I >> do wonder, however, why the system hostname has to appear in /etc/hosts >> at all? Programs that want to find it out can read /etc/hos

Re: where is /etc/hosts supposed to come from?

OoO En cette nuit nuageuse du mardi 29 décembre 2009, vers 00:41, Sam Morris disait : > Details in . I > do wonder, however, why the system hostname has to appear in /etc/hosts > at all? Programs that want to find it out can read /etc/

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Raphael Geissert writes: > 3.0 would be friendlier if it would only *not* automatically apply the > patches when extracting the source. But then there's not much point for > dpkg to know about patches. I do think the problem of not having buildable source after dpkg-source -x is worth solving, a

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Raphael Geissert wrote: > Russ Allbery wrote: > [...] >> For Git-maintained packages like openafs, that would mean >> ignoring all the patch management features and letting it generate a >> single combined Debian diff analogous to the existing 1.0 diff from the >> patched upstream source maintaine

Re: [Expat-discuss] RFH: Patch for CVE-2009-3560 in expat breaks the Perl XML parser

Niko Tyni wrote: > I'm attaching an example XML document and the external DTD it > references. Without the CVE-2009-3560 patch, the test 'xmlwf -p t.xml' > silently passes. With the patch, the output is > > t.dtd:4:3: syntax error > t.xml:2:28: error in processing external entity reference > >

Re: where is /etc/hosts supposed to come from?

On Tue, Dec 29, 2009 at 01:47:40AM +0100, Vincent Lefevre wrote: > > As for mail, we already appear to have an /etc/mailname file for MTAs and > > MUAs to use for finding out the 'canonical' name of the host for message- > > IDs and the like. > /etc/mailname doesn't seem to be specified by POSIX

Re: where is /etc/hosts supposed to come from?

In article <20091229005213.ga28...@xvii.vinc17.org> you wrote: > So, that would define the FQDN of your machine, i.e. what > "hostname -f" should return. We can also thing about putting the fully qualified host name in /etc/hostname. A patch to hostname would be to not start resolving, if /uname

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Tue, Dec 29, 2009 at 10:16 AM, Charles Plessy wrote: > The source format versions 3.0 (quilt) solves much of the issues in the above > paragraph, but comes with its own patch management system. How about > introducing > a new 3.0 variant that has the following features: > >  - no patch manage

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Le Mon, Dec 28, 2009 at 12:44:29PM -0500, Joey Hess a écrit : > > I would prefer not to see such packages in the archive using source > format 3.0. We've been down that road with 1.0, and it was not pretty. > Above all other goals, my goal with putting the framework of source 3.0 > in place was to

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Russ Allbery wrote: [...] > For Git-maintained packages like openafs, that would mean > ignoring all the patch management features and letting it generate a > single combined Debian diff analogous to the existing 1.0 diff from the > patched upstream source maintained in Git. > I couldn't agree mo

Re: where is /etc/hosts supposed to come from?

On 2009-12-29 01:47:40 +0100, Vincent Lefevre wrote: > On 2009-12-29 00:21:45 +, Sam Morris wrote: > > As for mail, we already appear to have an /etc/mailname file for MTAs and > > MUAs to use for finding out the 'canonical' name of the host for message- > > IDs and the like. > > /etc/mailnam

Re: where is /etc/hosts supposed to come from?

On 2009-12-29 00:21:45 +, Sam Morris wrote: > On Tue, 29 Dec 2009 01:03:12 +0100, Vincent Lefevre wrote: > > Programs may need the FQDN, even without any network connection (for > > instance, even local mail messages should have a Message-Id). And > > /etc/hostname doesn't necessarily contain t

Re: where is /etc/hosts supposed to come from?

On Tue, 29 Dec 2009 01:03:12 +0100, Vincent Lefevre wrote: > On 2009-12-28 23:41:38 +, Sam Morris wrote: >> Details in . I >> do wonder, however, why the system hostname has to appear in /etc/hosts >> at all? Programs that want to find i

Re: where is /etc/hosts supposed to come from?

On 2009-12-28 23:41:38 +, Sam Morris wrote: > Details in . I > do wonder, however, why the system hostname has to appear in /etc/hosts > at all? Programs that want to find it out can read /etc/hostname > directly, after all. And wtf is

Re: where is /etc/hosts supposed to come from?

On Sun, 27 Dec 2009 14:22:53 -0800, Steve Langasek wrote: > On Sun, Dec 27, 2009 at 01:25:55PM -0800, Daniel Moerner wrote: >> On Sun, Dec 27, 2009 at 12:50 PM, Russell Coker >> wrote: >> > I've just done a debootstrap install of Lenny, and /etc/hosts doesn't >> > exist. Where is /etc/hosts suppo

Re: where is /etc/hosts supposed to come from?

On 2009-12-28 12:52:12 -0800, Steve Langasek wrote: > That would seem to fit with the rest of the page. I guess a bug > report is in order? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562890 -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Re: where is /etc/hosts supposed to come from?

On Mon, Dec 28, 2009 at 08:14:51PM +0100, Vincent Lefevre wrote: > On 2009-12-27 14:22:53 -0800, Steve Langasek wrote: > > No, the hostname should be set on a *separate* line, mapped to 127.0.1.1, > > as we've been doing for years now. Setting an equivalence between localhost > > and the hostname

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mo, 28 Dez 2009, Neil Williams wrote: > svn-buildpackage 0.7.1 can cope with dpkg source format 3.0 - in the > context of using an .orig.tar.bz2 but not (yet) with multiple tarballs. > Have you tried that version with TeX Live? If there are things that Honestly, building TL packages is too comp

Re: bug #561324: asking questions in postinst

Reinier Haasjes writes: > I'm trying to solve bug #561324 which uses it's own binary in the config > script. > It uses it's own binary to get some information (tunnel id) which uses > login+password to retrieve, it really needs this to compile a good > config script (if you have more than 1 tunn

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mo, 28 Dez 2009, Iustin Pop wrote: > As others have remarked, the working copy is polluted with 1.0 too, and > you would need to run debian/rules clean to get back to a pristine > state. See my other email, that is *wrong*. I was talking about dpkg-buildpackage -us -uc -rfakeroot -S (

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Iustin Pop writes: > Furthermore, by standardising on quilt patches, I hope that we will move > away from directly patching upstream source in the debian diff.gz, which > I find very sloppy work. If patches to the upstream source are maintained in Git or some other full-featured revision control

Re: Bug#545782: imagemagick-dbg: missing README.Debian to explain how programs are used

Jari Aalto wrote: > In latest lintian, a message was added that warned about missing > > debian/REAADME.source > > in order to document the used patch system (dpatch, quilt etc.). It > could have been be argued that this information were already available > in the manual pages. That's why #5

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On So, 27 Dez 2009, Russ Allbery wrote: > >> My .quiltrc includes this: > >> > >> QUILT_PATCHES=debian/patches > > No, there's a more general recipe for selectively setting QUILT_PATCHES in > the documentation in the quilt package. Pointers please? I checked README.Debian, README.gz, quilt.t

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mo, 28 Dez 2009, Raphael Hertzog wrote: > > Mind that git-buildpackage with normal 1.0 source format does NOT pollute > > the git repository, so my expectation is that the 3.0 format does the > > same, but alas, it doesn't. > > Well, if you have the usual quilt rules, you working copy is also m

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mo, 28 Dez 2009, Norbert Preining wrote: > > No, there's a more general recipe for selectively setting QUILT_PATCHES in > > the documentation in the quilt package. > > Pointers please? I checked README.Debian, README.gz, quilt.txt.gz, > and quilt.quiltrc for QUILT_PATCHES but didn't find anythi

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Joey Hess wrote: > Joachim Wiedorn wrote: > > I still use CDBS and I use "simple-patches" - but now without CDBS > > support. My minor change is the file "patches/series" which let > > dpkg-buildpackages know that there are patches. This seems very simple, > > too. To get the old manner, I must o

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Joachim Wiedorn wrote: > I still use CDBS and I use "simple-patches" - but now without CDBS > support. My minor change is the file "patches/series" which let > dpkg-buildpackages know that there are patches. This seems very simple, > too. To get the old manner, I must only delete the series file an

automake and intermediate files generated by yacc, lex, valac

Hi, there are several tools that generate C source code that is later complied in object code, e.g. yacc, lex or valac. automake defaults to distribute these built intermediate files, so they are usually not regenerated during a build. This causes several problems: 1. The intermediate files mig

Re: GDM, getty and VTs

On Mon, Dec 28, 2009 at 12:53:27PM -0600, Mark Allums wrote: > On 12/27/2009 12:21 AM, Gaijin wrote: > Ice > >Weasel won't run many web pages as well as it does in Windows Firefox, > >including my Linksys router's configuration page, > > > Iceweasel will run everything Firefox on Windows will,

Re: GDM, getty and VTs

On 12/27/2009 12:21 AM, Gaijin wrote: Ice Weasel won't run many web pages as well as it does in Windows Firefox, including my Linksys router's configuration page, Iceweasel will run everything Firefox on Windows will, excepting things where the problem is Linux versus Windows. It might hel

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Joachim Wiedorn wrote: > No, I don't use an debian/rules based patch system. The patches will be > used by dpkg-buildpackage because I have created the patches/series > file. So inside dpkg the quilt-management of the patches will be used. > But I don't use quilt outside the dpkg system. > > Pleas

Re: bug #561324: asking questions in postinst

Hi, > Why? Is it really required to have _all_ questions in the postinst? No, not all. There are 4 questions asked. 1) brokers list, the list is received by the package-binary and the user selects te broker he wants to use. For this I can use a dns-query (type TXT) but dig and host are both not e

Re: where is /etc/hosts supposed to come from?

On 2009-12-27 14:22:53 -0800, Steve Langasek wrote: > No, the hostname should be set on a *separate* line, mapped to 127.0.1.1, > as we've been doing for years now. Setting an equivalence between localhost > and the hostname causes all manner of problems due to hostname > canonicalization. Should

Re: where is /etc/hosts supposed to come from?

On 2009-12-28 14:34:39 +1100, Brian May wrote: > Also, FQDNs are really not applicable to, say laptops, which > frequently change from one network to another. Or some desktops > even. I notice on this Ubuntu laptop `hostname` == `hostname -f` > perhaps for this reason. FQDNs are also applicable to

Re: bug #561324: asking questions in postinst

Hi Reiner, On Mon, Dec 28, 2009 at 04:40:50PM +0100, Reinier Haasjes wrote: > Hi, > > I'm trying to solve bug #561324 which uses it's own binary in the config > script. > > It uses it's own binary to get some information (tunnel id) which uses > login+password to retrieve, it really needs this t

Re: bug #561324: asking questions in postinst

Hi, On Mon, Dec 28, 2009 at 04:40:50PM +0100, Reinier Haasjes wrote: > I'm trying to solve bug #561324 which uses it's own binary in the config > script. > > It uses it's own binary to get some information (tunnel id) which uses > login+password to retrieve, it really needs this to compile a good

Re: bug #561324: asking questions in postinst

On Mon, 28 Dec 2009 16:40:50 +0100 Reinier Haasjes wrote: > I'm trying to solve bug #561324 which uses it's own binary in the > config script. > > It uses it's own binary to get some information (tunnel id) which uses > login+password to retrieve, it really needs this to compile a good > config

bug #561324: asking questions in postinst

Hi, I'm trying to solve bug #561324 which uses it's own binary in the config script. It uses it's own binary to get some information (tunnel id) which uses login+password to retrieve, it really needs this to compile a good config script (if you have more than 1 tunnel). My idea on solving this i

Bug#562861: ITP: remmina-xfce -- XFCE applet for Remmina

Package: wnpp Owner: Luca Falavigna Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org * Package name: remmina-xfce Version : 0.7.0 Upstream Authors: Vic Lee * URL : http://remmina.sourceforge.net/ * License : GPLv2+ Programming Lang: C Descrip

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

Hello, Am Mon, 28 Dec 2009 01:25:17 +0100 schrieb Iustin Pop : > Sorry to hear about your bad experience. I use the same workflow, > git-buildpackage + 3.0 (quilt) and I have no problems so far. Before I have made official Debian packages I have collected many experience with format 1.0 and

Bug#562848: RFP: pencil -- animation/drawing software

Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org --- Please fill out the fields below. --- debian package: http://www.pencil-animation.org/index.php?id=Download Package name: pencil Version: 0.4.4 Upstream Author: [NAME ] URL: [http://www.pencil-

Re: where is /etc/hosts supposed to come from?

On Mon, Dec 28, 2009 at 12:58:03AM -0800, John H. Robinson, IV wrote: > Hence /etc/hostname.hme0:1 and the like. Already solved. # ip addr add eth0 192.168.1.1 # ip addr add eth0 192.168.1.2 # cat /etc/hosts 192.168.1.1 www.foo.com 192.168.1.2 smtp.bar.org Now what /etc/hostname.eth0 sho

Re: Increasing developer productivity through tools

Le jeudi 24 décembre 2009 à 10:52 +0100, Florian Weimer a écrit : > Have you got any suggestions for increasing productivity with proper > IDE support for medium-sized C and C++ code bases? I’ve mostly been hearing good about anjuta, kdevelop and monodevelop. -- .''`. Josselin Mouette : :

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mon, 28 Dec 2009 12:29:48 +0100 Joerg Jaspert wrote: > > (Personally, I'm not happy with 3.0 either, I see no sufficient > > benefit to use it unless the upstream tarball is a .tar.bz2. It's > > not cleaner, lsdiff -z is no different to tar -tzf. However, I will > > do what I can to allow 3.0

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

> (Personally, I'm not happy with 3.0 either, I see no sufficient benefit > to use it unless the upstream tarball is a .tar.bz2. It's not cleaner, > lsdiff -z is no different to tar -tzf. However, I will do what I can > to allow 3.0 to work within svn-bp for the few packages that may > benefit.)

Re: Bug#545782: imagemagick-dbg: missing README.Debian to explain how programs are used

On Dec 28, Jari Aalto wrote: > It would be good if something similar were adopted to *-dbg packages as No, it would not since as it has been explained they all work the same way (i.e. you install one and it magically works). -- ciao, Marco signature.asc Description: Digital signature

Re: Bug#545782: imagemagick-dbg: missing README.Debian to explain how programs are used

"Nelson A. de Oliveira" writes: >> README.Debian to explain how programs are used". Please provide > > The problem here is that we have a lot of -dbg packages on Debian > Do we need the same README file on all of them? > > ...the package maintainer is responsible in helping the user to get a > bac

Re: where is /etc/hosts supposed to come from?

On Mon, Dec 28, 2009 at 03:52:44AM +0100, Marco d'Itri wrote: > Considering that any non-trivial server needs to send email out, having > a working FQDN configured is not "obsolete". Anything mail related must use /etc/mailname if it needs something that can be translated to an IP address. > You

Re: where is /etc/hosts supposed to come from?

Gabor Gombas wrote: > On Sun, Dec 27, 2009 at 10:38:58PM -0800, John H. Robinson, IV wrote: > > > This is one place where Solaris has gotten this right: /etc/nodename > > refers to the system itself, while each interface has its own (cf: > > /etc/hostname.hme0). > > That is still no good for linu

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mon, 28 Dec 2009 01:38:43 +0100 Norbert Preining wrote: > > cleaner - no longer quilt-specific stuff in debian/rules, and a nice > > debian.tar.gz instead of a diff. > > Beh, I disagree, the 3 different lines in debian/rules are NOT bad > by itself, it shows that *something* is changed. And

Re: Bug#545782: imagemagick-dbg: missing README.Debian to explain how programs are used

On Mon, Dec 28, 2009 at 11:09:34AM +0200, Jari Aalto wrote: > "Nelson A. de Oliveira" writes: > >> README.Debian to explain how programs are used". Please provide > > > > The problem here is that we have a lot of -dbg packages on Debian > > Do we need the same README file on all of them? > > > > .

Re: where is /etc/hosts supposed to come from?

On Sun, Dec 27, 2009 at 10:38:58PM -0800, John H. Robinson, IV wrote: > This is one place where Solaris has gotten this right: /etc/nodename > refers to the system itself, while each interface has its own (cf: > /etc/hostname.hme0). That is still no good for linux since a single interface can hav

Re: where is /etc/hosts supposed to come from?

On Sun, Dec 27, 2009 at 10:38:58PM -0800, John H. Robinson, IV wrote: > Brian May wrote: > > On Mon, Dec 28, 2009 at 03:52:44AM +0100, Marco d'Itri wrote: > > > Considering that any non-trivial server needs to send email out, having > > > a working FQDN configured is not "obsolete". > > > > I beli

Re: quilt 3.0 source format and dpkg-source/dpkg-buildpackage

On Mon, Dec 28, 2009 at 01:38:43AM +0100, Norbert Preining wrote: > On Mo, 28 Dez 2009, Iustin Pop wrote: > > Sorry to hear about your bad experience. I use the same workflow, > > git-buildpackage + 3.0 (quilt) and I have no problems so far. > > Good for you. > > > Are you using --git-export-dir?