Re: Resolvconf -- suggested reading before installing this :-)

[Thomas Hood]

On Mon, 2003-09-29 at 23:53, Osamu Aoki wrote: 
> Whomever interested on this subject, Thomas' network set up tutorial
> (draft) is available as "10 Network configuration":
> 
>   http://qref.sourceforge.net/Debian/reference/ch-gateway.en.html
>
> (Yes, he is rewriting my old small section with whole new section with
>  very good overview.  Please tell Thomas about any problem in 10.1-10.8.
>  Please understand this is on-going update.)

Thanks to Osamu for mentioning this.  Emphasis on the "on-going".
I would appreciate help, including proof reading.  

The Debian Reference promises to fill the gap between HOWTO and
how-to-do-it-in-Debian.

Before starting to work on DR chapter 10 I checked to see what
else was available.  To my surprise I found an assortment of
documents besides the familiar Installation Manual and Release
Notes:

  * Debian GNU/Linux FAQ
  * [formerly Progeny] User's Guide
  * [dwarf's] Debian Linux User's Guide
  * Debian GNU/Linux: Guide to Installation and Usage
  * Debian Tutorial
  * Debian User Reference Manual
  * Debian System Administrator's Manual
  * Debian Network Administrator's Manual

Links to all of these can be found at 
http://www.debian.org/doc/user-manuals#users-guide
along with commentary on their contents and status.

The FAQ seems to be up to date and maintained.  The three
user's guides look complete but more or less out of date.
The rest appear to be incomplete.  If there are newer versions
of any of these floating around that aren't available via the
link above then I would appreciate someone sending me a URL.

For DR ch.10 I have been consulting chapters 3 and 8 of the
Debian Network Administrator's Manual by Duncan C Thomson and
Ivan E. Moore II.  I really should drop those guys a line ...

-- 
Thomas Hood <[EMAIL PROTECTED]>

Re: ITH: icu

[Martin Michlmayr]

* Ivo Timmermans <[EMAIL PROTECTED]> [2003-09-10 07:05]:
> > > We (Daniel Glassey and Ivo Timmermans) are going to take over the
> > > package icu from Yves Arrouye <[EMAIL PROTECTED]>.  Yves has failed to
> > > respond (his hotmail address, that he last used in communication, is
> > > over quotum, and other email went unanswered) to bugs and other email.
> > > 
> It's waiting in queue/new.

Would you mind taking over icu and icu-docs?
-- 
Martin Michlmayr
[EMAIL PROTECTED]

Re: Debian should not modify the kernels!

[martin f krafft]

also sprach Adam Borowski <[EMAIL PROTECTED]> [2003.09.28.0744 +0200]:
> Well... as 2.6 is coming out really soon, ipsec is in a lot better 
> position than grsec.  Also, you will _have_ to port grsec to 2.6 (or 
> abandon it), and 2.6 will have ipsec in the upstream sources.  The only 
> difference lies in needing to do the porting work a bit sooner.

Bollocks. I am the Debian maintainer, I won't do any porting.
grsecurity will support the 2.6 kernel series when it is released.
Then I will port the new patches to Debian. Then, the problem will
be fixed.

However, I still don't think that this closes the issue. I think
feature backports to the kernel-source packages should not happen!

How do y'all suggest we continue on this, because apparently there
are two camps with different opinions, Herbert doesn't think he
needs to do anything, and this issue will just die without a change
happening. I think we have to properly address and close the whole
thing!

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpNbHcjozcvY.pgp
Description: PGP signature

Re: Bug#213127: ITP: extlib -- extended standard library for OCaml

[Stefano Zacchiroli]

On Mon, Sep 29, 2003 at 11:06:55AM -0400, Anthony DeRobertis wrote:
> >Actually ExtLib contains modules implementing: enumeration over 
> >abstract
> I suggest striking "actually"

Seconded!

-- 
Stefano Zacchiroli  --  Master in Computer Science @ Uni. Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it}  -  http://www.bononia.it/zack/
"  I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant!  " -- G.Romney

