On 24 November 2014 at 05:08, Bill Allombert wrote:
> Thanks for your clarification. Is the attached patch OK ?
That looks good to me.
--
Brian May
Package: debian-policy
Severity: normal
The httpd-wsgi virtual name was added in response to #588497.
However, as per the following email:
https://lists.debian.org/debian-devel/2014/09/msg00719.html
"WSGI is an API, not a wire protocol. The Python version of the WSGI
server would also be the Py
; packages? Comments and copyright notices don't look like a real
> advantage to me.
>
Copyright notices belong in /usr/share/doc/package/copyright.
--
Brian May
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
lso a really bad precedent to set for other shared library packages
>which are dlopen()d.
Just for the record, this is bad not just because policy days it is bad
;-), but it prevents installing multiple versions of the library at the
same time.
--
Brian May <[EMAIL PROTECTED]>
d most serious problem,
there is only one tar.gz file for all architectures...
Perhaps the autobuilders should (if they don't do so already) check
that nothing in the source code has changed from the downloaded *.dsc,
*.tar.gz and *.diff.gz files?
(might be a problem for autobuilt rebuilt files, eg. autoconf and
automake, though)
--
Brian May <[EMAIL PROTECTED]>
ust one bug I have seen with packages that use debconf.
Another one is packages that insist on asking the questions twice:
once after apt has downloaded the package and once for after the
package has been unpacked. Sometime I probably should test some
suspect packages for this problem and file bug re
et in touch
Chris> with the httpd maintainers, and make sure they're ready and
Chris> willing to do this, and (if no one has objected by that
Chris> time) we should be go.
--
Brian May <[EMAIL PROTECTED]>
very readable to a human reader, but at
least any program that understands quoted-printable (including mutt)
can display it properly.
This was GnuPG signed, with OpenPGP non-compliant options removed, and
the signature came out looking OK.
--
Brian May <[EMAIL PROTECTED]>
iance you have to remove this option.
escape-from-lines
which is really stupid IMHO, as it means the message gets converted
for mbox format before it is even sent.
--
Brian May <[EMAIL PROTECTED]>
use the package first, which requires reading the documentation
first, which has not even been installed yet.
--
Brian May <[EMAIL PROTECTED]>
t> the README.Debian or other documentation, such as the
Scott> release notes.
Strongly disagree for a number of reasons. Remember, that
README.Debian isn't available for pre-configuration.
--
Brian May <[EMAIL PROTECTED]>
e version), (current version),
(newly released version), (beta version), (alpha version), or
(dangerous version) instead.
--
Brian May <[EMAIL PROTECTED]>
sted CD, run said trusted dpkg, to
Adam> calculate the md5sums of the files.
Which requires scanning each and every *.deb file, in order to
calculate the expected checksums of each individual file. What is the
performance lost here?
--
Brian May <[EMAIL PROTECTED]>
be done via a
>> (low-priority) debconf message.
Anthony> ...or an "echo". Seconded.
Only one concern: such a message should *never* get displayed if you
are using devfs...
--
Brian May <[EMAIL PROTECTED]>
ld either:
a) not print any messages when creating devices or
b) only print messages if ! devfs.
Otherwise, seeing messages that devices are being created on a devfs
system can only cause confusion.
--
Brian May <[EMAIL PROTECTED]>
ode or not.
Does framebuffer solve this?
--
Brian May <[EMAIL PROTECTED]>
ultiple libraries at the same time, if
the major number is the same, but the minor number is different.
(please send followups to the most appropriate policy bug report).
--
Brian May <[EMAIL PROTECTED]>
X" will
Robbe> just do nothing on the Hurd.
I fail to see:
What is wrong with the current practise on the Hurd, where ldconfig
is a do nothing program?
How does disabling task 1 (creating the links) help for the Hurd?
--
Brian May <[EMAIL PROTECTED]>
ensure that all programs work with
UTF-8. Ideally, this should be done for woody (but may not be
possible).
How do tools (eg. debconf) know what coding set to use when reading a
file (eg. templates file)? Or, is ISO-8859-1 assumed?
--
Brian May <[EMAIL PROTECTED]>
for when the package uses the "Replaces: " header...
--
Brian May <[EMAIL PROTECTED]>
inux (i386, ppc, m68k, alpha) and hurd (i386,
Brian> ppc, m68k) - but not hurd(alpha)
This is a topic that we have been discussing on and off in the
debian-hurd mailing list. Please see the archives, especially for
earlier this year.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> upload to stable == upload to stable
Brian> + source only upload to testing
Brian> + source only upload to unstable
Sorry to followup straight away on my previous post, however I
is an earlier
version. Same with testing.
You could also argue that the initial upload should be source only
to. That way you wont encounter bugs dues to maintainers accidently
building using unstable libraries.
--
Brian May <[EMAIL PROTECTED]>
should be compiled against
unstable, I would suggest fixing source only uploads first (that way
maintainers don't have to run unstable).
--
Brian May <[EMAIL PROTECTED]>
is part of
>>> the base system and not part of the MTA package.
I think the proposal was for the MUA, not the MTA (which would have to
be configured separately).
--
Brian May <[EMAIL PROTECTED]>
ssed by sed,
m4, or whatever), so the paths will always be correctly set
(especially for packages based on autoconf).
--
Brian May <[EMAIL PROTECTED]>
on ftp
would work with ncftp, for instance.
Somebody suggested to use ftp-client-traditional (or was that
traditional-ftp-client?) instead.
--
Brian May <[EMAIL PROTECTED]>
get automatically. The makefiles I have
seen will automatically execute the build target if the stamp file has
not been created.
(is this required by policy?)
--
Brian May <[EMAIL PROTECTED]>
nstalled... and
Alexander> you get a chicken-and-egg problem. Ouch.
You don't consider make to be an interpreted language?
--
Brian May <[EMAIL PROTECTED]>
iles
"config.guess", "config.sub" and "ltmain.sh". (some earlier versions
also have "ltconfig").
--
Brian May <[EMAIL PROTECTED]>
they are simply uploaded to unstable.
(consider the time required to move packages from experimental to
unstable after the freeze - I suspect that would have to be
significant, too).
Same stages as proposed, just different names.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Julian" == Julian Gilbey <[EMAIL PROTECTED]> writes:
Julian> On Fri, Feb 16, 2001 at 02:04:24PM +1100, Brian May wrote:
>> What is the benefit of this new frozen stage, instead of just
>> freezing the testing stage?
Julian>
n> Possibility 2: Your possibility 1, so that there are four
Julian> distributions during the freeze; testing continues to
Julian> carefully follow unstable, and frozen is, well ... frozen.
What is the benefit of this new frozen stage, instead of just freezing
the testing stage?
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> Previously Brian May wrote:
>> ...and why is an empty diff file, for a small (if not tiny)
>> number of packages such a problem?
Wichert> It's impractica
d have no need for
No. Just recently, I uploaded a native version of Heimdal (0.3d-5), when
the previous version was non-native (0.3d-4). Note: same upstream
version. No problems.
When I wanted to fix the problem, I uploaded Heimdal 0.3d-7 with upstream
source again (same copy), and never had any problems.
--
Brian May <[EMAIL PROTECTED]>
but packages generally
should not[1] be native if upstream author != maintainer.
(do we need to include anything on uploading a native package if the
last one was non-native and vice versa? eg. only allow it if the
version number (excluding debian revision) changes?)
Note:
[1] must not?
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Massimo" == Massimo Dal Zotto <[EMAIL PROTECTED]> writes:
Massimo> chattr +i ?
Interesting point. Programs/packages shouldn't rely on it working all
the time though, as I doubt it is (yet) supported on NFS, resierfs,
Hurd, etc.
--
Brian May <[EMAIL PROTECTED]>
stems. It must be
s> something like "these users/groups may write, and these may
s> read", but I don't know if they have something for the
s> setuid/segid thing...
Yes. I was wondering the same thing myself...
--
Brian May <[EMAIL PROTECTED]>
lem.
(...depends on how they are implemented).
--
Brian May <[EMAIL PROTECTED]>
4096 Feb 6 14:30 ./
This is standard Unix semantics.
Sooo... your proposal might get a little gain in security, but not
much, since the owner of the file can just turn on write permission
anyway.
--
Brian May <[EMAIL PROTECTED]>
ht be used when it shouldn't, but that
doesn't mean that some applications exist. IMHO all packages that are
specific to Debian (eg. use on other platforms is not supported) fall
into this category.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> On Mon, Feb 05, 2001 at 01:13:44PM +1100, Brian May
Herbert> wrote:
>> As such, I recommend that we change this bug title to:
>>
>> "dynamic creation
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> For everyone concerned: versions of libtool already support
Brian> this. eg. cvs version of libtool 1.4, and cvs tree for
Brian> libtool 1.3x (not sure if includes the latest
bug?
Wasted effort.
However, if maintainers are happy to accept this risk, I have no
problem with it.
--
Brian May <[EMAIL PROTECTED]>
to fix, just release a new upstream version.
Some people don't want to do worry about this, so these people can use
native format, and not have to worry about the extra diff file.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> foo-dev (2.1) /usr/include/foo.h /usr/lib/libfoo.so ->
Brian> libfoo.so.2.1
For everyone concerned: versions of libtool already support this.
eg. cvs version of libtool 1.4, and cvs tre
t to the
original bug report by Ian, so I didn't discuss it earlier.
Then again, I now realize that *.la files conflicting is a totally
separate issue, so I probably should have bought it up at a different
time.
--
Brian May <[EMAIL PROTECTED]>
Manoj> I see no need to introduce a whole new syntax for
Manoj> packages to accomplish this; we already have a means for
Manoj> decoupling the packaing code from the rest of the code.
See my latter message - I am not disagreeing with you.
--
Brian May <[EMAIL PROTECTED]>
.la and *.so files into a separate
package (I think the *.so sym-link is required too)[1].
That way, multiple versions of the library don't conflict and can be
installed at the same time, but normal users don't have to install the
-dev package either.
--
Brian May <[EMAIL PROTECTED]>
ff-topic into a flame war over "why does libtool do it
this way?" please.
This thread&bug report is on a specific proposal to allow compiling of
programs against one version of the library, while another version is
used for run-time. (same major version).
--
Brian May <[EMAIL PROTECTED]>
rique> Seems fine to me. That would allow the issue with broken
Henrique> non-native uploads to be fixed, and allow binary uploads
Henrique> of native packages using a debian revision number, if
Henrique> one wants to.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Henrique" == Henrique M Holschuh <[EMAIL PROTECTED]> writes:
Henrique> On Sun, 04 Feb 2001, Brian May wrote:
>> Although for native packages (which should not already have a
>> Debian revision number), -# should probably be appended
refer to the newest library, this is so things will
work correctly for link-time and run-time.
(probably some dh_* helper program would do this stuff automatically
so individual maintainers do not have to worry.)
--
Brian May <[EMAIL PROTECTED]>
sts) works and
Henrique> causes no source headaches for the vast majority of the
Henrique> packages.
Agreed.
Although for native packages (which should not already have a Debian
revision number), -# should probably be appended instead, so the
version stays the same.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> However, this exposes other issues, since the version of
Brian> *.la required depends on the version of the library
Brian> required, however only one copy of the *.la file can be
he package for a
particular architecture without hacking around with the version
number.
I would recommend this solution.
--
Brian May <[EMAIL PROTECTED]>
de stable will install every
How big would the depends: line get? then again, don't answer that...
Matthew> single package listed therein. Does anyone else have a
Matthew> problem with that?
I suppose that is meant to be the difference between
apt-get upgrade stable
and
apt-get install stable
?
--
Brian May <[EMAIL PROTECTED]>
system with unstable packages?
Have you looked at the new features in the new version of apt (CVS
version, or has that been released now?). They might already address
the problems you want to fix.
--
Brian May <[EMAIL PROTECTED]>
be confusing the package a is compiled based on an older version
of libfoo-dev, but executed with the newer version of libfoo1,
but still it should be easy to realize what is happening (just stick
to the previous rule).
*.la files will be a problem, as explained in my other message.
--
Brian May <[EMAIL PROTECTED]>
andard libtool behaviour (although I haven't
double checked) although libtool has uses different terms.
For the 2nd case, you can't just increment the major version, this
will break existing software, even though the library is
backward compatible.
I hope that clears up some confusion over version numbers (which
admittedly I am only just beginning to understand myself).
--
Brian May <[EMAIL PROTECTED]>
o? You can't just hide it from ldconfig, can
Marcelo> you?
Don't you mean libbar1? Now you have got me confused.
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
I previously misunderstood Herbert's proposal, here it is again (I
hope it is accurate this time...).
foo2.0 (2.0) /usr/lib/libfoo.so.2.0 (actual library)
Provides: foo2 version 2.0
foo2.1 (2.1) /u
uld be
done privately too, if Debian doesn't want to do it).
--
Brian May <[EMAIL PROTECTED]>
already
Henrique> bloated */lib and the archive. Such doubling is NOT
Henrique> acceptable (IMHO, but it seems that at least BenC agrees
Henrique> with me).
hard-link support will not help any more then sym-links currently do.
--
Brian May <[EMAIL PROTECTED]>
n. foo-dev is independent of foo2.
People might complain about foo2 (do we really need a package
containing nothing but a symlink?), but personally I like the idea
(compare with task packages which are empty).
I think it is simple to understand, and adds little overhead (just
foo2). Packages wor
progu and progs.
(how do you ensure that all -dev packages installed are from stable,
and you haven't missed any?)
Ok, Thanks, I think I understand now.
Note:
[1] I hope nobody disputes why this version depends is required...
(things might get awkward if it was forgotten).
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Seth" == Seth Arnold <[EMAIL PROTECTED]> writes:
Seth> How does this work with the glibc mess I seem to recall from
Seth> about a month ago?
I don't recall the details - can somebody please give me a URL?
--
Brian May <[EMAIL PROTECTED]>
atible,
despite having the same major version. If this is really the case, I
think the potential exists to break a lot more then just the build
process.
Please give me a real life example of why distinguishing libraries
solely by their major version number is not good enough...
--
Brian May <[EMAIL PROTECTED]>
it
too, but I guess that might break things. However, I guess the fact
that which knows it is not an executable clearly shows that the shell
should be able to work it out for tab completion, too).
--
Brian May <[EMAIL PROTECTED]>
it.
Sometimes you can close a bug straight away - eg. if the bug was filed
in mistake, or a non-bug, etc. You don't always want to wait until the
next package release just so you can close a bug.
--
Brian May <[EMAIL PROTECTED]>
#x27;t have to scan the entire BTS
history for the package to find out if the problem has either been
reported before.
Otherwise, you will end up with the full documentation appearing in
the Changelog, which is not the intended purpose of the Changelog.
--
Brian May <[EMAIL PROTECTED]>
to heimdal) that will automatically obtain the
diff required to update automake and autoconf files (heimdal requires
the CVS version of automake and autoconf in project/experimental, so I
probably can't depend on this package for woody).
--
Brian May <[EMAIL PROTECTED]>
-cvzf debian.tar.gz debian [5]
xyz-0.0/debian.tar.gz[6]
xyz-0.0/xyz_0.0-1.deb
xyz-0.0/xyz_0.0-1.diff.gz
xyz-0.0/xyz_0.0-1_i386.changes
xyz-0.0/xyz_0.0-1_i386.dsc
xyz-0.0/xyz_0.0.orig.tar.gz
You say that this isn't meant to change the source code format, but
[2], [4] and [5] seem to be saying otherwise.
--
Brian May <[EMAIL PROTECTED]>
). Anybody
wanting to discuss this should probably open up a new bug report
against debian-policy.
--
Brian May <[EMAIL PROTECTED]>
are different between
operating systems, such as different interpretations of the FHS.
Note:
[1] Perhaps an possible alternative would be if alien could
automatically insert the correct copyright when converting the
package? This needs some reliable way of detecting the copyright
though (grep /usr
not required.
Note:
[1] argghh! what should I call the "compiler" (person doing the
compilation) so it doesn't get confused with the C compiler?
--
Brian May <[EMAIL PROTECTED]>
>>>>> "Bernd" == Bernd Eckenfels <[EMAIL PROTECTED]> writes:
Bernd> On Sun, Nov 19, 2000 at 01:02:42PM +1100, Brian May wrote:
>> telnet-server Any telnet server
Bernd> So dou u want to make the task-secure-system package
Bernd> c
Package: debian-policy
>>>>> "jae" == Jürgen A Erhard <[EMAIL PROTECTED]> writes:
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> (now I wonder when I created rsh-server and ftp-server, why
Brian> I didn
hat uses a feature
straight away (if it is already installed) or takes some other action
if the feature is not installed yet (eg ignoring the request or
logging the request for latter in case the feature is installed).
Such a mechanism could also be used as a base for update-*
--
Brian May <[EMAIL PROTECTED]>
ide how much
detailed information he wants to see, and to do this the program needs
to be able to determine the priority of various messages.
ie. similar to why priorities are needed for debconf.
--
Brian May <[EMAIL PROTECTED]>
if dpkg used a similar method to report "directory not empty"
warnings, the GUI could even have an option that allows you to browse
the directory, and see if there really is anything important there.
Now, this E-Mail is going to open up a new can of worms ;-)
--
Brian May <[EMAIL PROTECTED]>
ge --timeout 60seconds --message "Trying to start
package..." --command /etc/init.d/package start
so, if for instance a daemon has a history of hanging, something can
be done to make it easier to debug?
--
Brian May <[EMAIL PROTECTED]>
ld do with some refinement, but I think you get the
general idea.
--
Brian May <[EMAIL PROTECTED]>
ilar call to one of the above. (ultimately, for the most general
solution, dpkg should support it).
--
Brian May <[EMAIL PROTECTED]>
preview
Package: acroread
Provides: pdf-viewer, postscript-preview
No package currently depends/requires/suggests it. pdf-preview is not
used at all. Programs like gv (which can write postscript) and dvips
seem to be missing.
IMHO, the name "-preview" is misleading.
--
Brian May <[EMAIL PROTECTED]>
the commands would be standardised across every shell, in
such a way that a global config file (or directory) could be used to
setup defaults.
--
Brian May <[EMAIL PROTECTED]>
h systems might be essential, so that
people can get use to the completely different way in which things are
done, which-out being "forced" into the change.
I can't say much more then that right now until I get a chance to play
around with some of this stuff myself.
Perhaps enhancing suidregister to support capabilities might be a good
first step.
--
Brian May <[EMAIL PROTECTED]>
I do not understand how
processes are initially assigned capabilities.
Please consider posting replies to debian-devel.
--
Brian May <[EMAIL PROTECTED]>
ASL module that does ssh like RSA
based authentication. No re-compilation required. Not everybody likes
Kerberos, and this would be the best way to satisfy everyone.
SASL support in Debian would mean we could support both
implementations of Kerberos 5, and just use a different SASL module
for each one.
However, now the subject has changed considerable from what is in the
subject line...
--
Brian May <[EMAIL PROTECTED]>
proposal.
PS: I will be away next week, so may be delayed in responding.
--
Brian May <[EMAIL PROTECTED]>
never
Joey> designed to do.
I think something needs to be done to address this issue.
Yes, you can force dpkg to always use the old file, but then
this will break applications which require the new file to
be installed.
--
Brian May <[EMAIL PROTECTED]>
I think it is the license we
are discussing here, not the copyright...
However, why stop at the license? Perhaps the same thing could be
done with other information, eg relevant web pages, email addresses,
etc.
--
Brian May <[EMAIL PROTECTED]>
n woody does not contain any crypto
Ben> modules. AFA TLS, did you link against libssl09? If not, you
Ben> have nothing to worry about.
I believe that is now libsasl...
(just to make sure there are no copies of my old package still lying
around...)
--
Brian May <[EMAIL PROTECTED]>
but this only applies
(AFAIK) for console and telnet logins, and not ssh.
Perhaps, with PAM, something better could be done (if I said why I
think this is insufficient though, we would be heading way off topic
for this thread).
What is an LDA?
--
Brian May <[EMAIL PROTECTED]>
.
Hence all you really need for an /etc/mailsystem config file would be:
mboxformat=mbox|maildir
location=~/Maildir|~/Mailbox|/var/spool/mail/$USER
I don't think the other options are required or needed. However, some
way to override these defaults on a per user baisis is important
(eg in case a user needs a non-default location for some reason).
--
Brian May <[EMAIL PROTECTED]>
on how to compile the kernel and/or the
required module. I suggest a http address, and not a local file, and
it is highly probably it will need to be updated as new users find
more problems).
--
Brian May <[EMAIL PROTECTED]>
on... (also, it could be argued
that this is not the best solution). While I seem to remember that
alternatives to the dpkg -l command exist, the dpkg -l command is the
only one I ever remember when I need it.
--
Brian May <[EMAIL PROTECTED]>
nstalling a package in the wrong spot, then it
is my fault, and only my fault (although, depending on what happened,
I might complain to the upstream author...).
If a package that adheres to Debian policy messes things up, then it
is the fault of the Debian policy.
--
Brian May <[EMAIL PROTECTED]>
lisp files
so a system administrator could find all packages that use
/usr/local/lib by a simple grep (or egrep) command.
(not tested)
egrep '^/usr/local/lib' /usr/share/doc/*/local
which IMHO is far more useful then the current mechanism anyway.
There are probably one million plus one ways to enhance on the above
command.
--
Brian May <[EMAIL PROTECTED]>
retitle 58759 [ACCEPTED] Request for new virtual packages: rsh-client and
telnet-client
thanks
ARGGHH!!! How come I can never get this right first go :-(
--
Brian May <[EMAIL PROTECTED]>
1 - 100 of 154 matches
Mail list logo
