In my project leadership manifesto I promised to instute a more formal
decisionmaking procedure for the Project.
On debian-devel we have been discussing my drafts for the project's
constitution, which have evolved somewhat through that discussion.
This discussion has now reached the point where
The bug system has not been working properly for a few days now, and I
have just turned it off. No new mail will be processed and the web
pages will not be updated.
The problem is that (apparently) Linux 2.2 doesn't properly support
a.out binaries. The bug system uses a private copy of Smail3
Processing commands for [EMAIL PROTECTED]:
reassign 23340 general
Bug#23340: Quite a bad error from libstdc++2.8
Bug reassigned from package `libstdc++2.8' to `general'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(administrator, Debian bugs
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(administrator, Debian bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Enrique Zanardi writes (Re: Release management - technical):
On Tue, Jun 09, 1998 at 04:21:57PM +0100, Ian Jackson wrote:
...
I think we can only do one of these. With hamm we're doing the
latter; in the future I think we should do the former.
Fine, as long as we have some long term goals
Jules Bean writes (Re: Propersel for standerd configuration system. ):
--On Fri, Jun 12, 1998 7:53 am +0100 Philip Hands [EMAIL PROTECTED]
wrote:
The layout of the registry will be similar to Microsoft's windows
registry however it will be far more powerful.
...
So what do you think of
-floppies
Bug#23859: # of disks in floppy installation
Bug assigned to package `boot-floppies'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(administrator, Debian bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
I've been catching up on debian-devel (only 4900 messages to go), and
have come across a discussion about FHS.
I have two kinds of comment on this proposal: the first is appropriate
for debian-devel, and concerns our general goals, and is in this
message:
Firstly, I stick to my guns that we need
don't think would be addressed by the
API presented below let me know. If you don't understand the API
below then I'm afraid I can't help you atm - I haven't written the
documentation yet.
/*
* Copyright (C)1998 Ian Jackson.
* This version provided for review and comment only.
*
* $Id: adns.h,v
Mark W. Eichin writes (Re: Better (inc. asynchronous) DNS client (stub
resolver)):
You might look at the ares library (Asynchronous RESolver) that Greg
Hudson [EMAIL PROTECTED] wrote...
athena-dist.mit.edu:/pub/ATHENA/ares/ares-0.3.0.tar.gz
is the current version. (At very least,
David Welton writes (File renamer):
Hi, a friend of mine wrote a thing to rename a bunch of files, say
*.jpg to *.gif. Yes, he realizes you can do the same thing with a
shell script, but he wrote this thing just the same, because it's
convenient.
Does anyone know of anything similiar?
(I've now caught up on debian-devel, barring my 7 articles marked to
return, of which this was one ...)
Guy Maor writes on the 10th of September:
Yes, let's.
I am formally proposing version 0.8 of the constitution as given in
http://www.chiark.greenend.org.uk/~ian/debian-organisation.html.
Buddha Buck writes (Re: Ratifying the constitution ):
...
That's not what it means. It means that in order for an amendment to
automatically be accepted, you need to convince 6 people, Guy and the
five seconds.
If they don't like it, you can force it to a vote. I think you require
Darren Benham writes (Discussion - Proposed Constitution - voting part 2):
I've found another area that could cause problems in the vote counting area.
I've been running various sceanios and here's what I've found:
In point 5 of A.6. describes the STV method. Basicly, if no one
option has
Martin Schulze writes (Contacting authors):
tonight I was thinking about implementing @authors.debian.org which
would enable a way for us to get in touch with the upstream authors of
some piece of software without the need of looking into the copyright
file or digging in the source if the
I've had a brief look at this; would anyone like to take a closer look
?
Ian.
---BeginMessage---
--- start of forwarded message (RFC 934 encapsulation) ---
Received: from optima.cs.arizona.edu (optima.CS.Arizona.EDU [192.12.69.5])
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) with
I'm being sent to Stockholm by my employer and would be interested to
meet any other Debian or GNU people there.
I'm flying out tomorrow night and returning on Sunday. The conference
I'm attending is Wednesday to Friday, so I'll probably be available
Friday night and Saturday daytime and night.
Ryan Murray writes (master's mail backlog and upgrade time):
Also, I've investigated the mail backlog on master and found the main
problem. The mail queue is currently full of email that will never be
able to be delivered, all for one particular user. This mail is being
removed from the
to be treated this way for an unrelated reasons
without an announcement anywhere, surely that is even worse !
On Tue, Nov 15, 2005 at 12:18:45PM +, Ian Jackson wrote:
* The mail backlog that `will never be able to be delivered' was
(as far as I can tell) all spam that chiark has been properly
Steve Langasek writes (Re: master's mail backlog and upgrade time):
On Tue, Nov 15, 2005 at 12:18:45PM +, Ian Jackson wrote:
* It is unfortunate that (a) master has such a lax spam policy and
that (b) Debian developers cannot choose to make their @debian.org
address unuseable
Marco d'Itri writes (Re: master's mail backlog and upgrade time):
[I don't want a debian.org address either]. In the past the
debian-admins suggested that they would consider allowing to disable
them if somebody else implemented everything needed to do it.
Do we know what would be needed ?
Steve Langasek writes (Re: master's mail backlog and upgrade time):
On Tue, Nov 15, 2005 at 04:01:10PM +, Ian Jackson wrote:
But, there is another important point: I don't really want a
debian.org address. It's technically necessary for me to have one for
(eg) cronmail from debian
Steve Langasek writes (Re: master's mail backlog and upgrade time):
Anyway, the line in question is still in master's exim4 config; you may want
to try sending a mail to debian-admin, let them know what you've done on
your end, and ask if there's anything still preventing its removal...
Well,
Stephen Frost writes (Re: master's mail backlog and upgrade time):
Then bounce it locally. Duh. No reason to force master to deal with
the bounce messages you feel are 'right' to send.
I don't bounce it. I reject it at SMTP time with a 4xx or 5xx code.
Iaan.
--
To UNSUBSCRIBE, email to
Andy Smith writes (Re: master's mail backlog and upgrade time):
Instead of either side in this debate saying Not my problem, you
should do this... how about reaching some compromise? It sounds
like in the short term, Ian needs to discard some mail instead of
rejecting, and in the long term
Stephen Frost writes (Re: master's mail backlog and upgrade time):
* Andy Smith ([EMAIL PROTECTED]) wrote:
a) inflict bounce spam scatter on the forged from addresses in the
malware and spam he doesn't want to accept delivery for; or
...
It's his choice to do either (a) or (b) or (c). I
Six days ago I discovered that one of the Debian system administrators
had made a deliberate and highly unusual configuration change which
predictably broke mail from or via master to:
* me personally
* some of the =8 other Debian developers who have accounts on chiark
* the Technical Committee
Anthony Towns writes (Re: Automated testing - design and interfaces):
On Thu, Nov 17, 2005 at 06:43:32PM +, Ian Jackson wrote:
The source package provides a test metadata file debian/tests/
control. This is a file containing zero or more RFC822-style
stanzas, along these lines
James Troup writes (Re: master's mail backlog and upgrade time):
The change was made roughly less than 24 hours before your first post
to debian-devel. There wasn't actually all that much time to contact
you in.
You (plural) could have _just_ contacted me and I would have fixed it,
as I have
Stephen Frost writes (Re: master's mail backlog and upgrade time):
*I* don't bounce much of anything. Talk to Ian about wanting to
generate bounces, it wasn't my idea. What I want is for him to bounce
it himself if he feels it needs to be bounced, not make master do it.
What I want is for
Anthony Towns writes (Re: Automated testing - design and interfaces):
On Mon, Nov 21, 2005 at 06:22:37PM +, Ian Jackson wrote:
This is no good because we want the test environment to be able to
tell which tests failed, so the test cases have to be enumerated in
the test metadata file
Thiemo Seufer writes (Re: Bug#340428: octave2.9 - lists mailing list as
uploader in changelog):
Policy violations are RC by definition.
This is pernicious nonsense.
Asking whether a bug is release critical is the same as asking whether
it would be better to release with the bug, or to discard
Manoj Srivastava writes (Re: Canonical's business model):
What would I *like* to see? Well, that they treat me like I
treat my upstreams; I triage bug reports, I keep feature specific
patches separate, I submit these feature requests to upstream BTS,
or upstream author, depending
Thomas Bushnell BSG writes (Re: Need for launchpad):
Actually, upstream maintainers have no voice before the technical
committee, which exists to resolve disputes between Debian developers,
not between Debian developers and outsiders.
This is not true. Constitution s6 defines the powers of
(Note crosspost to debian-devel and ubuntu-devel. If your reply does
not concern both Debian and Ubuntu, please remove the inappropriate
list. And of course, in general, do not CC individual posters unless
they ask for it.)
Following discussions at Ubuntu's Montreal meeting, on debian-devel,
Gustavo Franco writes (Re: Automatic testing of .deb's):
On 2/2/06, Ian Jackson [EMAIL PROTECTED] wrote:
I would like to have some idea what people think I should do with the
tests that we're hopefully going to have, eventually for lots of
packages. Would Debian like those tests as patches
David N. Welton writes (Tcl in Debian - volunteers needed):
Apparently some of the packages I maintain were removed from Debian's
testing distribution this evening: rivet, tcldom, tclxml and tclsoap,
because of open bugs against them that I haven't found the time to
close. My bad, as they
Adrian von Bidder writes (Re: Automatic testing of .deb's):
On Monday 06 February 2006 19:53, Gustavo Franco wrote:
On 2/6/06, Ian Jackson [EMAIL PROTECTED] wrote:
[ filing automatic package tests to the Debian bts ]
The Ubuntu maintainer should always open bugs with the test related stuff
Martijn van Oosterhout writes (Re: timezone data packaged separately and in
volatile?):
The requirements for getting into a stable release update are not
black magic, they're quite well known:
http://people.debian.org/~joey/3.1r1/
2. The package fixes a critical bug which can lead into
Anthony DeRobertis writes (Re: conffile purging and maintainer scripts):
5. Decide you'd rather keep locally installed FOO, purge Debian FOO package.
DDTT
Solution to this one is that admins should follow the FHS and put their
config files in /etc/local/ :-D
No, the solution is not to purge
Thomas Hood writes (Re: conffile purging and maintainer scripts):
If a file /etc/foo was formerly a conffile of the package but no
longer is so then /etc/foo should be dealt with in the preinst or
postinst.
Regrettably this is currently true. I think this is a bug in dpkg and
I think I know
Branden Robinson writes (Ian Jackson, please get me the hell off your
blacklist.):
Mar 29 15:20:15 apocalypse sendmail[7886]: e2T8qEi03048: [EMAIL PROTECTED],
ctladdr=branden (1000/1000), delay=11:28:01, xdelay=00:00:21, mailer=esmtp,
pri=6332789, relay=chiark.greenend.org.uk
Branden Robinson writes (Re: Ian Jackson, please get me the hell off your
blacklist.):
Sending me mails -- with whatever content -- and discarding my replies
regardless of their content is nothing short of harassment.
[further polemic]
I reiterate, iwj and I are discussing this in private
Branden Robinson writes (Re: Ian Jackson, please get me the hell off your
blacklist.):
I see no reason not to reply [...]
I think you are being hypocritical. You complain when other people
post their opinions and discussions of this topic with you, yet you
post your own diatribes here. Since
I've just sent another, long, message about mail acceptance,
blacklisting, and this whole flamewar. Please read that message
first; it explains the context of this mail, and without it you might
misinterpret this one.
This message is about my opinion of the DUL, which I support and use.
In fact
Sam Hartman writes (Formal request for review: [Sam Hartman [EMAIL
PROTECTED]] Referring what kernel-images to build to the technical
committee?):
Hi. I posted the following message to debian-devel last night and
have received agreement with the summary and apparently (it was not
explicitly
I'm one of the small minority of people who have a very negative
opinion about gmail. I realise I'm a bit of a kook on this subject
and I'd ideally I'd like to avoid having an enormous flamewar about
it.
However, it has come to my attention that at least one developer
appears to be reading
Brian M. Carlson writes (Re: Mass bug filing: failure to use invoke-rc.d when
required):
But seriously, if violating Debian Policy has no consequences, then it
probably won't be followed. As it stands now, Policy is useless because
the worst that can happen is an important bug, which can be
Francesco P. Lovergine writes (Re: use of invoke-rc.d $PACKAGE stop || exit
$? in prerm scripts):
Unfortunately sometimes the daemon does not stop for an error in the
maintainer script and that prevents upgrading for ever, even when
the package has been corrected. [...]
If the old package's
Kevin B. McCarty writes (Re: sending debian-private postings to gmail):
Ian Jackson wrote:
[snip]
distributed to computers whose owners and operators cannot be expected
to refrain from processing the content in other ways
Wouter Verhelst writes (alternatives and priorities):
Fixing this wasn't very hard, but it made me consider why we let a
maintainer decide what the alternative priority of an editor would be.
I have a suggestion: how about we make it a rule that to provide a new
alternative with a greater
Michal Politowski [EMAIL PROTECTED]:
On Thu, 18 May 2006 22:38:08 +0200, Goswin von Brederlow wrote:
[...]
3. Make sh an alternative
dash already optionally diverts it. Isn't it good enough?
Both of these are a really bad idea. If anything goes wrong at the
wrong moment, /bin/sh would be
Florian Weimer writes (Re: use of invoke-rc.d $PACKAGE stop || exit $? in
prerm scripts):
Ian Jackson:
If the old package's prerm fails, dpkg tries the version from the new
package instead, precisely to avoid this problem. See the policy
manual for details.
And this doesn't help
Mike Bird writes (Re: Sun Java available from non-free):
Non-freeness is a red herring. The issue is that a small cabal -
- a small cabal operating outside its field of expertise - has
placed Debian in the position of indemnifying Sun.
This is obviously not possible.
Debian is not a legal
John Goerzen writes (Re: Sun Java available from non-free):
Also, I should add that agreeing to a license that commits SPI to
indemnify Sun
Who is purporting to commit SPI to indemnifying Sun ?
AFAICT ftpmasters are indemnifying Sun. This is silly of them but
probably not actually fatal.
John Goerzen writes (Re: Who can make binding legal agreements):
First, I don't believe that SPI has ever granted anyone the ability to
enter into legally-binding agreements to indemnify (which means to use
our resources to defend) third parties. I may be mistaken, though.
Could you please
John Goerzen writes (Re: Who can make binding legal agreements):
The first paragraph of the license linked to by the original
announcement:
SUN MICROSYSTEMS, INC. (SUN) IS WILLING TO LICENSE THE JAVA PLATFORM
STANDARD EDITION DEVELOPER KIT (JDK - THE SOFTWARE) TO YOU ONLY
Yes, but who is
Jeremy Hankins writes (Non-DD's in debian-legal):
I'm not sure I understand this part, though. Do you think that folks
like myself, who are not DD's, should not participate in the discussions
on d-l?
Actually, I think they should not participate, in general.
The arguments that are had on
Daniel Kobras writes (Re: Renaming a package):
but the alternative patch to dpkg is quite simple (see
below). Alas, it changes current behaviour.
I don't think it this patch is correct as is, but something similar
might not be unreasonable if it had to be turned on with a command
line option.
John Goerzen writes (Re: Who can make binding legal agreements):
* If a member project engages in activities that would jeopardize
SPI's classification as a non-profit entity
Things of that kind would be using SPI property or funds for
unsuitable activities. Note that if Debian do it
John Goerzen writes (Re: Who can make binding legal agreements):
The other plausible interpretation is that SPI *is* on the hook, as the
legal entity that owns servers that are distributing software.
If you use your shell account at your ISP to distribute software, and
the ISP concludes you
Manoj Srivastava writes (Re: severities of blocking bugs):
Well, consider this. If there is a feature someone wants from
a package, say kernel-pack^H^H^H^Hfoo.
[most of scenario snipped -iwj]
Can one now change the wishlist bug to grave as well? I think
not, since the
Daniel Kobras writes (Re: Renaming a package):
On Fri, Jun 09, 2006 at 02:15:06PM +0100, Ian Jackson wrote:
I don't think it this patch is correct as is, but something similar
might not be unreasonable if it had to be turned on with a command
line option.
[Context: When renaming
Thomas Bushnell BSG writes (Re: severities of blocking bugs):
Ian Jackson [EMAIL PROTECTED] writes:
As opposed to writing to demand that the maintainer spend their free
time to help you fix your problem !
How does adjusting the severity of a bug report amount to a demand
LEE, Yui-wah (Clement) writes (A question on setting setuid bit):
I am building a package in which one of the binary has
to have the setuid and setgid bits set. I wonder which
one of the following two is the more appropriate method
to use?
Forgive my scepticism, but which package, and why ?
LEE, Yui-wah (Clement) writes (Re: A question on setting setuid bit):
This is an experimental package that we built and
evaluate internally (up to this moment). The program
that needs setuid is a cgi-bin program that is invoked
by apache2, which runs as a regular user www-data. The
cgi-bin
Erast Benson writes (Re: cdrtools):
Joerg clearly stands that:
1) Makefiles != scripts or at least it is unclear whether Makefiles may
be called scripts:
GPL §3 requires the scripts for compilation to be provided but
as a first note, it is unclear whether Makefiles may be called
Bill Allombert writes (Getting rid of circular dependencies, stage 5):
Here the list of packages involved in circular dependencies listed by
maintainers.
Didn't we already have the conversation where we explained that there
is nothing necessarily wrong with a circular dependency ?
Ian.
--
Manoj Srivastava writes (Re: Getting rid of circular dependencies, stage 5):
I see you have not fully followed through on reading policy
here: [quote]
Quite.
Clearly, dpkg authors have read all of policy, including the
caveats about circular dependencies.
This is
Loïc Minier writes (Re: Getting rid of circular dependencies, stage 5):
I fail to see how the circular depends between tasksel and tasksel-data
would cause any bug though. I agree it's best to fix circular deps in
general, but it's not necessarily required each time.
You persist in using
Henning Glawe writes (Re: Getting rid of circular dependencies, stage 5):
Well, the problem with circular deps is not caused by dpkg but by the way
apt calls it:
Ahh. Well, perhaps apt should be fixed, as you say.
Personally I (still!) don't use it on my own systems.
Ian.
--
To
Osamu Aoki writes (Re: Getting rid of circular dependencies, stage 5):
Just curious ...
dselect with dpkg-ftp ?
Yes. It does need some handholding and the need to dpkg -iGROEB its
download area repeatedly is annoying but it's very reliable in the
sense that (if you are happy to drive dselect)
Josselin Mouette writes (Re: Getting rid of circular dependencies, stage 5):
Le lundi 24 juillet 2006 à 17:15 +0100, Ian Jackson a écrit :
Of course particular instances of circular dependencies might be
problematic. I would try to avoid it other than in closely coupled
sets of packages
Goswin von Brederlow writes (Re: Getting rid of circular dependencies, stage
5):
So you seem to be all for cleaning out that mad stuff, right?
Absolutely.
Lets all get on with the list initialiy posted and fix those circular
depends or note why they are required.
I agree that there are many
Tatsuya Kinoshita writes (Re: virtual packages `pinentry' and `pinentry-x11'):
Hmm, I have not yet understand the policy 3.6:
| All packages should use virtual package names where appropriate, and
| arrange to create new ones if necessary. They should not use virtual
|
Matthew Palmer writes (Re: Centralized darcs):
diff.gz archaeology should not be necessary.
I think this is the root of the key difference between the `like patch
systems' people and the `hate patch systems' people.
`Hate patch systems' people are those who can read code, and prefer
Josselin Mouette writes (Re: Centralized darcs):
Maybe you shouldn't assume all people who like to code and debug aren't
clueful enough to run diff. Putting my changes in a patch is the most
useful way to integrate them in a Debian package *and* to forward them
upstream. It is far less complex
Russ Allbery writes (Re: Centralized darcs):
In my experience, the key difference between whether or not I want to use
a patch system like quilt is whether I have an upstream to which I need to
feed self-contained patches that may go unapplied for extended periods of
time. When I'm in that
Anthony Towns writes (glibc and UNACCEPTs):
... how we can avoid this class of problem in future, given the safety
net that caught us this time is going away?
Ideally, there would be some automatic checks that could spot
`probably erroneous' uploads, and which you would mention in your
.changes
Bruce Sass writes (Re: Silly Packaging Problem):
files and size accommodate the desire to include generated or
packageless files and their size (if knowable) in the dpkg DB.
This is a bad idea. dpkg maintains these lists of files not primarily
for the purpose of dpkg -S, but rather for making
Michael Biebl writes (dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now
supports ~ in version numbers]):
Reading this announcement I thought, great and wanted to start using
'~', only to discover that dpkg believes that 0.09+0.1.svn 0.1~svn.
1.) Wait for a 0.10 release. I think my users
I reported that adduser creates a .bash_profile file in the invoking
user's current directory. On examining the code, it seems that if
/etc/skel contains a .login or a .profile it will write those too.
Below is a patch that I believe will fix the problem. It also adds a
new feature: after
Ian Murdock writes (Re: FTP arrangement):
Date: Tue, 26 Sep 95 12:03 BST
From: Ian Jackson [EMAIL PROTECTED]
I'm confused. I thought we had an incrementally upgradeable system ?
What is the purpose of the extra directory ?
[ bleeding edge vs. stable ]
Ah, it becomes much
Dick Arnold writes (Re: problems with elv-vi package install):
[...]
I had problems installing elv-vi also and found out when using update
alternatives you also need debian/binary/devel/perl-5.003.deb.
I think update alternatives needs /usr/lib/perl5/POSIX.pm which is in the
above mentioned
Erick Branderhorst writes (Bug#1503: How to remove fvwmr5):
Package: fvwmR5
Version: 1.24r-
Libc: libc.so.4.6.27
Kernel etc: Linux eb 1.2.10 #1 Tue Jun 13 18:37:28 EST 1995 i486
Reporter: repair 0.1
Subject: How to deinstall fvwmR5
I tried the following commands but no luck.
# dpkg
Ian Murdock writes (Re: virtual packages and X11 vs. X11Rspecific_number):
Well, the X11R5 and X11R6 libraries weren't compatible, and it is
likely the X11R6 and X11R7 libraries won't be, either. In this
case, the packages will have to be updated. We don't want people
thinking they can use
Ian Murdock writes (Re: Very weird stuff on ftp.debian.org):
I noticed this today, too, but I forgot about it until now.
Basically, after logging in and noticing Permission denied, I did
a cd /, and then a cd, and everything appeared to work normally
after that.
It shouldn't be happening,
David Brinks writes (Re: Very weird stuff on ftp.debian.org):
Give your cron a shot again, Ian. [...]
It succeeded some time earlier today, but I've only just got around to
answering my mail. Thanks for getting it fixed.
The new trn, dpkg and texinfo packages are now available in
Karl Ferguson writes (Bug#1508: Segmentation fault while installing...):
[...]
[EMAIL PROTECTED]:2:/pub/linux/debian/debian-0.93/binary/base] dpkg -i
adduser-
1.94-1.deb
(Reading database ... 6380 files and directories currently installed.)
Preparing to replace adduser (using
There are a number of things I want to do to dpkg, but I think they
all count as extra features, rather than bugfixes. I therefore
propose to call dpkg non-beta very shortly, and issue version 1.0.0.
NB that dpkg version numbers will then no longer have any apparent
resemblance to Debian release
Erick Branderhorst writes (Sizes and Packages in dselect):
* diskspace requirements (displayed/registered)
[...]
This is on the wishlist, and I think I know how to support it.
This will become more difficult when the different directory's where
parts of the packages are going to are mounted
Dirk Eddelbuettel writes (Bug#1497: acct-alpha-5-7 problems):
Marek - trying to start accounting again when it is already running gives
Marek a message Process accounting not available on this system, which
Marek is a bit confusing (I suggest not to redirect stderr from accton to
Marek
Bill Mitchell writes (0.93r6 sysadmin user account prompt (and smail config)):
0.93r5 prompted for a non-root admin account name. 0.93r6 has
dropped this. I just thought I'd comment on this. smail is
one of the default packages and, though it allows postmaster
mail to be set up to go to
David Engel writes (ld.so (fwd)):
Forwarded message:
I'm having a few problems with your 'ldso' package when using 'dftp'.
The problem arises because the internal package name is ldso yet
the filename is ld.so. Would you mind changing these to be consistant
in a future release?
This
Emilio C. Lopes writes (Re: dselect install times out screensaver):
I have just read that the max n is 60 (1 hour). The info comes
from the Linux Console Terminal Documentation, posted saturday
to c.o.l.a.
What we need is a sequence that means `reset the timeout now'. I
could have dpkg
Erick Branderhorst writes (Bug#1526: man dpkg(5) dpkg(8) dselect):
Package: dpkg
Version: 1.0
At the bottom of the man page of deb a see also line is included.
This line refers to dpkg and dselect. The manual pages of these
are missing. Perhaps this is not a bug but anyway.
Erick
Yes,
Bill Mitchell writes (Re: dselect install times out screensaver):
On Tue, 3 Oct 1995, Ian Jackson wrote:
What we need is a sequence that means `reset the timeout now'. I
could have dpkg output that every time it start processing a new
package, if TERM=linux. (I'd rather not hardwire
Bruce Perens writes (Re: Dselect / dpkg interaction. ):
In the case of the startup script running dselect, there is no interactive
shell to take over when dselect gets a stop signal. Thus, you'd simply
have to fork a shell at a lower level.
That's right. When the DPKG_NO_TSTP variable is set
Kenny Wickstrom writes (symbolic links within /bin):
I was just looking around in /bin and noticed some symbolic links that
may be incorrect. My system is 0.93R5+++ (I update the base regularly).
The links I wonder about are
csh - ../usr/bin/tcsh
rmail - /usr/sbin/rmail
Raul Miller writes (Re: ld.so (fwd)):
Ian Jackson:
: IMO the real solution is to have a real FTP method for dselect that
: only gets the first few bytes of each package to check what it is.
: This is doable, but someone has to go and write it.
Sure, but this doesn't exist yet. Is it likely
1 - 100 of 2647 matches
Mail list logo
