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
ich chiark is the MX.
If a domain was set up 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'
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 th
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 m
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...
We
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 t
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
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 (
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
&
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 h
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 fo
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 e
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 discar
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, depend
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 o
(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,
an
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
>
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 t
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 mainta
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 int
Do dpkg-ftp or dpkg-mountable modify /var/lib/dpkg/available
directly ?
If so then that is why this problem (older dpkg versions not
understanding epochs) has such serious consequences. If you tried to
dpkg --merge-available or dpkg --update-available with a Packages file
that the currently-insta
> 1. The software may be redistributed by anyone. The license for the
>software must allow modifications and derived works, and must allow
>them to be distributed under the same terms as the license of the
>original software. If the license restricts a source file from being
>distri
ge `netscape'.
> reassign 10614 netscape
Bug#10614: Screen does not refresh/reload crashes Netscape
Bug assigned to package `netscape'.
> --
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(maintainer, Debian bug tracking system)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I am going to reconfigure the bug tracking system so that any bounces
of the messages it sends out will be discarded. The level of
misconfiguration and general braindamage has become so large that this
has become necessary; in the past, I would investigate and chase up
people/sites sending broken
I suppose I really ought to bring this up again, so we can finish the
issue. *sigh*.
Raul continues to suggest using a CGI program:
> The cgi script wouldn't have to run on the same system. It's
> a pretty simple script (see below), just change input mechanism
> from <> to something based on use
oming mail about once
a week, and smaller messages (1Kb up to tens of Kb) once
every half hour.
* Intending not to drop out immediately.
Sue Campbell:
> Ian Jackson wrote:
> > Several people have said that they've had problems mirroring the bug
> > system because it'
Bdale asks:
> In bug report 15091, Christian Meder suggests to me that I make gzip
> predepend on libc6. It is not clear to me that this is a good thing
> to do.
Christian Meder is right. Packages that are Essential (ie, ones
without which the packaging system breaks) should use Pre-Depends for
> Date: Thu, 4 Dec 1997 18:55:14 -0700
> From: Richard Stallman <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: question about prep.ai.mit.edu -> ftp.gnu.org
>
> Simple question: Is "ftp.gnu.org" definitely the new preferred name for
> "prep.ai.mit.
Tim Sailer asks:
> Is there a problem with them being gatewayed? I find them very useful
I think that there are problems with them being gatewayed.
In general, USENET has a low signal-to-noise ratio, and newsgroups
have much greater exposure and attract a less clueful kind of reader
and poster.
Philip Hands:
> It seems a shame to have to ask people to do this sort of thing.
>
> It strikes me that one should be able to come up with a script that
> does a test of this sort in not much more that the time required to
> write the list (in this simple case at least ;-)
>
> I really think we s
Martin Mitchell <[EMAIL PROTECTED]>:
> It is clear that the actual maintainer, when preparing the new
> release, did not downloaded the non-maintainer release beforehand. The
> non-maintainer releases were made about 2 months before these current
> releases.
>
> While I don't consider these proble
Hamish Moffatt:
> Is the regular maintainer required to apply the diff? In doing
> some non-maintainer upgrades just for libc6 reasons, I have
> fixed some bugs where these are readily fixed. If the non-maintainer
> work does not have to be used, there is every risk of bugs
> being closed which are
Bruce:
> Chris says that all of the mailing lists are gatewayed one-way only,
> and there is no mention of the list address in the headers. Thus, he
> thinks that the people who are finding our list by mistake are doing
> it through some other means. Does this mean that they are finding it
> throug
Tyson Dowd:
> A couple of us discussed this (and other problems with the mailing
> list), in the thread "Duplicate messages on this list" in debian-devel
> about a week ago and eventually came to a standstill where most people
> in the discussion were happy with the following solution:
>
>
440 16444
Bug#16440: From: James Stansell <[EMAIL PROTECTED]>
Bug#16444: lynx: New upstream version available
Merged 16440 16444.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(maintainer, Debian bug tracking system)
--
TO UNSUBSCRIBE FROM T
I'm now properly back. I'll try to catch up on the mailing lists in
the next few days.
After that I'll write up some proposals for organisational structure /
management / etc. and post them to debian-devel for comment, and we'll
take it from there.
Amongst the things I'll propose are:
* Rules f
I think that /usr/src should the be domain of the local admin.
I don't think kernel-{header,source}-x.xx.deb should exist, really,
because I don't think source code should be distributed as .deb files
anyway. So I'm not unhappy about making a policy decision that leaves
kernel-{header,source} wit
Michael Meskes:
> Is auto-pgp still an active package? Or is it as outdated as it seems
> to be. That means it is the only package on my machine that still has
> an AOUT binary.
I don't know about anyone else, but I still use it.
If noone else wants it, since I'm the upstream author, I could qui
The meaning of self-referencing dependencies is as follows:
A (version x) --Depends-> A (no version specified)
A (version x) --Depends-> A (satisfied by x)
A (version x) --Provides-> A (version x)
Useless, but should be allowed and ignored.
A (version x) --Depends-> A (not satisfied by x)
I've just changed the bug system on master to use my new parameterised
version. I hope all is still working well - I've done some cursory
tests, and it doesn't seem _completely_ broken.
Please report all problems ASAP.
Guy: if it all goes apeshit then just get one of the
[EMAIL PROTECTED] people
Following the discussion on debian-policy and elsewhere, there is now
a new `important' bug severity level, which is between `grave' and
`normal'.
It is for bugs which do not meet the criteria for `grave', but which
are nevertheless release-critical.
Ian.
--
TO UNSUBSCRIBE FROM THIS MAILING LIS
James A.Treacy <[EMAIL PROTECTED]>:
> Another person has requested use of the Debian logo. As most people
> are pretty happy with the license I added a clause saying the logo is
> usable under the current license
> (http://www.debian.org/logos/logo.html. Update should reach there
> soon) until 31
Dale Scheetz writes ("Re: Constitution - formal proposal (v0.5)"):
...
> The wording seems clear to me, but the effect is confusing. In effect, if
> a quorum must vote in favor of a proposal for it to pass, and only a
> quorum is present, this condition makes the voting requirement go from
> N:1 to
[EMAIL PROTECTED] writes (chopped and changed):
> Ian Jackson writes:
> > Personally, I _want_ to appoint the technical committee, ...
> > But perhaps the developers don't trust me to do this.
> It isn't a matter of trust, it's a matter of involvement. ...
OK.
Juergen Menden writes ("Re: Constitution - formal proposal (v0.5)"):
> > 2. Decisionmaking bodies and individuals
> >
> >Each decision in the Project is made by one or more of the following:
> > 1. The individual developer working on a particular task;
> > 2. The developers, by way of
Oliver Elphick writes ("Re: Constitution - formal proposal (v0.5) "):
...
> I suggest certain changes between the double lines; lines beginning `X ='
> are to be deleted and replaced:
Thanks a lot. (Your notation was very difficult, btw. You might like
to look into using `diff -u'.)
I have inco
James A.Treacy writes ("Re: Constitution - formal proposal (v0.6)"):
> First a trivial change. "money money" in 9.2.1 should have one money deleted.
>
> Next some suggested changes: 1.) It should be stated somewhere that
> a member of a committee, that is a member of a group for which a
> decision
ckage `general'.
> 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 of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
James A.Treacy writes ("Re: Constitution - formal proposal (v0.6)"):
> [Ian:]
> > I disapprove of the idea of automation.
> >
> > s4.2(5):
> > Proposals, seconds, amendments, calls for votes and other formal
> > actions are made by announcement on a public-readable electronic
> >
eassign 20743 general
Bug#20743: autoup.sh: wtmp, utmp and btmp
Bug reassigned from package `autoup.sh' to `general'.
> reassign 20567 general
Bug#20567: logo license outdated
Bug reassigned from package `logo' to `general'.
> thanks
Stopping processing here.
Please c
und
Changed bug title.
> 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 of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ROTECTED]>
If you wish to continue to submit further information on your problem,
please send it to [EMAIL PROTECTED], as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(administrator, Debian bu
Steve Dunham writes ("Re: dpkg memory usage"):
> John Goerzen <[EMAIL PROTECTED]> writes:
> > I was upgrading packages on my 64 meg system today ant noticed:
> > PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> > 24785 root 18 0 12680 12M 568 S 0 0.1 20.
Brian White writes ("*** The Upcoming Release of Hamm ***"):
...
> So, when will Hamm be released? You decide. It's up to the devolpers
> to set the date by fixing the problems that are currently holding up
> the release. As soon as the last release-necessary bug gets closed or
> downgraded, we'
It will not have escaped the attention of the Project that dpkg hasn't
been very well maintained of late.
Klee seems to have dropped out of sight; I presume he's too busy doing
paid work or something. I'm currently very busy with the leadership
role and a couple of other free software programs (u
41
Bug#21175: Can't load Tix dynamically
Bug assigned to package `tix41'.
> 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 of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
James A.Treacy writes ("Re: Aiding the constitutional procedure [was
Re: Automation of the constitutional procedure]"):
> [Dale:]
> > While I agree with the merrits of your previous arguments, I don't see
> > what this has to do with the constitution. The secretary has "powers"
> > which allow the
[EMAIL PROTECTED] writes ("Re: dpkg memory usage"):
...
> I've written a Regina REXX program to run some comparisons
> between the dpkg/status file and current Packages (+non-free,
> contrib, nonus) files. It currently shows which files need
> updating, misconfigured packages, shows a deb's paragra
I think we should make it someone's job to collate versions and
amendments &c, so that the secretary doesn't have to do it unless they
want to.
So, I'm considering inserting after A.2 `Calling for a vote' 2.:
3. The person who calls for a vote states what they believe the
wordings of the res
7; to `libpng2'.
> reassign 21179 ssh
Bug#21179: ssh generating new host key
Bug reassigned from package `ssy' to `ssh'.
> 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 of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t to `important'.
> merge 21253
Unknown command or malformed arguments to command.
> 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 of &
Processing commands for [EMAIL PROTECTED]:
> merge 21253 20587
Bug#20587: There's no current libg++ package
Bug#21253: gperf can't be installed with libstdc++
Merged 20587 21253.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(admin
king
Bug reassigned from package `base' to `general'.
> stop
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]
This discussion is ridiculous.
In my view singular `they' is perfectly correct. If I can use it in
my PhD thesis (with a footnote[1] and supporting references, and
without any complaint from the examiners) then we can use it here.
Furthermore, language is defined by use, not by prescription (try
Richard Braakman writes ("Re: Constitution - formal proposal (v0.7)
(comments)"):
...
> All three looked the same to me; I hope they were :-)
Yes; I should make this clearer next time.
> I had trouble understanding the second paragraph of section 1:
>
>This document describes the organisati
We should modify our libc so that opening a file in /tmp or /var/tmp -
determined by simple string comparison of the filename passed to
open(2) - fails if O_CREAT is specified without O_EXCL.
We should do this in slink. That way almost any program with a /tmp
security hole will stop working strai
Manoj Srivastava writes ("Re: /tmp exploits"):
...
> I think I would want echo blah > /tmp/junk nto to start
> failing on my just because there is a file called junk already
> in there. Modifying libc is too deep rooted a change; and modifes the
> semantics of /tmp in an unacceptable fashi
rf can't be installed with libstdc++
Severity set to `normal'.
> retitle 20587 Fixed in NMU: There's no current libg++ package
Bug#20587: There's no current libg++ package
Changed bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
I
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
program
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 co
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 th
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
.chan
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
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 use
Manoj Srivastava writes ("Linking a static library with -fPIC for flex"):
> I was initially going to just provide libfl.a with position
> independent code, which would have prevented the FTBS breakage for
> scanner containing shared libraries, at the expense of a register
> lost for bina
John Wright writes ("Re: Bug#390754: O: piuparts -- .deb package installation,
upgrading, and removal testing tool"):
> I would be interested in co-maintaining this package. I don't think I
> have the time to give it the full attention it would need (e.g. filing
> bugs on packages that fail), bu
Gustavo Noronha Silva writes ("Re: anticipating the upstart migration"):
> The alternatives system is quite mature; it suffered from leaving
> dangling alternatives, but that was ages ago...
The alternatives system must not be used for any of the essential
files of an essential package.
This is b
Manoj Srivastava writes ("Making SELinux standard for etch"):
> We are at a point where we can support a targeted SELinux
> policy, at least in permissive mode. Everything seems to work for
> me; I can fire up targeted SELinux UML's and only see a few harmless
> log messages.
I am deep
On Wed, OcFt 04, 2006 at 09:32:16AM +0200, Frank Küster wrote:
> However, I'd like to point out that this problem is not special to TeX.
> Many programs create ~/.progname directories when run for the first time
> - and these directories contain configuration options which might cause
> trouble, si
Eric Dorland writes ("Re: anticipating the upstart migration"):
> Shouldn't it be possible to move the alternatives around in an atomic
> fashion? ln -sf bar foo.tmp ; mv foo.tmp foo . Or am I missing
> something?
This is in theory possible, I suppose. You would have to avoid
update-alternatives
Matthew Wilcox writes ("Re: Lack of a GR proposal explicitly condemning
dunc-tank"):
> I'm so thoroughly disgusted by you and the actions of people like you
> that I've stopped working on Debian. nice job, wanker.
That is the sole content of Matthew Wilcox's message to me, apart from
some quoted
Mr Yan writes ("Re: Making SELinux standard for etch"):
> Ian Jackson wrote:
> > if (selinux_enabled > 0)
> > if(setfscreatecon(NULL) < 0)
> > perror("Error restoring default security context:");
> >
> > Error che
e. So here is the whole of Matthew's
message, including the text of my message which he is objecting to:
On Wed, Oct 11, 2006 at 02:17:50PM +0100, Ian Jackson wrote:
> So I'd like to encourage dunc-tank opponents to consider whether they
> ought to have seconded my resoluti
Russ Allbery writes ("Re: Request for virtual package ircd"):
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > m-t-a's must conflict because they are required by policy to provide a
> > sendmail program at a fixed filesystem location.
>
> I was about to say the same thing earlier, but then realize
Tollef Fog Heen writes ("Re: mucking with dpkg control files in maintainer
scripts?"):
> old_md5sum="`sed -n -e \"/^Conffiles:/,/^[^ ]/{' $CONFFILE'{s/.*
> //;p}}\" /var/lib/dpkg/status`"
This is completely and utterly wrong and gives _wrong answers_.
/var/lib/dpkg/status is not gua
Frank Küster writes ("Re: mucking with dpkg control files in maintainer
scripts?"):
> I think the main reason why this is not being done is that there's a
> general fear that calling "dpkg -s" from a script that has been called
> by dpkg might give unpredictable, or at least not the desired result
Bill Allombert writes ("Getting rid of circular dependencies, stage 6"):
> Thanks to your collective effort, the number of circular dependencies in
> Debian has halved since the begining of the year.
... but as previously discussed there is nothing wrong with circular
dependencies. (Although of c
Manoj Srivastava writes ("Re: Bug mass filling"):
> On Fri, 20 Oct 2006 17:18:41 -0700, Steve Langasek <[EMAIL PROTECTED]> said:
> > When there are issues addressed in policy that are black-and-white
> > where all violations of the policy requirement are definitely bugs,
> > but not all such viola
Manoj Srivastava writes ("Re: Bug mass filling"):
> On Tue, 24 Oct 2006 17:18:20 +0100, Ian Jackson <[EMAIL PROTECTED]> said:
> > There are two different and orthogonal properties of a policy
> > requirement:
> > 1. [...]
> > [and]
> > 2. I
Manoj Srivastava writes ("Re: Bug mass filling"):
> On Tue, 24 Oct 2006 17:18:20 +0100, Ian Jackson <[EMAIL PROTECTED]> said:
> > There are two different and orthogonal properties of a policy
> > requirement:
> >
> > 1. Is the requirement applicable in
Frank Küster writes ("Re: mucking with dpkg control files in maintainer
scripts?"):
> In other words, "commits" to the dpkg database are atomic, and if dpkg
> is called from a script started by dpkg, it will report all packages in
> the correct, current and maybe partial state, including the packa
Goswin von Brederlow writes ("Re: mucking with dpkg control files in maintainer
scripts?"):
> Isn't it more accurate to say that the dpkg database is transaction
> based? Changes are recorded on the fly in updates and then commited
> attomically when the transaction is finished.
No. Updates writ
Charles Plessy writes ("Where to put non-locale global environment settitngs
?"):
> Users are now told to use /etc/defaults/locale instead of
> /etc/environment for setting system-wide default language. But what
> about the non-locale environment variables that users also put in
> /etc/environment
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
> cg
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 pu
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 kn
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 debian
1 - 100 of 2525 matches
Mail list logo
