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

On Tue, Dec 29 2009, Russ Allbery wrote: > I think the way forward for Git-maintained packages is the 3.0 (git) > format, but changed to ship a bundle. That way, relevant branches and > history can be included, and Git is fairly space-efficient so the > additional cost of doing so isn't that bad.

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

Manoj Srivastava writes: > On Tue, Dec 29 2009, Russ Allbery wrote: >> I think the way forward for Git-maintained packages is the 3.0 (git) >> format, but changed to ship a bundle. That way, relevant branches and >> history can be included, and Git is fairly space-efficient so the >> additional

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

On Mon, Dec 28, 2009 at 10:40:34PM -0800, Russ Allbery wrote: > 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 pro

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

]] Joey Hess | I think you should be using a dedicated source format for your patch | system, preferably one that preserves the pre-patched source on unpack | invariant. Either the existing 3.0 (custom), or a new 3.0 subformat. Note that those won't be accepted into the archive (at least not wit

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

On Tue, Dec 29, 2009 at 08:46:09AM +0100, Vincent Bernat wrote: > And BTW, this is exactly what hostname -f does. It does not read > /etc/hostname. Nothing should read /etc/hostname except /etc/init.d/hostname.sh during boot. Everything else should use either uname(2) or gethostname(3) (which in

Re: 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. > [...] Why do you restrict this question to g

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

Hi, On Mon, 28 Dec 2009, Norbert Preining wrote: > $ git-buildpackage -us -uc -rfakeroot -S [...] > nothing to commit (working directory clean) > $ > > So please tell me *what* has changed? That's because you're doing a source only build. With a binary build, patches would have been applied. I

Re: automake and intermediate files generated by yacc, lex, valac

On Tue, Dec 29, 2009 at 03:23:21AM +0900, Ansgar Burchardt wrote [edited]: > 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

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

On Di, 29 Dez 2009, Raphael Hertzog wrote: > That's because you're doing a source only build. With a binary build, > patches would have been applied. I always build my packages in a clean chroot and not in my life system. Best wishes Norbert --

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

On Tue, Dec 29, 2009 at 12:21:45AM +, Sam Morris wrote: > What would a hypothetical host that only had IPv6 connectivity do? It's not "hypothetical". IPv4 sucks so badly compared to IPv6 that once you switch your internal hosts to v6-only, you don't want to go back. While getting IPv6 connec

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

On Dec 29, 2009, at 8:46, Vincent Bernat wrote: > 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 >>>

Bug#562942: ITP: liblog4ada -- An Ada library for flexible logging

Package: wnpp Severity: wishlist Owner: xavier.gr...@ipno.in2p3.fr * Package name: liblog4ada Version : 1.0 Upstream Author : Xavier Grave * URL : http://www.ada-france.org:8081 branch org.log4Ada * License : GPL Programming Lang: Ada Description : An

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

On 2009-12-28 20:56:03 -0800, Steve Langasek wrote: > 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 l

Re: bug #561324: asking questions in postinst

On Mon, Dec 28, 2009 at 07:44:56PM +0100, Reinier Haasjes wrote: >> 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 t

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

On 2009-12-29 14:09:49 +0100, Jeremiah Foster wrote: > On one of my machines apticron uses a call to hostname -f, which > fails, while uname -n succeeds. "uname -n" doesn't necessarily return the FQDN. xvii% uname -n xvii xvii% hostname xvii xvii% hostname -f xvii.vinc17.org xvii% cat /etc/hostna

Re: bug #561324: asking questions in postinst

Hi, On Tue, Dec 29, 2009 at 02:38:46PM +0100, Lionel Elie Mamane wrote: > On Mon, Dec 28, 2009 at 07:44:56PM +0100, Reinier Haasjes wrote: > > >> 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 r

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

Hello, Joachim Wiedorn wrote: > The only missing item for me is: there are no simple command to unapply > the patches with dpkg-buildpackages (or debuild). For example: > >debuild unapply Even though there are some newer Mails this question seems to not be solved. Is it true, that I need

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

On Mon, Dec 28, 2009 at 12:29:48 +0100, Joerg Jaspert wrote: > It would have been MORE than easy to have bz2 support in 1.0. There is > absolutely no reason why it needs a 3.0 just for a different compression. > But that wasnt wanted. By whom? dpkg maintainers, archive admins, package maintainer

Re: bug #561324: asking questions in postinst

Hi, On Tue Dec 29, 2009 at 15:13:54 +0100, Patrick Schoenfeld wrote: > Hi, > > On Tue, Dec 29, 2009 at 02:38:46PM +0100, Lionel Elie Mamane wrote: > > On Mon, Dec 28, 2009 at 07:44:56PM +0100, Reinier Haasjes wrote: > > > > >> Why? Is it really required to have _all_ questions in the postinst?

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

Luca Falavigna (28/12/2009): > Description : XFCE applet for Remmina > Remmina-XFCE is a XFCE applet for the Remmina application. This XFCE > desktop applet allows for easy-access of the Remmina main features. > Remmina-XFCE is also able to list all remote desktop files and makes > t

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

> On Mon, Dec 28, 2009 at 12:29:48 +0100, Joerg Jaspert wrote: It would > > have been MORE than easy to have bz2 support in 1.0. There is > > absolutely no reason why it needs a 3.0 just for a different > > compression. But that wasnt wanted. [Julien Cristau] > By whom? dpkg maintainers, archiv

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

On Tue, Dec 29, 2009 at 10:04:19AM -0600, Peter Samuelson wrote: > Presumably dpkg maintainers. I've long suspected that the main reason > they chose not to add tar.bz2 to format 1.0 is, if they did, a lot of > us would have no reason to want format 3.0. Many packagers don't need > multiple tarba

Re: bug #561324: asking questions in postinst

Le mardi 29 décembre 2009 à 14:38 +0100, Lionel Elie Mamane a écrit : > Well, this could be solved by a pre-depends on dnsutils | > bind9-host. Pre-depends are often frowned upon, what do others think > of this for this case? It is utterly and absolutely useless, since config scripts are executed

Re: bug #561324: asking questions in postinst

On Tue, Dec 29, 2009 at 05:32:29PM +0100, Josselin Mouette wrote: > Le mardi 29 décembre 2009 à 14:38 +0100, Lionel Elie Mamane a écrit : > > Well, this could be solved by a pre-depends on dnsutils | > > bind9-host. Pre-depends are often frowned upon, what do others think > > of this for this case?

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

On Tue, Dec 29, 2009 at 17:35:53 +0100, Stefano Zacchiroli wrote: > Format 3.0 is more than .bz2 support. And we're saying .bz2 support is the only thing in it we care about, and didn't need to come with 3.0's drawbacks. [...] > Finally, nobody is forced to use it: if you don't like it, just avo

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

On Mon, 2009-12-28 at 20:56, Steve Langasek wrote: > 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 li

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

Hello Nick, Nick Shaforostoff wrote: > Package: wnpp > Severity: wishlist > X-Debbugs-CC: debian-devel@lists.debian.org > > --- Please fill out the fields below. --- It is a best practice to fill all the fields below (they wouldn't be in the template otherwise ;) >Package name: pencil >

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

On Tue, Dec 29, 2009 at 04:52:59PM +, Julien Cristau wrote: > > Format 3.0 is more than .bz2 support. > And we're saying .bz2 support is the only thing in it we care about, and > didn't need to come with 3.0's drawbacks. And I'm still saying that ranting _here_ about that is pointless. Submit

Bug#562968: ITP: otpasswd -- one-time passwords implementation for PAM

Package: wnpp Severity: wishlist Owner: Luke Faraone * Package name: otpasswd Version : 0.4 Upstream Author : Tomasz bla Fortuna * URL : http://savannah.nongnu.org/projects/otpasswd/ * License : GPLv3+ Programming Lang: C Description : one-time pas

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

Hi, On Tue, 29 Dec 2009, Norbert Preining wrote: > On Di, 29 Dez 2009, Raphael Hertzog wrote: > > That's because you're doing a source only build. With a binary build, > > patches would have been applied. > > I always build my packages in a clean chroot and not in my life system. I do the same (

Re: defaulting to net.ipv6.bindv6only=1 for squeeze

* Hendrik Sattler [091226 18:48]: > > Does that mean your application only works if the kernel supports > > IPv6? > > Why would you want to disable basic IPv6 support? I routinely blacklist the ipv6 module. There are far too many programs breaking or doing stuff I do not want if it is loaded. Ho

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

On Tue, Dec 29, 2009 at 02:52:44PM +0100, Vincent Lefevre wrote: > When the machine is correctly configured (i.e. really has a FQDN), > "hostname -f" is reliable. No, it is not. "hostname -f" can return one value only, while a host may have dozens or hundreds of valid FQDNs. Example: there is a

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

Hi, On Tue, 29 Dec 2009, Stefano Zacchiroli wrote: > On Tue, Dec 29, 2009 at 04:52:59PM +, Julien Cristau wrote: > > > Format 3.0 is more than .bz2 support. > > And we're saying .bz2 support is the only thing in it we care about, and > > didn't need to come with 3.0's drawbacks. > > And I'm s

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

On Tue, 29 Dec 2009, Joachim Wiedorn wrote: > Even though there are some newer Mails this question seems to not be > solved. > > Is it true, that I need an installed quilt to unapply the patches? Yes. With "3.0 (quilt)", the default state is "patches are applied" (since that's what you get when

Bug#562976: ITP: python-ev -- Python bindings to libev

Package: wnpp Severity: wishlist Owner: Julien Danjou * Package name: python-ev Version : 0.5.3 Upstream Author : Malek Hadj-Ali * URL : http://code.google.com/p/pyev/ * License : BSD/GPL-3 Programming Lang: C, Python Description : Python bindings to li

Re: defaulting to net.ipv6.bindv6only=1 for squeeze

On Tue, 2009-12-29 at 18:37 +0100, Bernhard R. Link wrote: > * Hendrik Sattler [091226 18:48]: > > > Does that mean your application only works if the kernel supports > > > IPv6? > > > > Why would you want to disable basic IPv6 support? > > I routinely blacklist the ipv6 module. There are far too

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

Peter Samuelson writes: > Presumably dpkg maintainers. I've long suspected that the main reason > they chose not to add tar.bz2 to format 1.0 is, if they did, a lot of > us would have no reason to want format 3.0. Many packagers don't need > multiple tarballs or non-text files, and are quite ha

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

On Mon, 2009-12-28 at 22:40 -0800, Russ Allbery wrote: > I think the way forward for Git-maintained packages is the 3.0 (git) > format, but changed to ship a bundle. That way, relevant branches and > history can be included, and Git is fairly space-efficient so the > additional cost of doing so is

Re: bug #561324: asking questions in postinst

Patrick Schoenfeld writes: > Uhm, yes, you are right. So it wouldn't help anyway. Only possibility > would be a versioned dependency (according to [1]) or to really do it in > the postinst. Leads to the question which of the solution we'd prefer. > [1] http://www.debian.org/doc/debian-policy/ch-

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

Felipe Sateler writes: > On Mon, 2009-12-28 at 22:40 -0800, Russ Allbery wrote: >> I think the way forward for Git-maintained packages is the 3.0 (git) >> format, but changed to ship a bundle. That way, relevant branches and >> history can be included, and Git is fairly space-efficient so the >>

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

Vincent Lefevre writes: > Even if Debian has its own patches to match its policy, end users are > still allowed to compile software from upstream (this is what I do for > Mutt, because I have my own patches), and they expect such software to > work. If you expect the software you use to be prope

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

Frank Lin PIAT (29/12/2009): > It is a best practice to fill all the fields below (they wouldn't be > in the template otherwise ;) > […] > Usually, it is a good idea to write the full package description > that you would use for the upload... so people can give feed back. Better yet, check the BT

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

Niko Tyni wrote: >> Could you please run the failing tests with Expat directly, instead of the >> Perl parser? > > I'm able to reproduce (at least part of) the problem without the Perl > bindings, using the 'xmlwf' example tool from the expat source (shipped > in the 'expat' package on Debian.) >

Bug#562980: RFP: iFolder -- keeps synchronized the directories on many computers

Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org Package name: iFolder Version: 3.8 Upstream Author: Novell (Bipin sivaraman, Ravi Kumar, Joe 'Zonker' Brockmeier) URL: http://sourceforge.net/projects/ifolder/ License: GPL Description:

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

On 2009-12-29 18:49:00 +0100, Gabor Gombas wrote: > On Tue, Dec 29, 2009 at 02:52:44PM +0100, Vincent Lefevre wrote: > > When the machine is correctly configured (i.e. really has a FQDN), > > "hostname -f" is reliable. > > No, it is not. "hostname -f" can return one value only, while a host may >

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

On 2009-12-29 17:44:31 +0100, Milan P. Stanic wrote: > Mutt in testing/unstable use /etc/mailname. But not the official Mutt version. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic /

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

On 2009-12-29 10:45:17 -0800, Russ Allbery wrote: > Vincent Lefevre writes: > > Even if Debian has its own patches to match its policy, end users are > > still allowed to compile software from upstream (this is what I do for > > Mutt, because I have my own patches), and they expect such software t

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

Vincent Lefevre writes: > When I compile Mutt or any other portable software (e.g. conforming to > POSIX), I don't mind if such software isn't integrated with the Debian > system. I just want it work according to the POSIX spec. If it doesn't > because the system configuration doesn't comply to P

Bug#563004: ITP: procserv -- A process server with telnet console and log access

Package: wnpp Severity: wishlist Owner: Ralph Lange * Package name: procserv Version : 2.5.0 Upstream Author : Ralph Lange * URL : http://sourceforge.net/projects/procserv/ * License : GPLv3 Programming Lang: C++ Description : A process server with te

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

>> It would have been MORE than easy to have bz2 support in 1.0. There is >> absolutely no reason why it needs a 3.0 just for a different compression. >> But that wasnt wanted. > By whom? dpkg maintainers, archive admins, package maintainers? > tar.bz2 support is the only reason I see for conside

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

On 2009-12-29 14:18:47 -0800, Russ Allbery wrote: > Vincent Lefevre writes: > > When I compile Mutt or any other portable software (e.g. conforming to > > POSIX), I don't mind if such software isn't integrated with the Debian > > system. I just want it work according to the POSIX spec. If it doesn

Intel 845G Card not working on SID..

I Just upgraded to SID from Lenny and I am having a problem with the Graphics Card. Someone please help me out here on Intel Graphics cards is not working on SID platform. I am seeing an error on my Intel 82845G Integrated Graphic Device A message drm:i915_gem_execbuffer] *ERROR* Execbuf while wed

Re: Intel 845G Card not working on SID..

On Tue, Dec 29, 2009 at 06:30:42PM -0800, mukund jampala wrote: > I Just upgraded to SID from Lenny and I am having a problem with the > Graphics Card. Someone please help me out here on Intel Graphics cards is > not working on SID platform. Report bugs to the Bug Tracking System, not debian-devel

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

Le Tue, Dec 29, 2009 at 10:33:45AM -0800, Russ Allbery a écrit : > > * Support for other compression methods. > * Multiple upstream source tarballs. > * Apply patches so that dpkg-source -x gives buildable source. > * Ship debian/* as a tarball instead of a patch. > * Allow binaries in the debian

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

Vincent Lefevre writes: > Yes, but a failure is something one can expect to happen under some > occasions, at least for remote hosts. This doesn't mean that hosts don't > have a canonical name, just that this canonical name couldn't be > determined. > For the local host, I would say that a failu

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

Charles Plessy writes: > In my opinion, much of the current disagreements come from two false needs: > * Apply patches so that dpkg-source -x gives buildable source. That was the need that had as much or more project consensus as anything else on my list, and as I recall was the impetus for do

Re: bug #561324: asking questions in postinst

On Tue, Dec 29, 2009 at 10:37:45AM -0800, Russ Allbery wrote: > Patrick Schoenfeld writes: > > > Uhm, yes, you are right. So it wouldn't help anyway. Only possibility > > would be a versioned dependency (according to [1]) or to really do it in > > the postinst. Leads to the question which of the

Re: bug #561324: asking questions in postinst

Patrick Schoenfeld writes: > On Tue, Dec 29, 2009 at 10:37:45AM -0800, Russ Allbery wrote: >> Patrick Schoenfeld writes: >>> Uhm, yes, you are right. So it wouldn't help anyway. Only possibility >>> would be a versioned dependency (according to [1]) or to really do it in >>> the postinst. Leads

Re: Bug#563004: ITP: procserv -- A process server with telnet console and log access

Hello, On Tue, 2009-12-29 at 17:35 -0500, Ralph Lange wrote: > > * Package name: procserv > * URL : http://sourceforge.net/projects/procserv/ > Description : A process server with telnet console and log access > > procServ is a wrapper that starts an arbitrary command as a

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

OoO En cette fin de nuit blanche du mercredi 30 décembre 2009, vers 05:23, Russ Allbery disait : >> I haven't said that. And this is often not the case under Debian, >> i.e. the FQDN is often obtained from /etc/hosts, which has the >> precedence over DNS (see /etc/nsswitch.conf). > I have n

Re: bug #561324: asking questions in postinst

On Tue, Dec 29, 2009 at 11:01:58PM -0800, Russ Allbery wrote: > Patrick Schoenfeld writes: > > On Tue, Dec 29, 2009 at 10:37:45AM -0800, Russ Allbery wrote: > >> Patrick Schoenfeld writes: > > >>> Uhm, yes, you are right. So it wouldn't help anyway. Only possibility > >>> would be a versioned de

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

Vincent Bernat writes: > Russ Allbery disait: >>> I haven't said that. And this is often not the case under Debian, >>> i.e. the FQDN is often obtained from /etc/hosts, which has the >>> precedence over DNS (see /etc/nsswitch.conf). >> I have no entry in /etc/hosts other than 127.0.0.1 and the

Re: bug #561324: asking questions in postinst

Patrick Schoenfeld writes: > Debconf or another tool that implements the Debian Configuration > Management Specification will also be installed, and any versioned > dependencies on it will be satisfied before preconfiguration begins. Oh, sorry, I didn't think to check the footnote. However, I t