Thank you for your response. Please don't reply to this message - it is an
automated response and your reply will not be received.
If you have a question for eBay Customer Support, please visit the following
eBay Help page. This page will help you locate the answer to your question, or
assist
[Steve Greenland]
> Guess what? This is not a paid support forum, or a commercial
> organization. This is a *community*. Communities have cultures,
> traditions, in-jokes, etc. You can either choose to be part of that
> community, and learn to be part of the culture, or you can go join a
> differen
Hello!
As I understand, deleting start links with 'update-rc.d -f apache remove' is
the Debian way of removing start calls for services at boot time.
After every package upgrade of e. g. apache, I must call this command again,
because start links were be installed again. Is it the normal behavi
On Wed, Jan 12, 2005 at 09:41:34AM +0100, Erik Schanze wrote:
> As I understand, deleting start links with 'update-rc.d -f apache remove' is
> the Debian way of removing start calls for services at boot time.
>
> After every package upgrade of e. g. apache, I must call this command again,
> beca
On Wed, 12 Jan 2005 09:41:34 +0100, Erik Schanze wrote:
> As I understand, deleting start links with 'update-rc.d -f apache remove' is
> the Debian way of removing start calls for services at boot time.
No. Generally update-rc.d is a tool for maintainer scripts not for the admin to
use.
Its man
Package: wnpp
Severity: wishlist
* Package name: ooo2dbk
Version : 1.2.2-1
Upstream Author : Indesko ([EMAIL PROTECTED])
* URL : http://www.indesko.com/telechargements/
* License : LGPL
Description : OpenOffice.org SXW to DocBook XML converter (sxw to xml)
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
> [No Cc needed, as per list policy]
>
> On Tue, Jan 11, 2005 at 11:47:42PM +0100, Pierre Habouzit wrote:
> > > it's _quite_ true that you don't need to play with include_path.
> > > your library has to know it's installed
> > > into /usr/share
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
> So you patch libfile2.php to require_once 'mylib/libfile1.php'
> instead of just 'libfile1.php'.
oh and btw, the suggestion I did is better (IMHO) :
replace require_once 'libfile.php'; with
require dirname(__FILE__).'/'.'libfile1.php';
be
Hi Michal!
Michal Politowski <[EMAIL PROTECTED]>:
> On Wed, 12 Jan 2005 09:41:34 +0100, Erik Schanze wrote:
> > As I understand, deleting start links with 'update-rc.d -f apache remove'
> > is the Debian way of removing start calls for services at boot time.
>
> No. Generally update-rc.d is a tool
On Wed, Jan 12, 2005 at 01:12:08AM -0500, William Ballard wrote:
> And *I'm* being precise when I said "foo 1.0" is removed and not
> replaced.
This is what Cameron said:
> > User runs "dpkg -i foo-modules_2.0_arch.deb"
> >
> > dpkg first removes foo-modules_1.0
> > dpkg then check dependencie
On Wed, Jan 12, 2005 at 10:13:05AM +0100, Pierre Habouzit wrote:
> Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
> > [No Cc needed, as per list policy]
> >
> > On Tue, Jan 11, 2005 at 11:47:42PM +0100, Pierre Habouzit wrote:
> > > > it's _quite_ true that you don't need to play with includ
On Wed, 12 Jan 2005 10:16:43 +0100, Pierre Habouzit
<[EMAIL PROTECTED]> wrote:
> Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
> > So you patch libfile2.php to require_once 'mylib/libfile1.php'
> > instead of just 'libfile1.php'.
>
> oh and btw, the suggestion I did is better (IMHO) :
>
* Petter Reinholdtsen
| [Steve Greenland]
| > Guess what? This is not a paid support forum, or a commercial
| > organization. This is a *community*. Communities have cultures,
| > traditions, in-jokes, etc. You can either choose to be part of that
| > community, and learn to be part of the cultur
[Tollef Fog Heen]
> The question is what's considered rude. What's not rude on
> debian-devel might be considered rude in other fora and vice versa.
That might be your question, but it isn't mine. :) Calling someone a
dickhead is rude in most fora. I suspect most of us know when we are
trying t
> dpkg (1.10.26) unstable; urgency=low
>
> * ...
>
> * Revert to current 'stable' behaviour of Space/Enter/'Q' in the dselect
> help screen, Space leaves the help screen and Enter and 'Q' do nothing.
> It's dangerous to encourage users to press Enter or 'Q' since they
> commit cha
Le Mer 12 Janvier 2005 10:50, Kees Leune a écrit :
> On Wed, 12 Jan 2005 10:16:43 +0100, Pierre Habouzit
>
> <[EMAIL PROTECTED]> wrote:
> > Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
> > > So you patch libfile2.php to require_once 'mylib/libfile1.php'
> > > instead of just 'libfile1.php
On Wed, Jan 12, 2005 at 07:47:50PM +1100, Hamish Moffatt wrote:
> This is an excellent question for debian-user. Or Google.
And a question which has been answered countless times and is even
documented already (besides the manpage itself) at
http://www.debian.org/doc/manuals/securing-debian-howt
Domenico Andreoli wrote:
[snip]
> oh no, these are bad news :(
>
> i found it very fast using Enter to exit the help message. i'm not
> talking about the first one shown on entering package selection but the
> (usually "many") ones shown before dependency conflict resolution. it
> was everything i
Hi Martin
On Tuesday 11 January 2005 21:40, Martin Zobel-Helas wrote:
> Hi Frederik,
>
> On Tuesday, 11 Jan 2005, you wrote:
> > BTW, what does RoM and RoQA mean?
>
> RoM: Request of Maintainer
> RoQA: Request of QA Group
Thanks, bug report sent away with subject of
"RM: mozilla-firefox-locale-d
* Scott James Remnant <[EMAIL PROTECTED]> [050111 20:10]:
> > Of course this is the right way to do, but sometimes users are
> > lazy (or just expect different things, and some of them appear here,
> > with their arrogant attitude, pissed and beeing polemic).
> >
> Actually users will be more like
Hi!
Anyone can give a pointer for doc's how to build apache modules
for Debian? I already looked at some examples but that didn't
helped much.
Sorry if this question answered already or the location of doc's
(policy) is easy to find.
TIA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
Hello Milan,
* Milan P. Stanic <[EMAIL PROTECTED]> [2005-01-12 14:16]:
> Anyone can give a pointer for doc's how to build apache modules
> for Debian? I already looked at some examples but that didn't
> helped much.
>
> Sorry if this question answered already or the location of doc's
> (policy) i
On 12-Jan-05, 02:05 (CST), Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
> Being part of a community or not being paid is not a valid excuse for
> being rude to others. I happen to be part of this community too, and
> I do not treasure being rude as a positive side of the debian
> community.
Bu
Ron Johnson wrote:
On Wed, 2005-01-12 at 00:06 +, Henning Makholm wrote:
Scripsit Ron Johnson <[EMAIL PROTECTED]>
If you want sweetness and light, just tell them which document
to read.
If I want sweetness and light I don't pretend that I think somebody
needs to have explained what documentat
On 2005-01-12, Milan P. Stanic <[EMAIL PROTECTED]> wrote:
> Sorry if this question answered already or the location of doc's
> (policy) is easy to find.
apache-dev includes `/usr/share/doc/apache-dev/README.modules' which
contains a set of simple guidelines on how to integrate external Apache
modu
On Wed, 2005-01-12 at 11:19 +0100, Domenico Andreoli wrote:
> > dpkg (1.10.26) unstable; urgency=low
> > * Revert to current 'stable' behaviour of Space/Enter/'Q' in the dselect
> > help screen, Space leaves the help screen and Enter and 'Q' do nothing.
> > It's dangerous to encourage us
On Tue, 2005-01-11 at 21:57 -0800, Michael K. Edwards wrote:
> What would be the impact on (c)debootstrap of changing the operation
> of dpkg?
>
Forget the impact on debootstrap, the impact on APT and dselect is
pretty huge. dpkg is designed to be able to unpack packages while their
dependencies
On Wed, Jan 12, 2005 at 11:19:26AM +0100, Domenico Andreoli wrote:
> > dpkg (1.10.26) unstable; urgency=low
> > * Revert to current 'stable' behaviour of Space/Enter/'Q' in the dselect
> > help screen, Space leaves the help screen and Enter and 'Q' do nothing.
> > It's dangerous to encour
On Wed, Jan 12, 2005 at 02:19:32PM +0100, Nico Golde wrote:
> Hello Milan,
>
> * Milan P. Stanic <[EMAIL PROTECTED]> [2005-01-12 14:16]:
> > Anyone can give a pointer for doc's how to build apache modules
> > for Debian? I already looked at some examples but that didn't
^
On Wed, Jan 12, 2005 at 03:06:06PM +, Scott James Remnant wrote:
> What William Ballard, Cameron Hutchinson and Eduard Bloch are asking for
> is to remove the difference between Depends and Pre-Depends and make all
> Depends behave like Pre-Depends.
No: I do not want dependencies to be INSTALL
Steve Langasek <[EMAIL PROTECTED]> writes:
> Recommends means "packages that would be found together with this one in all
> but unusual installations". It is not unusual to have a single designated
> build machine in an organization, which may or may not ever have the final
> binary packages inst
On Wed, Jan 12, 2005 at 03:44:45PM +0100, Michael Ablassmeier wrote:
> On 2005-01-12, Milan P. Stanic <[EMAIL PROTECTED]> wrote:
> > Sorry if this question answered already or the location of doc's
> > (policy) is easy to find.
>
> apache-dev includes `/usr/share/doc/apache-dev/README.modules' whi
Hi all,
it seems to be consensus that one should generally not "correct" older
changelog entries, like adding (closes: #...) if it turns out later that
this bug had been closed by this release. I am wondering whether there
is an exception to this rule, namely packages in experimental. The
changel
On Wed, Jan 12, 2005 at 05:10:39PM +0100, Frank K?ster wrote:
> Hi all,
>
> it seems to be consensus that one should generally not "correct" older
> changelog entries, like adding (closes: #...) if it turns out later that
> this bug had been closed by this release. I am wondering whether there
>
Steve Greenland wrote:
And yes, community standards can and do change. But they don't get
changed by people whining about them; they get changed by the members
behaving differently.
ACK.
This standard of a community can be different to that, what individuals
would expect. As a result the activity
Hello!
I need to compile libc4 on a brand-new unstable Debian machine in
order to run a 10-year old executable (it only needs /libc.so.4). I
believe it is doable (famous last words!), but I wanted to consult
this list (which I hope is the correct one) in order to check if there
is somebody out th
On Jan 12, Hal Niner <[EMAIL PROTECTED]> wrote:
> I need to compile libc4 on a brand-new unstable Debian machine in
> order to run a 10-year old executable (it only needs /libc.so.4). I
> believe it is doable (famous last words!), but I wanted to consult
It /may/ be doable, but not without a lot
On Wed, 12 Jan 2005, Hal Niner wrote:
> I need to compile libc4 on a brand-new unstable Debian machine in
> order to run a 10-year old executable (it only needs /libc.so.4). I
> believe it is doable (famous last words!), but I wanted to consult
> this list (which I hope is the correct one) in ord
Hal Niner <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I need to compile libc4 on a brand-new unstable Debian machine in
> order to run a 10-year old executable (it only needs /libc.so.4). I
> believe it is doable (famous last words!), but I wanted to consult
> this list (which I hope is the correct o
* Frederik Dannemare:
> I'll dare to take the other route and ask: what is now holding back
> software such as mplayer/mencoder, transcode and mjpegtools from
> entering Debian?
Same as ever, sufficiently influential people oppose it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Frank KÃster <[EMAIL PROTECTED]> writes:
> it seems to be consensus that one should generally not "correct" older
> changelog entries, like adding (closes: #...) if it turns out later that
> this bug had been closed by this release. I am wondering whether there
> is an exception to this rule, nam
Hi all,
I've been manually filing bugs against packages with improper
copyright files, as per this thread:
http://lists.debian.org/debian-devel/2004/03/msg02190.html
I stopped when I started gettign consecutive bug numbers :) I've been
using Severity: normal, although it is arguably a violati
On Wed, Jan 12, 2005 at 01:01:34PM -0500, Jay Berkenbilt wrote:
> ... or put an entry in the latest changelog block with a parenthetical
> remark saying that bug was actually fixed by version x.y-z.
I've seen this done more often, and frankly, in my opinion this really
is ugly. There is text in a
On Wed, Jan 12, 2005 at 10:05:00AM -0600, Matthew Dempsky wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > Recommends means "packages that would be found together with this one in all
> > but unusual installations". It is not unusual to have a single designated
> > build machine in an or
On Tuesday 11 January 2005 20:29, Frederik Dannemare wrote:
> Hi,
>
> how should I properly approach the removal of a package which I
> maintain?
>
> Package in question is mozilla-firefox-locale-da which is to be
> replaced by mozilla-firefox-locale-da-dk (not maintained by me) from
> source packa
Jay Berkenbilt <[EMAIL PROTECTED]> wrote:
> I personally feel that adding new changelog "blocks" is okay but
> editing old changelog blocks isn't okay, even if you are going to do a
> subsequent build with a -v when you go back to unstable. I would
> either close the bug manually or put an entry
On Wed, 12 Jan 2005 10:05:00 -0600, Matthew Dempsky wrote:
[...]
> If a new version of ndiswrapper-utils is not backwards-compatible with
> an old version of ndiswrapper-modules, shouldn't it declare a
> versioned Conflicts with those older versions or else when you try to
> upgrade you'll have pro
Scripsit Scott James Remnant <[EMAIL PROTECTED]>
> Forget the impact on debootstrap, the impact on APT and dselect is
> pretty huge. dpkg is designed to be able to unpack packages while their
> dependencies are not yet fulfilled.
But don't apt and dselect already invoke dpkg with special options
Frederik Dannemare <[EMAIL PROTECTED]> wrote:
> On Tuesday 11 January 2005 20:29, Frederik Dannemare wrote:
>> Package in question is mozilla-firefox-locale-da which is to be
>> replaced by mozilla-firefox-locale-da-dk (not maintained by me) from
>> source package mozilla-firefox-locale-all.
>>
>>
On Wednesday 12 January 2005 19:39, Frank Küster wrote:
> Frederik Dannemare <[EMAIL PROTECTED]> wrote:
> > On Tuesday 11 January 2005 20:29, Frederik Dannemare wrote:
> >> Package in question is mozilla-firefox-locale-da which is to be
> >> replaced by mozilla-firefox-locale-da-dk (not maintained
Anthony Towns writes:
> Frank Küster wrote:
>
> > Do I understand right that you recommend not to use libfoo1-dev,
> > libfoo2-dev generally, but that the most recent version should be just
> > libfoo-dev? The Debian library packaging guide gives the opposite
> > advice, to use libfoo-dev always,
On Wed, 12 Jan 2005, Frank Küster wrote:
> Frederik Dannemare <[EMAIL PROTECTED]> wrote:
>
> > On Tuesday 11 January 2005 20:29, Frederik Dannemare wrote:
> >> Package in question is mozilla-firefox-locale-da which is to be
> >> replaced by mozilla-firefox-locale-da-dk (not maintained by me) from
* Florian Weimer ([EMAIL PROTECTED]) wrote:
> * Frederik Dannemare:
>
> > I'll dare to take the other route and ask: what is now holding back
> > software such as mplayer/mencoder, transcode and mjpegtools from
> > entering Debian?
>
> Same as ever, sufficiently influential people oppose it.
W
On Wed, 12 Jan 2005 18:09:18 +0100, Helmut Wollmersdorfer
<[EMAIL PROTECTED]> wrote:
[snip]
> My few attempts to step into debian as a contributor ended after some
> hours of senseless discussions or waste of time against unnecessary
> barriers. Compared against average OSS, or OSS where I contribu
On Wed, 2005-01-12 at 18:28 +, Henning Makholm wrote:
> Scripsit Scott James Remnant <[EMAIL PROTECTED]>
>
> > What's interesting is nobody has jumped in on this thread to point out
> > that dpkg *has* a dependency field for forcing checking of dependencies
> > before the package is unpacked.
Scripsit Justin Pryzby <[EMAIL PROTECTED]>
> Copyright:
> GPL 2.0
> Copyright: Most recent version of the GPL.
> Copyright:
> [GPL follows]
http://lintian.debian.org/reports/Tcopyright-should-refer-to-common-license-file-for-gpl.html
lists 264 packages. Some of the
On Wed, 2005-01-12 at 12:52 -0500, Justin Pryzby wrote:
> Hi all,
>
> I've been manually filing bugs against packages with improper
> copyright files, as per this thread:
>
> http://lists.debian.org/debian-devel/2004/03/msg02190.html
>
> I stopped when I started gettign consecutive bug numbers
Scripsit Jens Peter Secher <[EMAIL PROTECTED]>
> But the advice in the library packaging guide is to do something like
> Package: libpackage2-dev
> Provides: libpackage-dev
> Conflicts: libpackage-dev
> AFAICT the above approach offers nothing more than simply
> Package:
Scripsit Erik Schanze <[EMAIL PROTECTED]>
>> PS. this is a topic for debian-user not debian-devel
> Right, but I asked for a package for bug reporting.
That is, too, within debian-user's topic.
--
Henning Makholm "It will be useful even at this
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> On Wed, Jan 12, 2005 at 01:01:34PM -0500, Jay Berkenbilt wrote:
>> ... or put an entry in the latest changelog block with a parenthetical
>> remark saying that bug was actually fixed by version x.y-z.
>
> I've seen this done more often, and frank
On Wednesday 12 January 2005 11:52 am, Scott James Remnant wrote:
> It's breaking elegance to fix something I'm not convinced is a problem.
Just to be clear: you mean the elegance of the dpkg code, not its external
behavior, right? Because I don't see anything elegant about erroring out and
l
On Wed, 2005-01-12 at 12:26 -0800, Daniel Burrows wrote:
> On Wednesday 12 January 2005 11:52 am, Scott James Remnant wrote:
> > It's breaking elegance to fix something I'm not convinced is a problem.
>
> Just to be clear: you mean the elegance of the dpkg code, not its external
> behavior, ri
* "Milan P. Stanic"
| I thought such file is in the apache-dev and my first search was
| there but without luck. After your answer I think that must be for
| the testing/unstable, but not for stable.
| And I have only stable/woody.
You really don't want to develop new packages for apache 1 and
c
Henning Makholm <[EMAIL PROTECTED]> writes:
> Scripsit Jens Peter Secher <[EMAIL PROTECTED]>
>
> > But the advice in the library packaging guide is to do something like
> > Package: libpackage2-dev
> > Provides: libpackage-dev
> > Conflicts: libpackage-dev
> > AFAICT the above approach
On Wed, Jan 12, 2005 at 08:37:04PM +, Scott James Remnant wrote:
> Why not? It means that you just need to go fetch and install the
> dependency, you don't need to try and install the depending package
> again.
Yeah, that's real "elegant."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Wednesday 12 January 2005 12:37 pm, Scott James Remnant wrote:
> On Wed, 2005-01-12 at 12:26 -0800, Daniel Burrows wrote:
> > On Wednesday 12 January 2005 11:52 am, Scott James Remnant wrote:
> > > It's breaking elegance to fix something I'm not convinced is a problem.
> >
> > Just to be clear
Hamish Moffatt wrote:
> Yes: don't remove ALL the links. If you keep some (eg all the K stop
> links), update-rc.d will not add any new ones.
I dunno, I've seen some strange things lately with bind9 and ipmasq
links that I'm quite sure were only disabled at rc2.d coming back on
upgrade. Not conclu
Scripsit Scott James Remnant <[EMAIL PROTECTED]>
> On Wed, 2005-01-12 at 12:26 -0800, Daniel Burrows wrote:
>> Just to be clear: you mean the elegance of the dpkg code, not its
>> external behavior, right? Because I don't see anything elegant
>> about erroring out and leaving an operation half-c
Scripsit Jens Peter Secher <[EMAIL PROTECTED]>
> Henning Makholm <[EMAIL PROTECTED]> writes:
>> If the source-level API differs, then having libpackage2-dev will
>> allow other packages to Build-Depend on the API they are written
>> against. Of course this is especially relevant when the API chang
On Wed, Jan 12, 2005 at 09:25:12PM +0100, Tollef Fog Heen wrote:
> You really don't want to develop new packages for apache 1 and
> certainly not for the apache in woody. Woody's apache is broken in
> so many and interesting ways it's beyond funny and into the scary
> territory. Apache 1 is going
> > This is an excellent question for debian-user. Or Google.
>
> And a question which has been answered countless times and is even
Given that this comes up so often, is there a reason not to add an
option to update-rc.d that does this? The problem here is that
"remove" sounds like "disable th
Package: wnpp
Severity: wishlist
* Package name: mocp
Version : 2.1.4
Upstream Author : Damian Pietras <[EMAIL PROTECTED]>
* URL : http://moc.daper.net/
* License : GPL
Description : ncurses based console audio player
mocp (music on console player) is a
Hi,
We are a small company from Romania - AMS Software -
that produces multimedia software.We made a
programming language, especially created to make
multimedia applications, called MPL (Multimedia
Programming Language). The main advantage of this
project is that MPL applications runs on all the
p
On Wed, Jan 12, 2005 at 11:48:05AM -0800, Michael K. Edwards wrote:
> On Wed, 12 Jan 2005 18:09:18 +0100, Helmut Wollmersdorfer
> <[EMAIL PROTECTED]> wrote:
> [snip]
> > My few attempts to step into debian as a contributor ended after some
> > hours of senseless discussions or waste of time against
[No Cc please, as per list policy]
On Wed, Jan 12, 2005 at 10:16:43AM +0100, Pierre Habouzit wrote:
> Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
> > So you patch libfile2.php to require_once 'mylib/libfile1.php'
> > instead of just 'libfile1.php'.
>
> oh and btw, the suggestion I did
Will Lowe <[EMAIL PROTECTED]>:
> Given that this comes up so often, is there a reason not to add an
> option to update-rc.d that does this? The problem here is that
> "remove" sounds like "disable this".
>
> I'm thinking have "update-rc.d -f foo disable" do the same thing as
> "update-rc.d -f foo
> On Wed, Jan 12, 2005 at 10:16:43AM +0100, Pierre Habouzit wrote:
> > Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
> > > So you patch libfile2.php to require_once 'mylib/libfile1.php'
> > > instead of just 'libfile1.php'.
> >
> > oh and btw, the suggestion I did is better (IMHO) :
> >
>
On Wed, Jan 12, 2005 at 12:52:06PM -0500, Justin Pryzby wrote:
> Hi all,
>
> I've been manually filing bugs against packages with improper
> copyright files, as per this thread:
>
> http://lists.debian.org/debian-devel/2004/03/msg02190.html
The example here is not a good one. While it's not de
On Wed, Jan 12, 2005 at 01:38:28PM -0500, Andres Salomon wrote:
> Of course. No one has provided proof that this is the case, though. I
> asked if a versioned depends was necessary, but instead got accusations
> and vitriol. I have not had time to test it myself yet.
Some of the other *-source
Andreas Barth wrote:
with ideas and code (and a lot more) from Anthony, I was able to put
together the server part for partial patches in a way that it seems to
me that it might be included in dak. The resulting files are available
from
deb http://merkel.debian.org/~aba/debian sid main contrib non
On Wed, 12 Jan 2005 23:55:03 +0100, Erik Schanze <[EMAIL PROTECTED]> wrote:
> Will Lowe <[EMAIL PROTECTED]>:
> > I'm thinking have "update-rc.d -f foo disable" do the same thing as
> > "update-rc.d -f foo remove && update-rc.d foo stop stop 0", and
> > clearly document this in the manual page, so t
Dear gksu maintainer
Can you make gksu's default behavior to be "gksu --disable-grub" ?
I think we loose nothing significant by doing this. We gain remote
access and we gain stable invocation of configuration tools under CJK
environment where input method (IM) support is needed as I read BTS.
Si
> It does exactly as suggested above:
> * remove existing symlinks
> * add stop with priority 0
> * remember original priorities when enabling them later on
... but is not scriptable. I'm thinking of environments like a large
number of hosts managed with cfengine -- update-rc.d is a handy
one-lin
Em Qui, 2005-01-13 Ãs 01:31 +0100, Osamu Aoki escreveu:
> Dear gksu maintainer
Hey Osamu,
I've been really bad at responding to your queries lately, I'm very
soory about that =/
> Can you make gksu's default behavior to be "gksu --disable-grub" ?
s/grub/grab/, FWIW
After reading your e-mail, I
At Tue, 11 Jan 2005 11:27:28 +0100,
Falk Hueffner wrote:
> > Marcelo E. Magallon <[EMAIL PROTECTED]> wrote:
> >> Mesa upstream uses -mcpu=ev5 -mieee on alpha. Is that ok? Where does
> >> this belong into? /usr/lib/ev5?
> >
> > IIRC, alpha does not define any hwcaps.
>
> There's a patch for thi
At Tue, 11 Jan 2005 19:03:44 -0600,
Marcelo E. Magallon <[EMAIL PROTECTED]> wrote:
> > Note that MMX will be removed from the next glibc 2.3.4 upload. It
> > will provide only SSE2 (and CMOV, debian-specific for only VIA C3
> > processor).
>
> Well, there's hand-crafted MMX code, so it's runt
Re: Matthew Garrett in <[EMAIL PROTECTED]>
> Can't you just grab a libc4 deb from archive.debian.org? That worked
> fine last time I tried it.
[0] [EMAIL PROTECTED]:~ $host archive.debian.org
archive.debian.org has address 208.185.25.38
[0] [EMAIL PROTECTED]:~ $host 208.185.25.38
38.25.185.208.in-
* Henning Makholm ([EMAIL PROTECTED]) wrote:
> In summary: Yes, one could probably work around the lack of versions
> in the -dev packages name, but the result would be (in my view)
> significantly less elegant than having it there.
Trying to support unsupported versions of libraries is decidely w
On Sun, Jan 09, 2005 at 09:44:26AM -0500, Roberto Sanchez wrote:
> Quoting Ola Lundqvist <[EMAIL PROTECTED]>:
>
> > Hello
> >
> > Instead of doing all this by hand I can recommend my own package
> > debarchiver. The latest versions of it do this pretty good in
> > an automatic way.
> >
> > Just
On Wed, Jan 12, 2005 at 03:20:19PM +, Colin Watson wrote:
> The change *to* Enter was the thing that broke dselect for those of us
> who have been using it since woody and earlier. Switching back to the
> old behaviour unbroke it. As the changelog message states, encouraging
> people to press E
Andrew Suffield <[EMAIL PROTECTED]> writes:
> For a GPLed project, the declaration looks something like this:
>
> * Copyright (C) Andrew Suffield <[EMAIL PROTECTED]>
Shouldn't you include a year?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
The stats:
8,920 source packages in Debian unstable main.
8,254 declare a build-dependency on debhelper
= 92% of packages build-depend on debhelper.
Is that sufficient to declare it build-essential?
The downside:
Package: debhelper
Depends: perl (>= 5.6.0-16), coreutils | fileutil
On Thu, 2005-01-13 at 14:00 +1100, Hamish Moffatt wrote:
> On Wed, Jan 12, 2005 at 03:20:19PM +, Colin Watson wrote:
> > The change *to* Enter was the thing that broke dselect for those of us
> > who have been using it since woody and earlier. Switching back to the
> > old behaviour unbroke it
On Thu, Jan 13, 2005 at 04:07:29AM +, Scott James Remnant wrote:
> The stats:
>
> 8,920 source packages in Debian unstable main.
> 8,254 declare a build-dependency on debhelper
>
> = 92% of packages build-depend on debhelper.
>
> Is that sufficient to declare it build-essential?
>
>
Henning Makholm wrote:
Scripsit Jens Peter Secher <[EMAIL PROTECTED]>
But the advice in the library packaging guide is to do something like
Package: libpackage2-dev
Provides: libpackage-dev
Conflicts: libpackage-dev
If the source-level API differs, then having libpackage2-de
Works a little better with the following patch to untiffani:
--- /usr/local/bin/untuttifrutti2005-01-12 21:54:38.0 -0800
+++ /usr/local/bin/untiffani2005-01-12 21:27:07.0 -0800
@@ -16,7 +16,7 @@
c_size="-1"
cur_sha1 () {
if [ "$c_sha1" = "" ]; then
-c_sha1=$(sh
On 10168 March 1977, Scott James Remnant wrote:
> = 92% of packages build-depend on debhelper.
> It can be argued that these are already effectively build-essential due
> to the high number of packages build-depending on them anyway.
I think it should be b-e, but with a versioned dep thats high
On Thursday 13 January 2005 02:29, Will Lowe wrote:
> > It does exactly as suggested above:
> > * remove existing symlinks
> > * add stop with priority 0
> > * remember original priorities when enabling them later on
>
> ... but is not scriptable. I'm thinking of environments like a large
> number
98 matches
Mail list logo
