Chris Lawrence wrote:
> On Jul 20, Joey Hess wrote:
> > So would anyone murder me if the code in debhelper to make postinst
> > scripts manage /usr/doc links just went missing? This would of course
> > cause the link to go away when packages were upgraded to versions built
> > with the new debhelpe
Wichert Akkerman wrote:
> Previously Ian Jackson wrote:
> > I'd appreciate it if people wouldn't send messages which are copied to
> > *both* the policy list and the technical committee.
>
> Actually the ctte list has seen 1 post this month, all the others
> never make it there since the list is m
Julian Gilbey wrote:
> Here's an issue. About two years ago there was a proposal that the
> default httpd setup should not allow /usr/doc to be remotely
> accessible, as it's a huge security risk. (Yes, we're talking about a
> small amount of "security through obscurity" here, but we don't need
>
Josip Rodin wrote:
> On Mon, May 22, 2000 at 08:42:42AM +0200, Martin Schulze wrote:
> > > I can (and will, if allowed) do as many NMUs as necessary to get this
> > > done.
> > > Since it should be done in potato, too, I'm sending this to Richard to ask
> &
Josip Rodin wrote:
> I can (and will, if allowed) do as many NMUs as necessary to get this done.
> Since it should be done in potato, too, I'm sending this to Richard to ask
> can I/we upload changed packages in frozen. We have one full week to do it,
> which should be enough (these packages aren't
Ohhh :)
Branden Robinson wrote:
> + should delcare in their control data that they provide the
May I ask for the use of proper english as well? "declare" looks better. :)
Regards,
Joey
--
Linux - the choice of a GNU generation.
Please always Cc
I'm soo sorry *evil grin*[1]
Branden Robinson wrote:
> Package: debian-policy
> Version: 3.1.1.1
> Severity: wishlist
>
> Documents current practice.
>
> --
> G. Branden Robinson| A committee is a life form with six or
> Debian GNU/Linux | more legs and
Hi,
I'm currently discussing an issue with the maintainer and author of
rbootd. This is a server that provides boot-loaders or kernels for a
couple of HP9000 boxes.
The old package defaulted to /usr/local/lib/rbootd as location for
those boot-loaders and kernels. No boot-loader or kernel is pro
Hi,
I'm currently discussing this with Joey and Manoj but cannot enforce
it myself due to time constraints.
For a maintainer it is very difficult to follow policy if there is
no proper way to find out what needs to be done for a package that
was compliant to policy version 2.5.0.0 and should now
Julian Gilbey wrote:
> Now that we have a "fixed" priority in the developers-reference (this
> is not in policy itself), can this proposal be closed?
Your quote is not sufficient for me to decide.
Regards,
Joey
--
Unix is user friendly ... It's just picky about its friends.
Please al
John Lapeyre wrote:
> *Martin Schulze wrote:
> > I'm trying to revive Debian QA. With the growing number of new
> > maintainers showing interst in general QA for Debian it seems useful
> > that one of the 'old' maintainers shows direction.
> Longer descript
I'm trying to revive Debian QA. With the growing number of new
maintainers showing interst in general QA for Debian it seems useful
that one of the 'old' maintainers shows direction.
However if it works and we have a working QA team we need to discuss
ways the QA team is allowed to upload package
Santiago Vila wrote:
> > > If the dependency rule is to be considered "distribution-wise", ncurses3.4
> > > may not be made optional in a certain release until all the packages of
> > > standard or higher priorities have been recompiled in the same release.
> >
> > Which means that when uploading
Santiago Vila wrote:
> On Sun, 21 Feb 1999, Martin Schulze wrote:
>
> > Santiago Vila wrote:
> > > Regarding slink, it is not released yet. Is there a reason why we should
> > > not try to have correct priorities for slink? (You seem to imply that
> > > pri
I was asked to look at this thread.
John Goerzen wrote:
JG> * Despite having Important, Critical, or Grave bugs filed against their
JG> packages in frozen, some developers still ignore them. They could
JG> at least say "I can't fix this; can somebody else help?"
Unfortunately there are too m
I was asked to look at a thread here but haven't reached it, instead
I'm entering the second huge thread that seems to need my comments.
First of all, there are only three reasons for removing packages:
a) F*cked up license that forbids distribution
b) The package causes damages on systems
c
Brederlow wrote:
> > [No, Jason, apt doesn't count, since not everyone uses it.]
>
> Why don't we kick out dpkg and use apt only?
Umm, maybe because apt is a frontend to dpkg?
> Both should be merged into one WORKING binary or at least the dpkg
> should be used only internally and not by the use
Santiago Vila wrote:
>
> If the dependency rule is to be considered "distribution-wise", ncurses3.4
> may not be made optional in a certain release until all the packages of
> standard or higher priorities have been recompiled in the same release.
Which means that when uploading ncurses 3.4 the m
Santiago Vila wrote:
> > > Previously Santiago Vila wrote:
> > > > Is this to be considered "distribution-wise"?
> > > > i.e. Is this to be applied to hamm, slink, potato, in an independent
> > > > way?
> > >
> > > I think so, because packages that may be required in release N could
> > > be obso
Brian White wrote:
> > If you file this as bug agains Apache you need to file it against all other
> > httpd's that support cgi-bin as well. Thus I assume that you need to modify
> > policy first.
>
> I figured I'd start with the big one and then work my way around. However,
> somebody has reass
Brian White wrote:
> Package: apache
> Version: 1.3.3-4
> Most people setting up a web site expect /cgi-bin/ to be available for
> scripts on their site. Unfortunately, Debian uses this for those scripts
> packages that get installed. These two need to be independant.
I don't seem to understand
[EMAIL PROTECTED] wrote:
> > a) Use [EMAIL PROTECTED] or [EMAIL PROTECTED] in the maintainer field
> > of package foo.
>
> That still leaves in the dependency on the physical maintainer. It also
> makes the information in the Packages file authoritative for the
> maintainer information. Thi
Shaleh wrote:
> Nifty idea. Kinda like it. My only beef is that the "user" must know to mail
> [EMAIL PROTECTED] rather than [EMAIL PROTECTED] or
> [EMAIL PROTECTED]
There is a cute mechanism that [EMAIL PROTECTED] and [EMAIL PROTECTED] both
work, so for regular libraries this issue is resolved.
Howdy Joost,
some issues of your proposel are already working. Every package can have
a mailing list referenced through [EMAIL PROTECTED] This is already
working for over a year.
Requirements:
a) Use [EMAIL PROTECTED] or [EMAIL PROTECTED] in the maintainer field
of package foo.
b) Creat
Wichert Akkerman wrote:
> > Instead, "Compiler maintenance group" <[EMAIL PROTECTED]> and
> > "Debian boot floppies team" <[EMAIL PROTECTED]> should be
> > used.
>
> You have a chicken & egg problem here: @packages.debian.org just passes
> the mail on to the address listed in the Maintainer field
J.H.M. Dassen (Ray) wrote:
> On Thu, Dec 10, 1998 at 15:40:23 +0100, Martin Schulze wrote:
> > > I agree that this would be a more pleasing solution. Currently the
> > > packages.debian.org address database is based on the maintainer
> > > addresses from the Packages
J.H.M. Dassen Ray" wrote:
> On Thu, Dec 10, 1998 at 13:47:53 +0100, [EMAIL PROTECTED] wrote:
> > I don't very much like either of "Compiler maintenance group
> > <[EMAIL PROTECTED]>" and "Enrique Zanardi " because
> > it does not structurally solve the problem it addresses.
> >
> > Instead, "Comp
Miquel van Smoorenburg wrote:
> sh script.sh is very different from running it in a subshell with ().
> For example, bash doesn't really fork a new invocation - it just
> sets up a new internal environment temporarily. It's a speed optimization.
I didn't learn this. However it's funny that even s
Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> Martin Schulze <[EMAIL PROTECTED]> wrote:
> >So regular *.sh scripts must not contain any "exit" statement.
> >(which is the case e.g. for keymap.sh)
>
> Ah, now I remember. Th
Miquel van Smoorenburg wrote:
> > >b) All scripts in /etc/init.d, /etc/rc.boot and similar directories
> > > have to be standalone shell scripts. They must have the 'x' flag
> > > turned on and contain a regular command to execute them in the
> > > first line (such as "#! /bin/sh"). The
In /etc/* there are severeal scripts that are named *.sh. Most of
them are not marked executable and don't contain a "#! /bin/sh" line.
Thus, to run them you need to "sh foo.sh" or "source foo.sh" them.
This raises a problem if the script contains code like "test -x foo ||
exit 0". This would ca
Manoj Srivastava wrote:
>
> PROPOSAL: Policy manual contradicts itself about including docs
> ---
> Manoj Srivastava <[EMAIL PROTECTED]>
> $Revision: 1.2 $
>
>
> Copyright Notic
Darren Benham wrote:
> I have just heard that, as strange as it sounds, it's not part of policy to
> reject a package from incoming that violates policy. THEREFORE, I propose
> that
> it be made part of policy to reject from incoming packages that contain policy
> errors and that the standard of
Hi,
Due to bash bug #23857, the installation of several daemon packages
will fail if `set -a' or `set -o allexport' has been used in the root
shell that executes dpkg.
Francesco Potorti` proposed to to make the pre- and post- installation
scripts set "+e" before executing a subscript.
Can this p
Davide G. M. Salvetti wrote:
> Currently some package stop at installation time asking the user to
> press RET to be sure he reads very important stuff.
>
> What about mailing that stuff to root, as well as displaying on the
> console _without_ stopping, instead? I assume people not installing a
Joseph Carter wrote:
> On Tue, Sep 29, 1998 at 12:16:52PM +1000, Herbert Xu wrote:
> > After purging emacs today, the damn thing deleted my /usr/local symlink
> > since
> > it was the last package to have /usr/local in it. Obviously this is not
> > very
> > clever.
> >
> > So we should either r
Dale Scheetz wrote:
> On Tue, 22 Sep 1998, Brian White wrote:
>
> > > This is a formal request for removal from the NAG distribution list.
> > >
> > > Receiving 100 useless messages, each indicating an outstanding bug, is the
> > > worst kind of spam. It imparts no information, either about the b
John Lapeyre wrote:
> On Thu, 17 Sep 1998, Ward Deng wrote:
>
> wdeng>We really intend take over some numerical/scientific
> wdeng>applications. However, none of us here are official Debian
> wdeng>developers. We are asking question if a company can be a
> wdeng>developer and nobody seems to know
Hi,
I'd like to append two (hopefully short) comments to this.
a) The right place to fix this bug/implement it is Guy's dinstall
program that installs the packages into the archive. If
one feels that this should happen soon he should contribute
to it. I think Guy would accept appro
I believe this is the last mail that wasn't delivered due to failure.
Regards,
Joey
- Forwarded message from Manoj Srivastava <[EMAIL PROTECTED]> -
Hi,
>>"Marcus" == Marcus Brinkmann <[EMAIL PROTECTED]> writes:
Marcus> Great option. Imagine the free software would follow the s
Santiago Vila wrote:
> Hi.
>
> [ I've Bcc:ed debian-devel. Please answer only to debian-policy. Thanks ].
>
> The "new upload procedure", approved some time ago, is already in the bug
> list for ftp.debian.org (#17525), so I hope it will be implemented some
> day and this procedure will allow us
I also like this proposal but I don't volunteer, some jobs should
not be connected to me ;-)
However I'd like to add:
a) A weekly status has to be posted to debian-policy.
b) A set of web pages covering recent topics has to be set
up and maintained. This could be master/~srivasta/ since
Hi,
This is Richard Stallmans oppinion about free documentation.
It might be useful in our discussion of a free license for
documentation.
Regards,
Joey
--
There are lies, statistics and benchmarks.
--- Begin Message ---
[Please repost this wherever it is appropriate.]
A couple of wee
Martin Mitchell wrote:
> > I think you can remove this one. I actually do have scripts to do the
> > common archive operations, which I only wrote fairly recently. I
> > don't think it's a good idea to allow developers to activate them
> > directly.
>
> Please provide a rationale. Do you think m
Keita Maehara writes:
> From: Yann Dirson <[EMAIL PROTECTED]>
> Subject: Chosing release goals for slink
> Date: Fri, 10 Jul 1998 12:36:53 +0200 (CEST)
>
> > * No binary-section manpages (mainly 1, 6, 8) in `manpages' and
> > `manpages-' packages, but in their relevant binary packages.
>
> Is thi
[EMAIL PROTECTED] wrote:
> > > > I'd suggest that all logfiles will be removed when the package
> > > > is purged, but is that written down somewhere and do packages
> > > > make use of it?
> > >
> > > Don't you dare... I think that should be up to the administrator...
> >
> > When a package is
Turbo Fredriksson wrote:
> > I'd suggest that all logfiles will be removed when the package
> > is purged, but is that written down somewhere and do packages
> > make use of it?
>
> Don't you dare... I think that should be up to the administrator...
When a package is removed it has to remove its
Hi,
this just came up to my mind, I'm not sure that even I have dealt
with it so I think bringing it up publically is a good thing.
What is our packaging policy about logfiles?
Logfiles are rotated on a daily, weekly or monthly basis through
the /etc/cron./ files.
But what happens with the logf
Enrique Zanardi wrote:
> On Sat, Jul 11, 1998 at 03:50:25AM +1000, Martin Mitchell wrote:
> > * Developer controlled automatic archive maintenance (eg removal of packages
> > automatically after GPG signed email with list of packages to delete)
>
> That is a very interesting goal. Have you asked
Zed Pobre wrote:
> >Please try to convince the x?splay maintainer to split the package
> >and/or (no or, only and) the x?splay author to use a free widget set.
>
> What widget set is usually recommended as a replacement?
Any free one. Gtk comes to my mind.
Regards,
Joey
--
The
Brian Almeida wrote:
> Ok, looks like eMusic *can* go into main...as it uses splay (which is in
> contrib)
Nope. It has to go into contrib then.
> Except from README.Debian out of the splay package...
> "Currently the dependency upon qt1 for the xsplay interface forces this
> package into cont
egards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ VFS: no free i-nodes, contact Linus -- finlandia, Feb '94 /
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
.debian.org
The security team publishes updates there.
Regards,
Joey, who is happy that Debian GNU/Linux 1.3.1r7 materialized
yesteday.
--
/ Martin Schulze http://home.pages.de/~joey/
/ Linux - the choice of a GNU generation [EMAIL PROTECTED] /
pgp7wpwpgsCaj.pgp
Description: PGP signature
e postrm script interactive:
Afaik msql's postinst has similar statements. This is minimal prompting
IMHO. We must not remove such data without request.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ The good thing
> > [1] That is James Troup, Igor Grobman, Klee Dienes and myself
>
> I could not find a [1] in the text.
Oups, then it got removed.
Regards,
Joey
--
/ Martin Schulze http://home.pages.de/~joey/
/ Linux - the choice of a GNU generation [EM
hope to support gnupg later.
[1] That is James Troup, Igor Grobman, Klee Dienes and myself
[2] http://www.debian.org/doc/packaging-manuals/developers-reference/ch1.html
[3] That is James Troup and Igor Grobman
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Old
x distribution.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ Never trust an operating system you don't have source for! /
pgpPQwTT8kT9H.pgp
Description: PGP signature
I do understand that there are people not speaking english. It should
be ok if they provide their information in their native language as
long as somebody translats it when packaging the software up so others
are able to read its docu.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTE
On Sun, Apr 19, 1998 at 12:46:44PM -0700, Guy Maor wrote:
> Martin Schulze <[EMAIL PROTECTED]> writes:
>
> > We will update the debian keyring with public servers on a
> > regular basis and exchange keys - in both directions.
>
> I assume that public se
On Sun, Apr 19, 1998 at 01:26:47PM -0700, Ben Gertzfield wrote:
> >>>>> "Martin" == Martin Schulze <[EMAIL PROTECTED]> writes:
>
> Martin> . Your public PGP key that is at least 1024 bits big.
> Martin> Shorter keys won't be accep
On Sun, Apr 19, 1998 at 02:27:40AM +0200, Richard Braakman wrote:
> Martin Schulze wrote:
> > . say what you've done,
>
> What does this part mean?
"I'm a student of medical technologies for 3 years now and have
used Linux from the very beginning like 0.99pl13
/ch1.html
[3] That is James Troup and Igor Grobman
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ If you come from outside of Finland, you live in wrong country /
/ Featuring Debian GNU/Linux motd von irc.funet.fi /
pgpWlLbaprKWd.pgp
Description: PGP signature
Chinese I want to be able to understnd
the changes. They may give good ideas for ones own packages - if
one is able to understand them...
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ If you come from outside of Finland, you live in wrong coun
at the language in the package description
and changelog has to be english?
Thanks,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ If you come from outside of Finland, you live in wrong country /
/ Featuring Debian GNU/Linux motd von irc.funet.fi /
pgprSnfsmkwhz.pgp
Description: PGP signature
/fakeroot/libfakeroot 0 libc6
If it's only with the fakeroot package, it's a special case where the
shared library is *not* included in a path provided by /etc/ld.so.conf.
I believe this is intentional (at least for fakeroot it is). Therefore
I bel
this
> directory?
Why not?
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ Never trust an operating system you don't have source for! /
pgpqrSlj8KIQ8.pgp
Description: PGP signature
nds: blah" on the control file for the source part?)
Unfortunately we still don't have Source-Depends. Joey has pointed
out one serious thing today - we have non-i386 maintainer - which
reminds me to the neeed of source depends in order to let auto-compilers
run.
Regards,
J
a different story. If I get such Makefiles I'm trying
to optimize them where I can and submit it to the author. I think this
is appropriate.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~j
on makefiles, too. They're issued and so
on, no problem normally.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ VFS: no free i-nodes, contact Linus -- finlandia, Feb '9
recall a hook in our
packaging documentation I won't bother you with it any longer. I've
instead improved my wrapper.
Sorry for the disturbance,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home
needs to have such a .PHONY entry. At least it
sounds ok.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ VFS: no free i-nodes, contact Linus -- finlandia, Feb '94 /
name is intentional.
>
> What does stamp-build do?
It shows that make -f debian/rules build has run successfully.
The binary target may be issued.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de
e tools are
quite nice, but for me they often do a lot of stuff I don't want
them to do. I might be a bit convervative.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ http://home.pages.de/~joey/
/ Unable to locate
e
to use. As there are normaly no depends on the build target
make will refuse to run the build stage.
I'd like to make it policy that the stamp-file is NOT called
'build' but something else, I still use stamp-build like in
the early days - the name is intentional.
Comments
g reports. If this becomes policy, it
> would be best if debhelper & co. did the stripping for you and lintian did
> bug reporting after that.
s/debhelper & co/install -s/g ?
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ Whe
ted twice at boot time.
>
> Should they test for the existance of something that is unique for the
> package? I doubt /usr/doc/ would be appropriate. Wat would be good?
Oups, they should test for something unique and the programs it
calls.
Regards,
Joey
--
/ Martin Schulze
L PROTECTED] seems to make sense. Perhaps
> even a virtual domain dedicated to this like
> [EMAIL PROTECTED]
Just see above and try it out. You'll see that it already works
the way you want to - even better.
Regards,
Joey
--
/ Martin Schulze
ages.debian.org address?
What do you mean exactly? This is "only" a mapping of the .dsc files.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ linux: Unbekannter Terminaltyp/
/ Ich weiß nicht, auf was
ecause I create that
file on master and va during account creation.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ linux: Unbekannter Terminaltyp/
/ Ich weiß nicht, auf was für einem Terminaltyp Sie arbeiten - /
/ alle
e asked Peter again and he
answerd that I should give him the entry. While adding it he noticed
that it's already in. So new installations should already have this
entry and the file won't be modified anymore. So this is no problem.
For compatibility with older versions of D
t use scoring in Gnus?
>
> We not just create different lists for different architectures?
>
> [ I'm an i386 user. Do you really think I should *receive* all
> those alpha, m68k, sparc, etc. announcements? ]
Are you completely uninterested how the ports are going on?
Regards,
for this:
>
> [EMAIL PROTECTED]
This is the mechanism that I use at packages.debian.org. It looks
for a file ~$(maintainer)/.qmail-$(package).
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ No question is too
developers have agreed that
it makes sense to maintain packages as a group. Boot-floppies is another
package that seems to be maintaines by a group.
Therefore I'm requesting a policy change. Leave out the first paragraph
and add a sentence about a group of maintainer in the succsessor
rs
Regards
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ Whenever you meet yourself you're in a time loop /
/ http://home.pages.de/~joey/ or in front of a mirror /
oming isn't world readable anymore only
developers can see the packages. Only few people know aj's ftp address.
Regards
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ The MS-DOS filesystem is nice for removable media /
/ -- H. Peter Anvin /
d to close bugs.
Let's take a look at the .changes files. Normally all information
is covered there. Normally closed bugs are mentioned in the
Changes: section. So Guys script should look for #(\d+) and
close $1 after proceeding (speaking in Perl).
Regards
Joey
--
/ Martin Schulz
daemons, too. This has to be controlled by the admin, imho.
Regards
Joey
--
/ Martin Schulze * Debian Linux Maintainer * [EMAIL PROTECTED] /
/ http://www.debian.org/ http://www.infodrom.north.de/~joey/
/ Never trust an operating system you don't have sources for! /
loading.
Regards
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ [EMAIL PROTECTED] /
/verursacht durch kaputte Gatesoftware auf der CyberBox /
88 matches
Mail list logo