How many different configurations of Debian systems are out there?

[Auke Jilderda]

I'm curious how many different configurations of Debian systems are out
there.  Hence, how many distinct configurations are theoretically
possible within the managed space of versions of packages, defined by
the dependency graph?  

It would be very interesting to compare the amount variability the
Debian community supports with commercial products.  I guess, a script
analysing the package information retrieved by apt-get should be able
figure this out.  Is there any software that can provide such (or even
remotely related) information?


Auke

-- 
PGP: 0x4A34DD6D, http://bunny.sourceforge.net/

paella

[Joseph Rawson]

abstract

Paella is system for creating/installing customized debian systems.
There are no current plans for configuration updates on live systems,
that's not it's initial purpose, although it may be extended later.

Paella is still in a planning state, and the configuration ability is 
real simple right now.

Inspiration for paella comes from many places:

debconf -- an important abstract configuration system
which is sadly not yet supported by paella (can somebody help
me?)
debconf is fully planned to be supported, i just haven't
figured out the best way to template a debconf template
and whether to crete a flat db, use a dir/db over nfs, or
ldap (which sounds like the best shot, though i'm unfamiliar
with it)
paella is not a replacement for debconf.

fai -- fully automatic install
an excellent installer, with the capability of bootstrapping
an entire network!  paella was going to just complement fai,
but I'm starting to prefer the configuration layout i'm
planning,
so paella will probably completely replace fai

Knoppix -- and Morphix, Gnoppix, and other live cd's
paella will eventually be a jigdo-ish like description
of the cd, so it will be easier to construct the cd's
from a local repository, and modify them before creation

OpenZaurus -- and Matt Zimmerman's efforts with debian-handhelds
building oz is a pita, i'm not used to bitkeeper and I can't
find a specific build-root for a specific release.  It's like
the 
source is available, but not specifically per package.  Overall
though, i have found the openzaurus cross compiling solution
to be the most preferable way to build source for an
embedded device.  My solution now is to use paella,
and pbuilder (thanks, for the work in getting so many
packages to autobuild! ;)) to define, bootstrap, and control
cross compiling pbuilders with autobuilt toolchains.  This
should
make it easier to script autobuilds of an embedded systems,
patches and all :)

Demudi, Debian-Lex, ...
I think paella can be very instrumental in helping configure and
install a custom network on a per network type basis, (i.e. what
machines are on the network and what are there jobs, expected
activities, etc.  I am also thinking of networks with custom
configured
roaming pda's, laptops, or whatever can take a debian system

and that is also probably the order i will be working in.

I am aware that customized packages can be made and distributed (like
tasksel and jablicator), but it is not paella's designed purpose to be
used
in that manner.  Once paella is done configuring and installing, it
should leave
no trace of itself.  The user should be left with a clean, customized
debian 
system.  This is mainly a tool meant for somebody who is going to be
creating,
configuring, and installing many debian systems.

I have tried to make a common denominator that most of these pojects
share,
but seem to be missing.

My urgent need to get this system working so i can starting earning a
living
with it, has caused to code to wind up a bit sloppy. Sorry.

all of the code is in cvs, the schema has been changing too much for any
kind of release.  I would also like to make a request for comments
before making a release, as i don't want to do something really stupid
:).  I am still a newbie with the release and versioning stuff.

anyway, the project is at http://sourceforge.net/projects/paella/

btw, paella is like a little bit of everything, with debian as rice.

updating a deb

[Filippo Basso]

Hi all,
   I'm now playing with deb files, and had a nice day making my first 
deb, and my local repository...
Just a problem: if I update the deb (correct the problem, dch -i, and 
again dpkg-buildpackage), simple apt-get update doesn't work, I need to 
purge it before...
it's like it consider all files as conffiles!

