> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
Manoj> I disagree. Developers reference still exists, and so
Manoj> does the packaging manual. The packaging manual is merely
Manoj> no longer policy.
There is no link to the packaging manual from w.d.o/devel and there
> "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> What exactly do you want in policy? `if you behave like
Wichert> the old suidregister don't do this' or so? I really don't
Wichert> see the use of that.
The conflicts that man dh_suidregister mentions should be i
> "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> Policy should set guidelines for making packages [...]
Wichert> The less details, the better.
Um. Policy *IS* the guide for making packages now. There's no
Packaging Manual any more, and so these kinds of details
> "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Julian> dpkg-statoverride --list is OK, adding or removing
Julian> overrides is almost certainly not.
Wichert> It most certainly is. Think dynamic useres and groups,
Wichert> user interaction if debconf isn't availabl
Package: debian-policy
Version: 3.5.2.0
Severity: wishlist
The man page for dh_suidregister says that any package containing a
SUID/SGID binary no longer needs to use suidregister, instead, users
can use dpkg-statoverride as necessary.
Policy (section 11.9, "Permissions and Owners") doesn't talk
Here's a question:
Should these packages built with BUILD_DEBUG turned on have a different
name (i.e. libgtk1.2-dbg) than the standard packages? Is there an
easy way to do this other than replicating control file entries?
--
Brought to you by the letters G and Z and the number 18.
"What's differ
> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Santiago> Symlinking /usr/doc/ to
Santiago> /usr/share/doc/ directly is not supported by
Santiago> dpkg, so additional and ugly tweaks would be required in
Santiago> maintainer scripts.
Joey> Could you be a little more clea
> "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes:
Joseph> Actually, Debian's kernel-{source,headers} packages both
Joseph> update /usr/src/linux to point at the correct directory
Joseph> and the documentation available indicates that
Joseph> /usr/src/linux is a symlink wh
> "Theodore" == Theodore Y Ts'o <[EMAIL PROTECTED]> writes:
Theodore> I agree, and I do accept the path to a version of the
Theodore> kernel tree it shall be compiled for. It requires
Theodore> editing the Makefile, though, and this is not pleasant
Theodore> for naive users.
> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
Brian> Yes, the headers under /usr/include should match the
Brian> current kernel version installed(using package managment of
Brian> course).
Manoj> What do you mean by version? I have 6 kernel images
Manoj
> "Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> VMWare I know nothing about. Are you supposed to recompile
Raul> it every time you change kernel versions? And does it
Raul> really not let you specify -I/usr/local/src/linux/include/ ?
Yes and no. :) There is a default i
> "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes:
Ben> Just for examples, I cite VMWare and OSS as two packages that
Ben> fail miserably on a Debian system because it's so different.
Joseph> The way OSS does it is broken anyway. I can't speak fro
Joseph> vmware.
Yes, t
> "Brian" == Brian Servis <[EMAIL PROTECTED]> writes:
Brian> Just curious how Debian is going to stand on the FHS
Brian> requirements for /usr/include kernel headers in section
Brian> 6.1.5 of the FHS? Is the practice of including known good
Brian> headers with libc6-dev going
> "Miquel" == Miquel van Smoorenburg <[EMAIL PROTECTED]> writes:
Miquel> It sounds more like you want a rc.local style directory,
Miquel> not rc.boot.
Miquel> But what is so difficult about update-rc.d? It's only one
Miquel> line in the postinst .. (and one in prerm)
It's not
> "Miquel" == Miquel van Smoorenburg <[EMAIL PROTECTED]> writes:
Miquel> Well, what's wrong is that there is no certain order of
Miquel> execution defined for the scripts in /etc/rc.boot. Then we
Miquel> got things like /etc/rc.boot/0serial and such, so why not
Miquel> use a sy
I'm going through my old bug reports, and I remembered people
telling me /etc/rc.boot/ is obsolete. But I just went to look at
the new policy (I assume 3.0.0.0 is the latest) and it has the same
old stuff about /etc/rc.boot/ :
(snip)
3.3.4 Boot-time initialization
There is another directory, /e
> "Richard" == Richard Stallman <[EMAIL PROTECTED]> writes:
Richard> I think that the best basic policy is that a package can
Richard> go in `main' if it doesn't require any non-free software
Richard> *on your machine*. Making use of non-free software on
Richard> another machi
> "Scott" == Scott K Ellis <[EMAIL PROTECTED]> writes:
Scott> Yep, it also implys nosuid (maybe noexec as well, but i'm
Scott> not positive)
I hope we ship with Perl 5.005_03 or later, then, because if we don't,
we've just put a big old security hole in the system, as older Perls
don'
> "Enrique" == Enrique Zanardi <[EMAIL PROTECTED]> writes:
Enrique> /dev/fd0 /floppy auto defaults,user,noauto 0 0
Enrique> /dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 0
These look good. I assume that 'user' still obeys the permissions
on the devices themselves, but allows an
of rc.boot is obsolete
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Message-Id: <[EMAIL PROTECTED]>
*- Ben Gertzfield wrote about "Re: Bug#32441: nethack: the use of rc.boot i=
s obsolete
> "Hamish" == Hamish Moffatt <[EMAIL PROTECTED]> writes:
Ben> The XFree86 sources as shipped use ~/.Xresources as the
Ben> default place for user X resources. Every other Unix in the
Ben> world uses the file ~/.Xdefaults. I think we should support
Ben> both by default, not just
> "Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:
Branden> Well, the startx.cpp that ships with the XFree86 sources
Branden> sets userresources to ~/.Xresources. If those guys use
Branden> ~/.Xdefaults, then they've changed it.
Branden> This sounds like the kind of
> "Jason" == Jason Gunthorpe <[EMAIL PROTECTED]> writes:
Ben> I believe this has been discussed before, and the general
Ben> consensus was that dpkg is slow enough already as it is;
Ben> generating md5sums on the fly, while it would be a great
Ben> thing to have as an option, p
> "Jason" == Jason Gunthorpe <[EMAIL PROTECTED]> writes:
Joey> What do people here think about changing policy to
Joey> reccommend that packages contain a md5sums file? The md5sums
Joey> files have been around for over a year now, there is a well
Joey> defined file format, tool
Adam, this is excellent work. This has been sorely needing a write-up
for some time now. Thanks!
Ben
--
Brought to you by the letters L and Q and the number 11.
"The spiraling shape will make you go insane!" -- They Might Be Giants
Debian GNU/Linux -- where do you want to go tomorrow? http://www
>>>>> "Richard" == Richard Braakman <[EMAIL PROTECTED]> writes:
Richard> Ben Gertzfield wrote:
Richard> So I was thinking it'd be nice to warn developers of
Richard> shared library packages that they should have the -dev
Richard>
> "Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes:
Adam> Well, rather than making an exemption, the point is pretty
Adam> simple:
Adam> If a package depends on a specific version of a -dev or
Adam> lib* pacakge, that dependancy should be reflected in the
Adam> control
> "James" == James Troup <[EMAIL PROTECTED]> writes:
Ben> I've noticed that it's not policy for shared libraries'
Ben> libblah-dev and libblah-dbg packages to depend on libblah1
Ben> (=${Source-Version}) of the main library.
James> BTW: this isn't quite right; the source versi
I've noticed that it's not policy for shared libraries' libblah-dev
and libblah-dbg packages to depend on libblah1 (=${Source-Version})
of the main library.
I was bitten by this when I forgot to manually keep the dependancy
up-to-date in debian/control, which allowed people to, say, install a
new
> "Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
Ian> Does anyone have a piece of code that can automatically undo
Ian> SuperCite ?
SuperCite can undo SuperCite :) I don't know about automatically.
--
Brought to you by the letters G and K and the number 3.
"He's kissing Christian.
Well, congratulations to the first birth of the new standards process!
:)
Ben
--
Brought to you by the letters Q and G and the number 19.
"He's kissing Christian.. and it's making you die." -- that dog.
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUC
> "Marcus" == Marcus Brinkmann <[EMAIL PROTECTED]> writes:
Ben> I think our ongoing problem of finding an appropriate license
Ben> for documentation has been solved.
Ben>
Ben> On slashdot.org today, an article about the OpenContent
Ben> License (OPL, pronounced 'opal') was
I think our ongoing problem of finding an appropriate license for
documentation has been solved.
On slashdot.org today, an article about the OpenContent License (OPL,
pronounced 'opal') was posted.
The license looks perfect for our use. I've included it at the
bottom of this message.
It specifie
> "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes:
Neale> The temporary logo license expired 21 days ago. I'm not a
Neale> developer so I can't do it, but could someone please write
Neale> up a proposal for a permanent license? This is getting
Neale> ridiculous.
Jos
> "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes:
Joseph> [Please remove debian-devel when replying]
Joseph> On Mon, Sep 21, 1998 at 12:00:30PM -0600, Neale Pickett
Joseph> wrote:
Neale> The temporary logo license expired 21 days ago. I'm not a
Neale> developer so
>From discussions on IRC and from lintian errors, I can see that files
in /var/lib/games/ (generally high-score and save-game files) should
not be conffiles, but instead should be managed through the
postinst and removed in the postrm if we're doing a purge.
This makes a lot of sense.
However, I
> "Jason" == Jason Gunthorpe <[EMAIL PROTECTED]> writes:
Jason> I'm certain we don't need another alias for this list :>
Jason> Use [EMAIL PROTECTED] or [EMAIL PROTECTED] All
Jason> of the documentation uses [EMAIL PROTECTED]
Okay. To verify, we want to:
* Change the 'Maintaine
Jason> list.
Jason> I guess .19 will do this? (Ben?)
James has said it might be better to have an alias outside of
[EMAIL PROTECTED]; perhaps [EMAIL PROTECTED], or
[EMAIL PROTECTED] would be better..
--
Brought to you by the letters F and M and the number 11.
"* denotes
y 768 bits, I believe. Do I have to revoke this key and
create a new one now?
--
Brought to you by the letters R and X and the number 14.
"You have my pills!" -- Grampa Simpson
Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public
PGP key. I'm on FurryMU
me; I just know there's policy for elisp
packages, perl library packages, etcetera..
perhaps we should follow the libperl-blah convention for naming
Perl packages, and use libgimp-blah?
--
Brought to you by the letters H and V and the number 8.
"You have my pills!" -- Grampa Simpson
Ben Ger
lib/gimp/0.99/ -- I'm assuming this
will change to 1.0 when 1.0 is released.
Is it kosher to just have any package dump a plug-in into this
directory?
--
Brought to you by the letters S and Q and the number 6.
"You should be glad you don't have diaper rash. Mah Jongg." -- The C
#x27;s certainly
a pain in the butt to have to do this by hand every time a new
upstream version comes out..
--
Brought to you by the letters A and I and the number 16.
"Ha ha! I have evaded you with the aid of these pasty white mints!"
Ben Gertzfield <http://www.imsa.edu/~wilwonka/>
mes> end up with all kinds of nastiness with .dpkg-tmp files as
James> .so links and in ld.so's cache and other fun stuff[1].
James> [1] Hi Ben.
eep! I didn't do it! You can't prove anything!
--
Brought to you by the letters X and D and the number 19.
"I wanna
I remove the newer libtool from the upstream source and replace
it with the current libtool in the Debian distribution?
--
Brought to you by the letters Y and A and the number 12.
"Hello! We are only joke. It is funny enough." -- Orz, SCII
Ben Gertzfield <http://www.imsa.edu/~wilwonk
e to close these bugs, or
come up with some sort of policy (why, though?) about them.
--
Brought to you by the letters P and O and the number 15.
"The spiraling shape will make you go insane!" -- They Might Be Giants
Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for m
at GIMP
crashes without informative information (it's because it needs the
fonts and can't get them). If I leave the dependancy in, I get bug
reports from people who use xfs.
What's the solution here?
--
Brought to you by the letters K and O and the number 10.
"It makes my nippl
and other fun things.
--
Brought to you by the letters K and U and the number 9.
"Mom! Dad! Don't touch it, it's evil!" *POOF* -- Time Bandits
Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public
PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
hould be the libc5
Gergely> one) and optionally libforms0.86-altdev ;)
Okay, I've made them this way. :) Thanks for enlightening me.
--
Brought to you by the letters F and V and the number 3.
"Hello! We are only joke. It is funny enough." -- Orz, SCII
Ben Gertzfield <http://www
er.
Ben
--
Brought to you by the letters D and B and the number 14.
"Oh, all right, Uncle Ulty REALLY wants you to do his portrait." -- FF6
Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public
PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
27;t find the proper place in the policy manual that talks about
how to do it correctly, however. If someone could clue me in as to how
to do it right..
--
Brought to you by the letters I and T and the number 16.
"You forgot Uranus." "Goodnight everybody!" -- Ya
compressed files.
Anyone familiar with their patent?
Ben
--
Brought to you by the letters Y and X and the number 8.
"You should be glad you don't have diaper rash. Mah Jongg." -- The Critic
Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public
PGP key. I&#
51 matches
Mail list logo