what have i to do, to update pippo_1.0-1.deb into a pippo_1.0-2.deb so 
that I don't have to do
"dpkg -P pippo" before reinstall ?

thank you,
   please cc: [EMAIL PROTECTED]

Re: updating a deb

[Adam Heath]

On Tue, 30 Sep 2003, Filippo Basso wrote:

> Hi all,
> I'm now playing with deb files, and had a nice day making my first
> deb, and my local repository...
> Just a problem: if I update the deb (correct the problem, dch -i, and
> again dpkg-buildpackage), simple apt-get update doesn't work, I need to
> purge it before...
> it's like it consider all files as conffiles!
>
> what have i to do, to update pippo_1.0-1.deb into a pippo_1.0-2.deb so
> that I don't have to do
> "dpkg -P pippo" before reinstall ?

edit debian/changelog.

summary of the Oldenberg d-i debcamp (and release plans)

[Joey Hess]

Between last Thursday and Sunday more than 10 debian-installer
developers participated in the d-i debcamp held during the Oldenburg
developer's meeting. It was quite a successful event, and we appreciated
the hospitality of the Oldenburg developers, and had a good time as well
as doing a lot of work on d-i. But then, if you're subscribed to d-i cvs
and survived the flood of commits, you probably already knew that.

I'll try to summarize everything we accomplished, as well as what
remains to be done. Any innacuracies are my own (please correct them),
and I apologize for leaving out the names of who did what -- too much to
keep track of, and I'm bad with names. The most important part of this
message is probably the last part, which concerns getting ready for the
release.

Perhaps the most significant accomplishment came from the powerpc
contingent, who got d-i fully installing on the powerpc. Motly this
involved fixing yaboot. Some powerpc subarchitectures still lack kernel
images, but this is a major step. Powerpc is perhaps better supported by
debian-installer right now than is i386.

We also have a mips port that is well under way, booting up to the main
menu (with some minor problems). I expect this port is moving too fast
right now for me to properly summarize it.

The alpha port still has boot issues. In particular, we still lack the
source to milo. This is unresolved. Despite this, CD images are in
progress.

There was also some s/390 sctivity, but I did not get a summary of
progress.

There was plenty of work on i386 as well. We have finally updated to the
2.4.22 kernel for i386 (up from 2.4.20), and the boot floppies have been
fixed to fit the new kernel, as well as having plenty of space to grow
on. There's now a page on the d-i wiki describing i386 netbooting of
debian-installer. The i386 boot disk should soon support usb keyboards,
usb storage devices, and pcmcia as well.

Quite a lot of work was done on general UI issues. The largest change
was increasing the default cdebconf priority to high so we can test how
the installer will actually behave for users. This testing is as yet
incomplete.

Several UI improvements were done in cdebconf, including fixing back
button display, wrapping of text in progress displays, and highlighting
error messages. We still need to comb through the d-i tree for error
messages and make sure they are templates of type "error" and not
"note". Other UI imporovements included making partconf behave sanely
when run a second time.

On the i18n front, main-menu's menu items can now be provided from
debconf templates to allow for easy translation with the rest of the
templates. This transition is still in progress. Along similar lines,
the debconf title can be set to the description of a debconf template
using the new SETTITLE command. This will allow for translated titles,
but there is still lots of code that calls TITLE and needs to be found
and fixed. So now we should have full i18n of everything except some
error messages and, well, the kernel boot messages. Translation work 
continues as usual.

Other work included work on discover2 data reduction (still in
progress), working out how d-i should talk to base-config (still needs
to be implemented), 

We also discussed things that still need to be done. Perhaps the most
important right now is the transition to the new version of
libdebian-installer. Unfortunatly, a lot has changed, and all code that
uses it will have to be updated. There should be a summary posted soon
regarding what has changed in libdebian-installer and how to deal with
it. The rough plan is to get a list of packages that need a fix, assign
them to d-i workers, and try to get the whole tree converted over to the
new version in a 1 week time frame. During this time frame, most other
development on d-i may be blocked.

Here are some other items that need work:

 - Make main-menu set the title of items it runs to the item's
   description (using the new SETTITLE command and the same description
   templates we're now in the process of adding. This will remove the
   need for much manual setting of titles at all, and it will avoid
   confusing titles retained from earlier parts of the installer.
 - Make main-menu not pester the user when a module exits nonzero (but
   detect modules that have crashed with a segfault, and warn then).
 - Try to better organize the language menu. This many involve
   maintaining it manually and picking the placement of new items when
   they are added. Some work on this has occured since I started this
   summary.
 - Some kind of subarch support is needed by a couple of archutectures,
   so d-i can know the approptiate partitioning tool, boot loader, etc
   to use for the subarchitecture it is being used with. We need a list
   of subarches, and a design. Work on this has started since I began to
   write this summary.
 - Add code to popularity context to track kernel module usage so we can
   better decide which to include w

d-i milo missing (might have fix)

[Greg Folkert]

On Tue, 2003-09-30 at 12:18, Joey Hess wrote:
> The alpha port still has boot issues. In particular, we still lack the
> source to milo. This is unresolved. Despite this, CD images are in
> progress.

Which version of milo are you referring to?

I still have 0.13 through 0.27 laying around. Will that help?
-- 
greg, [EMAIL PROTECTED]
REMEMBER ED CURRY! http://www.iwethey.org/ed_curry

An ocean-going tin of crosseyed mussels could never match the melodious
burblings of your sister's husband.


signature.asc
Description: This is a digitally signed message part

Re: updating a deb

[Filippo Basso]

Hi all,
   I'm now playing with deb files, and had a nice day making my first
deb, and my local repository...
Just a problem: if I update the deb (correct the problem, dch -i, and
again dpkg-buildpackage), simple apt-get update doesn't work, I need to
purge it before...
it's like it consider all files as conffiles!
what have i to do, to update pippo_1.0-1.deb into a pippo_1.0-2.deb so
that I don't have to do
"dpkg -P pippo" before reinstall ?
   

edit debian/changelog.
SOLVED
Thank you,
   that was what I did with "dch -i"...
what happened is that using dselect I couldn't see properly what was 
happening (asked me nothing, while doing "apt-get upgrade" I was asked of

Configuration file `/etc/logs/php/eth2'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : background this process to examine the situation
The default action is to keep your current version.
*** eth2 (Y/I/N/O/D/Z) [default=N] ?
so, the package system is thinking that eth2 is a configuration file... 
so if I cancel it, or modify, it isn't updated!
the problem was that any file in /etc directory is considered as 
conffile, I suppose, because changing it in /var all worked right.
thank you,
   filippo

Sitio WEB SIN CARGO

[MBProfesionales]

Title: flyermbp.jpg




  






  
  



  
  



  
  
4796
  - 5961 |
  www.dealnet.com.ar | [EMAIL PROTECTED]



  
  
SU EMPRESA EN INTERNET



  
  



  
  

  DESARROLLO DE SITES (sin prediseños)
  Desarrollo y diseño personalizado de sitios. 
   
  
  
  PLAN ACCESS (Consulte)
  Diseño y desarrollo total de su sitio sin cargo.
   
   
  HOSTING (con Panel de Control)
  Tenga independencia y el control de su sitio web con más de 40 herramientas
  para potenciar su sitio web 
   
   
  EL MEJOR SERVICIO POST VENTA
   Tenga
  un servicio incluído de actualización
  de contenidos de su página web sin costo.
  



  
  


  
  


  
  





  

NOTA: Si no deseas recibir mas correo de este
tipo, por favor responde este e-mail con "SACAR" en el asunto, y seras
quitado la lista. Muchas Gracias.



<>

Re: d-i milo missing (might have fix)

[Steve Langasek]

On Tue, Sep 30, 2003 at 12:49:29PM -0400, Greg Folkert wrote:
> On Tue, 2003-09-30 at 12:18, Joey Hess wrote:
> > The alpha port still has boot issues. In particular, we still lack the
> > source to milo. This is unresolved. Despite this, CD images are in
> > progress.
> 
> Which version of milo are you referring to?

> I still have 0.13 through 0.27 laying around. Will that help?

You tell us. :)  So far, no one has stepped forward to manage the MILO
side of things.  Dealing with aboot is easy; it's packaged in Debian, so
pulling it from the archive when building CD images is straightforward.
MILO, OTOH, is not packaged at all, and (if my knowledge is current) has
a rather grotesque build process due to its use of a stripped-down Linux
kernel as the second-stage bootloader.  Getting it somewhere that it can
be smoothly incorporated into the d-i builds is a challenge, one that's
likely to only be overcome by someone with a vested interest in the
MILO-dependent subarchs.

Cheers,
-- 
Steve Langasek
postmodern programmer


pgpLBbzW9AowG.pgp
Description: PGP signature

Re: updating a deb

[Peter S Galbraith]

Filippo Basso <[EMAIL PROTECTED]> wrote:

> Configuration file `/etc/logs/php/eth2'
>  ==> File on system created by you or by a script.
>  ==> File also in package provided by package maintainer.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : background this process to examine the situation
>  The default action is to keep your current version.
> *** eth2 (Y/I/N/O/D/Z) [default=N] ?
> 
> so, the package system is thinking that eth2 is a configuration file... so
> if I cancel it, or modify, it isn't updated!
> the problem was that any file in /etc directory is considered as conffile,
> I suppose, because changing it in /var all worked right.

Right.  All packaged files under /etc should be conffiles according to
Debian policy.

uscan help

[Shaun Jackman]

I can't get uscan to work with the following watch line. Could
someone please point out my mistake?

Please cc me in your reply.
Thanks,
Shaun

# Site  Directory   Pattern Version Script
http://www.geekshop.be /rien/lcab/?page=down lcab-(.*).tar.gz debian uupdate

Re: d-i milo missing (might have fix)

[Greg Folkert]

On Tue, 2003-09-30 at 13:11, Steve Langasek wrote:
> On Tue, Sep 30, 2003 at 12:49:29PM -0400, Greg Folkert wrote:
> > On Tue, 2003-09-30 at 12:18, Joey Hess wrote:
> > > The alpha port still has boot issues. In particular, we still lack the
> > > source to milo. This is unresolved. Despite this, CD images are in
> > > progress.
> > 
> > Which version of milo are you referring to?
> 
> > I still have 0.13 through 0.27 laying around. Will that help?
> 
> You tell us. :)  So far, no one has stepped forward to manage the MILO
> side of things.  Dealing with aboot is easy; it's packaged in Debian, so
> pulling it from the archive when building CD images is straightforward.
> MILO, OTOH, is not packaged at all, and (if my knowledge is current) has
> a rather grotesque build process due to its use of a stripped-down Linux
> kernel as the second-stage bootloader.  Getting it somewhere that it can
> be smoothly incorporated into the d-i builds is a challenge, one that's
> likely to only be overcome by someone with a vested interest in the
> MILO-dependent subarchs.

Quick question then...  how do I get on the mailing list that develops
the d-i? I don't see a specific one on lists.d.o. (I could be blind
though)

I have a DEC Alpha 1000/4 and a DEC Alpha 2100/4 (sable) that could be
stand a linux install on them. Currently I have no valid license of
OSF/1 or Tru64 for them, except a 1 user "root-only" license. The 2100
would be the nasty one to get it to work on. They both require milo, the
sable has never booted linux "proper" ever, as it's is the "early
version"

I am interested in helping out. But be warned, I come from a HARDWARE
background not a programming one.
-- 
greg, [EMAIL PROTECTED]
REMEMBER ED CURRY! http://www.iwethey.org/ed_curry

I should welcome flagellation by your ovoviviparous torso.


signature.asc
Description: This is a digitally signed message part

Re: Debian and the GNU Free documentation license

[Manoj Srivastava]

Hi,

I have updated the position summary page with responses from
 RMS to some of the concerns (thanks to Bob Hilliard for bringing them
 to my attention), added a nascent Overview section (which currently
 only has links deeper into the page), and general spell check and a
 few typographical corrections. I also removed a spurious font size
 specification in the style sheet, which may make for easier reading
 for some folks.

Again, the document lives at:
 http://people.debian.org/%7Esrivasta/Position_Statement.xhtml>
or, if your browser balks ath the xml+xhtml mime type, at:
 http://people.debian.org/%7Esrivasta/Position_Statement.html>

Does anyone have suggestions for a pithy position blurb to be
 appended to the overview?

manoj

-- 
Center meeting at 4pm in 2C-543.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: d-i milo missing (might have fix)

[Rene Engelhard]

Hi,

Greg Folkert wrote:
> Quick question then...  how do I get on the mailing list that develops
> the d-i? I don't see a specific one on lists.d.o. (I could be blind
> though)

debian-boot

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73
   `-   Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73
  


signature.asc
Description: Digital signature

Re: Linux Day

[Christian Surchi]

Il mar, 2003-09-30 alle 19:11, Emanuele Rocca ha scritto:
> Vedo che nessuno ha risposto, sarei parecchio interessato anche io.
> 
> In questi casi mi pare che la persona di riferimento sia fog, sbaglio?

solitamente si, e ricordo che ci sono i soldi debian a disposizione
degli eventi italiani sul conto corrente dell'Associazione Software
Libero... se non ricordo male sono intorno ai 250¤.

ciao
christian

RFP checkpassword-pam

[Alexey Mahotkin]

Hello,

I'd be grateful if somebody would upload my checkpassword-pam package to
Debian archive.

Project homepage is at http://checkpasswd-pam.sourceforge.net/.  I've just
released 0.98 version and it seems to be rather stable.

This package is of interest mostly to users running qmail, however there
are some other packages interoperating with it.

I am not a Debian developer, but I did some packaging (it passes lint, is
installable, and all that) already.  So you will have mostly to fix up if I
did something wrong, and do the upload.


Feel free to contact me if you need any advice.  I am not subscribed to
debian-devel, so please keep me in Cc: list.

Thank you,

--alexm

Re: uscan help

[Josip Rodin]

On Tue, Sep 30, 2003 at 10:17:10AM -0700, Shaun Jackman wrote:
> I can't get uscan to work with the following watch line. Could
> someone please point out my mistake?
> 
> http://www.geekshop.be /rien/lcab/?page=down lcab-(.*).tar.gz debian uupdate

IIRC, it doesn't support HTTP.

-- 
 2. That which causes joy or happiness.

Re: Building kernel modules for stock kernels is a hell of a job!

[Nicolas Boullis]

Hi,

On Tue, Sep 30, 2003 at 12:27:29AM +0200, Eduard Bloch wrote:

> > > kdist_clean:
> > > $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
> > 
> > Are those $(MFLAGS) really useful?
> > I thought they were not because $(MAKE) also had the flags, but I'm not 
> > sure anymore...
> 
> MFLAGS are the flags that make got on the commandline. The calls above
> copy the make call with options.

Well, I just checked the gnu make manual (section 5.6.3) and, if I 
understand it correctly, it says that using $(MFLAGS) is now useless 
thanks to the $(MAKEFLAGS) variable...


Is there something wrong with my inderstanding of this manual? Or is 
this a gnu-only feature, that we should not depend on?


Regards,

Nicolas

Re: uscan help

[Dagfinn Ilmari MannsÃker]

Josip Rodin <[EMAIL PROTECTED]> writes:

> On Tue, Sep 30, 2003 at 10:17:10AM -0700, Shaun Jackman wrote:
>> I can't get uscan to work with the following watch line. Could
>> someone please point out my mistake?
>> 
>> http://www.geekshop.be /rien/lcab/?page=down lcab-(.*).tar.gz debian uupdate
>
> IIRC, it doesn't support HTTP.

It does, but there is one space too much, and the file name must match the
complete href in the link. This would do:

http://www.geekshop.be/rien/lcab/?page=down \./files/lcab-(.*)\.tar\.gz debian 
uupdate

See the manual page, search for "alternative", for details.

-- 
ilmari

Re: updating a deb

[Martin Pitt]

Hi!

Am 2003-09-30 18:49 +0200 schrieb Filippo Basso:
> so, the package system is thinking that eth2 is a configuration file... 
> so if I cancel it, or modify, it isn't updated!
> the problem was that any file in /etc directory is considered as 
> conffile, I suppose, because changing it in /var all worked right.

I don't suppose that you entered it in the file 'conffiles' when
building the package. But if you use debhelper (dh_installdeb in
particular), then all files below etc/ are automatically entered in
the 'conffile' of the resulting deb.

Martin
-- 
Martin Pitt
home:  www.piware.de
eMail: [EMAIL PROTECTED]

Bug#213520: ITP: phpreports -- A report generation system written in PHP

[Matthew Palmer]

Package: wnpp
Version: N/A; reported 2003-10-01
Severity: wishlist

* Package name: phpreports
  Version : 0.1.5
  Upstream Author : Eustaquio Rangel de Oliveira J <[EMAIL PROTECTED]>
* URL : http://phpreports.sf.net/
* License : GPL
  Description : A report generation system written in PHP

PHPReports takes report definitions written in a custom XML DTD format and
turns them into a complete set of PHP code, which can be run to produce a
HTML formatted report in the format you specified.

Currently only HTML reports can be produced, in a fairly straightforward
table-oriented style, however work is underway to allow the generation of
PDF, plain text, and other formatting styles, for those that want them.

带给你一份惊喜！

[hi]

  
   送CDMA电话安心打便宜的国际电话

   
CDMA商务电话是联通公司针对商务电话市场，基于优质的CDMA网络技术推出的无线桌面电话。
使用联通商务电话比现行IP资费便宜30％以上！资费标准如下：

资费名称商务电话  普通电话
月租25元/月   35元/月
来电显示6元/月6元/月
拨打市话和手机  0.15元/分钟   0.11元/分钟，0.20元/分钟
国内长途0.3元/分钟（不收市话费）  0.3元/分钟＋0.11元/分钟本地
港澳台  1元/分钟  1.5元/分钟＋0.11元/分钟本地
美国加拿大  0.4元/分钟(促销期)2.4元/分钟＋0.11元/分钟本地
日本1.8元/分钟(促销期)3.6元/分钟＋0.11元/分钟本地
其它地区按IP资费  IP资费＋0.11元/分钟本地

 **最新优惠：美国、加拿大（0.40元/分不含本地通话费）
 新加坡、韩国（0.60元/分不含本地通话费）
 
日、俄、英、德、法、新西兰、澳大利亚、泰国（1.80元/分不含本地通话费）
   （即日到2003年12月31日）
使用方便：
   直拨长途，无需安装、布线，即插即用，走到哪，可用到哪！
   往电话机内装上电池，就可以将电话随意带到任何地方使用。
话音质量好：
   CDMA商务电话采用联通的优质网络技术，话音质量非常清晰。

中国联通商务电话指定代理商

   免费送机联系电话：27241858、83757164
 
   联系人（上门办理）：13316911528（王生）、13602698524（周生）

   客服热线：83757164、27241858

Buildd's using really old packages

[Chris Cheney]

I noticed while verifying that the buildds weren't still using the buggy
g++ 3.3.2-0pre4 that some are using 3.3.2-0pre1 which is 6 weeks old. Is
there a particular reason some of the buildds are so out of date?

Chris


signature.asc
Description: Digital signature