Re: idea for project machines
On Mon, Mar 27, 2006 at 03:28:42PM +0530, Ganesan Rajagopal wrote: > How about providing this access only in a Xen guest? We have vserver enabled kernels for some arches in the archive. Bastian -- I have never understood the female capacity to avoid a direct answer to any question. -- Spock, "This Side of Paradise", stardate 3417.3 signature.asc Description: Digital signature
Re: Deciding new arm EABI port name
Riku Voipio wrote:
On Thu, Mar 30, 2006 at 10:31:58AM +0100, Martin Guy wrote:
dpkg-architecture in dpkg 1.13 returns "os-cpu", where os and arch are
grabbed from ostable and cputable.
Er... are we talking about different meanings of the word "architecture" here?
s/os and arch/os and cpu/
This discussion is about the new equivalent to "arm", "i386", "m68k"
and so on, as used in the file names for Debian binary packages that
contain machine-dependent object code.
Do you mean that all the existing architectures (i386, arm, powerpc)
have to change to linux-i386, linux-powerpc etc? That makes no sense
at all.
Or that eabi/gnueabi is an operating system?
"arm", "i386", "m68k" are shorthands. Please have a look at
dpkg-architecture sources:
if ($os eq "linux") {
return $cpu;
} else {
return "$os-$cpu";
}
Next, have a look at ostable and cputable files. After that I think it
should be clear why current dpkg-architecture limits our choices.
Pardon me, but to me it looks outright stupid to let development be
constrained by some perl script. Can't you just change it to allow more
useful variations? Why can't we have Debian distributions tuned to our
(embedded) devices?
I would want to install a Debian distribution compiled with
-march=armv5te -mtune=xscale -Wa,-mcpu=xscale on a newer iPAQ
and another one compiled with -march=armv4 -mtune=strongarm1100
on my older iPAQ.
On machines with/out FPU or VFP this is even a requirement that you
compile everything with the same options such as -msoft-float and
-mfpu=vfp.
Attaching patches for -softfloat and -uclibc... With these patches,
this is what my local dpkg-architecture says (DEB_BUILD lines removed):
$ dpkg-architecture -aarm
DEB_HOST_ARCH=arm
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=arm
DEB_HOST_GNU_CPU=arm
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=arm-linux-gnu
$ dpkg-architecture -aarm-softfloat
DEB_HOST_ARCH=arm-softfloat
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=arm-softfloat
DEB_HOST_GNU_CPU=arm-softfloat
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=arm-softfloat-linux-gnu
$ dpkg-architecture -aarm-uclibc
DEB_HOST_ARCH=arm-uclibc
DEB_HOST_ARCH_OS=linux-uclibc
DEB_HOST_ARCH_CPU=arm
DEB_HOST_GNU_CPU=arm
DEB_HOST_GNU_SYSTEM=linux-uclibc
DEB_HOST_GNU_TYPE=arm-linux-uclibc
Idem ditto for i386, mipsel... hurd-i386 and friends are not affected:
$ dpkg-architecture -ahurd-i386
DEB_HOST_ARCH=hurd-i386
DEB_HOST_ARCH_OS=hurd
DEB_HOST_ARCH_CPU=i386
DEB_HOST_GNU_CPU=i486
DEB_HOST_GNU_SYSTEM=gnu
DEB_HOST_GNU_TYPE=i486-gnu
I would expect arm-eabi to look like this:
$ dpkg-architecture -aarm-eabi
DEB_HOST_ARCH=arm-eabi
DEB_HOST_ARCH_OS=linux-eabi
DEB_HOST_ARCH_CPU=arm
DEB_HOST_GNU_CPU=arm
DEB_HOST_GNU_SYSTEM=linux-gnu-eabi
DEB_HOST_GNU_TYPE=arm-linux-gnu-eabi
--- dpkg-1.13.16/debian/archtable 2006-03-23 17:10:47.0 +0100
+++ dpkg-1.13.16-my.0/debian/archtable 2006-03-23 17:07:03.0 +0100
@@ -15,6 +15,7 @@
ia64-linux-gnu ia64
alpha-linux-gnualpha
arm-linux-gnu arm
+arm-softfloat-linux-gnuarm-softfloat
hppa-linux-gnu hppa
m68k-linux-gnu m68k
mips-linux-gnu mips
--- dpkg-1.13.16/cputable 2006-01-20 04:34:28.0 +0100
+++ dpkg-1.13.16-my.0/cputable 2006-03-23 17:07:15.0 +0100
@@ -19,6 +19,7 @@
amd64 x86_64 x86_64
armeb armeb arm.*b
armarm arm.*
+arm-softfloat arm-softfloat arm.*
hppa hppahppa.*
m32r m32rm32r
m68k m68km68k
--- dpkg-1.13.16/scripts/dpkg-architecture.pl 2006-03-23 17:10:47.0
+0100
+++ dpkg-1.13.16-my.0/scripts/dpkg-architecture.pl 2006-03-23
17:08:35.0 +0100
@@ -55,14 +55,16 @@
sub split_debian {
local ($_) = @_;
+return ("linux",$_) if exists ($cputable{$_});
+
if (/^([^-]*)-([^-]*)-(.*)/) {
- return ($3, join("-", $1, $2));
+ return (join("-","linux",$3), join("-", $1, $2)) if
exists($cputable{join("-",$1,$2)});
}
if (/^(hurd)-(.*)/) {
- return ($1, $2);
+ return ($1, $2) if exists($cputable{$2});
}
if (/^([^-]*)-(.*)/) {
- return (join("-", "linux", $2), $1);
+ return (join("-", "linux", $2), $1) if exists($cputable{$1});
} else {
return ("linux", $_);
}
@@ -79,6 +81,9 @@
sub split_gnu {
local ($_) = @_;
+/^([^-]*)-([^-]*)-(.*)/;
+return (join("-",$1, $2), $3) if exists($cputable{join("-",$1,$2)});
+
/^([^-]*)-(.*)/;
return ($1, $2);
}
--- dpkg-1.13.16/debian/archtable 2006-01-18 09:30:03.0 +0100
+++ dpkg-1.13.16-my.0/debian/archtable 2006-03-11 16:10:10.0 +0100
@@ -24,3 +24,6 @@
sh-linux-gnu sh
sparc-linux-gnusparc
i486-gnu hurd-
Re: Bug#358695: ITP: latex-utils -- utilities for LaTeX/xfig
On 3/29/06, Henning Makholm <[EMAIL PROTECTED]> wrote: > Scripsit Vincent Danjean <[EMAIL PROTECTED]> > > > Package name : latex-compile > > Description : easy compiling of complexe (and simple) LaTeX documents > > This package provides several tools that aim to simplify the > > compilation of LaTeX documents : > > I'm marginally unhappy with the word "compile" here. LaTeX programs > are not being _compiled_; they are being _executed_ and their output > are page descriptions. I'd go for something like "build" or "builder". That's somewhere between compiling and just scripts. Or may be "make" or "maker" as it's using Makefile fragments. -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
Re: Some packages need a new maintainer
retitle 312078 ITA: ht -- Viewer/editor/analyser (mostly) for executables owner 312078 ! thanks Hi! * Alexander Schmehl <[EMAIL PROTECTED]> [060329 20:51]: > * Florian Ernst <[EMAIL PROTECTED]> [060329 20:00]: > > The following packages are up for adoption, if you want them > > please just take them; [..] > > ht - Viewer/editor/analyser (mostly) for executables > And I use that from time to time, so I'm willing to take it; but after > reading #312078 I'm unsure if I'm knowledgeable enough for that myself. Since I haven't heard from you, yet (and I'm about to leave again for a couple of days to a no-net area), and since Luk Claes volunteered to me Co-Maintainer, we are taking it. Upload will follow, when I return (which should be Sunday evening). Frank, I would welcome feedback from you, what the remaining issues you mention in your RFA are. I didn't saw any bug reports or new upstream releases (and upstream doesn't seem to release a new release every hour...) Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: Bug#357703: udev breaks syslog
On Wed, 29 Mar 2006, Marc Haber wrote: > On Tue, 28 Mar 2006 18:15:27 +0200, [EMAIL PROTECTED] (Marco d'Itri) wrote: > >On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote: > >> How about restarting syslog (or it's equivalent) after relocating the > >> old /dev? glibc already has infrastructure for restarting services on > >> upgrade, maybe udev can borrow that. > >Harder than it looks. There are multiple syslog daemons, how can the > >package know which one is installed and needs to be restarted? > > One more sign that we need out syslog daemon packages to cooperate > better. Which is kind of hard if not impossible considering the > current state of sysklogd packaging, which is unfortunately still the > default. A common interface for adding additional locations of logging sockets would also be nice. So that packages could tell the local syslogd to please create a socket in /chroots/bind/dev/log and then chroot by default. Cheers, Peter PS: and I want a pony too, please -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ITP: kmplayer -- media player for KDE
Package: wnpp Severity: wishlist Owner: Fathi Boudra <[EMAIL PROTECTED]> * Package name: kmplayer Version : 0.9.2-pre3 Upstream Author : Koos Vriezen <[EMAIL PROTECTED]> * URL : http://kmplayer.kde.org/ * License : GPL-2 Description : media player for KDE KMPlayer, a simple frontend for MPlayer/Xine/ffmpeg/ffserver/VDR. It can play DVD/VCD movies, from file or url and from a video device. If setup right, KMPlayer can embed inside konqueror. Which means if you click on a movie file, the movie is played inside konqueror. It can also embed inside khtml, enabling movie playback inside a html page. Movie recording using mencoder (part of the mplayer package). No video during recording, but you can always open a new window and play it there. Broadcasting, http streaming, by using ffserver/ffmpeg. For TV sources, you need v4lctl (part of the xawtv package). cheers, Fathi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dh_installtex just for calling mktexlsr?
[ Uh, do we really need debian-devel here? ] Frank Küster <[EMAIL PROTECTED]> wrote: > masters of dh_installtex, That's Norbert. ;-) >> The drawback is that update-updmap, update-language and update-fmtutil >> are called whereas my package does not need them (and that mktexlsr is >> called without any argument, so all dirs are checked). Just a data point: running update-updmap, update-language and update-fmtutil is very cheap (contrary to running e.g. updmap-sys). > I'm not familiar with dh_installtex code - would it be easy to add an > option, so that only the mktexlsr call is introduced into maintainer > scripts? Should we provide an option to add directories to the mktexlsr > call, so that only the directories where files have been installed are > updated? This could speed up things considerably, and there's no need You mean add these directories manually, right? Because the general case is not that simple. It is not sufficient to run mktexlsr on directories where files are installed, because files can also be moved to a different place under TEXMFMAIN, or simply removed, and these need to disappear from ls-R. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#357703: udev breaks syslog
Peter Palfrader <[EMAIL PROTECTED]> writes: > A common interface for adding additional locations of logging sockets > would also be nice. So that packages could tell the local syslogd to > please create a socket in /chroots/bind/dev/log and then chroot by > default. In this case, one way of doing this for chroots would be for syslog packages to provide a file e.g. /etc/schroot/setup.d/50syslog which would create the socket on the fly when the chroot is used. This does require using schroot to access chroots, however. Regards, Roger -- Roger Leigh Printing on GNU/Linux? http://gutenprint.sourceforge.net/ Debian GNU/Linuxhttp://www.debian.org/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. pgpPs4heq1gGG.pgp Description: PGP signature
Re: Bug#357703: udev breaks syslog
On Tuesday 28 March 2006 18:15, Marco d'Itri wrote: > On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote: > > How about restarting syslog (or it's equivalent) after relocating the > > old /dev? glibc already has infrastructure for restarting services on > > upgrade, maybe udev can borrow that. > > Harder than it looks. There are multiple syslog daemons, how can the > package know which one is installed and needs to be restarted? Look in /proc and find out which process has the log socket open? If that process belongs to one of the packaged syslog implementations (there aren't that many!) restart it. (Taking advantage of the fact that IIRC processes printing log messages open and close the socket for every messages, so looking a few times until abs(the intersection of all processes on that socket) == 1 should be safe. -- vbi -- Protect your privacy - encrypt your email: http://fortytwo.ch/gpg/intro pgp6EGgdiVySL.pgp Description: PGP signature
Re: Bug#357703: udev breaks syslog
On 3/30/06, Adrian von Bidder <[EMAIL PROTECTED]> wrote: > On Tuesday 28 March 2006 18:15, Marco d'Itri wrote: > > On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote: > > > How about restarting syslog (or it's equivalent) after relocating the > > > old /dev? glibc already has infrastructure for restarting services on > > > upgrade, maybe udev can borrow that. > > > > Harder than it looks. There are multiple syslog daemons, how can the > > package know which one is installed and needs to be restarted? > > Look in /proc and find out which process has the log socket open? If that Can you depend on /proc being available?
Re: Bug#357703: udev breaks syslog
On Tuesday 28 March 2006 18:15, Marco d'Itri wrote: On Mar 28, Gabor Gombas <[EMAIL PROTECTED]> wrote: How about restarting syslog (or it's equivalent) after relocating the old /dev? glibc already has infrastructure for restarting services on upgrade, maybe udev can borrow that. Harder than it looks. There are multiple syslog daemons, how can the package know which one is installed and needs to be restarted? Look in /proc and find out which process has the log socket open? If that process belongs to one of the packaged syslog implementations (there aren't that many!) restart it. That much is easy, but how do you turn a process ID into a script that can be invoke-rc.d'd? Well, I suppose one could hard code in a list of packaged syslog daemons and the names of their init scripts, but that's pretty nasty. IMO this is just foolishness caused by the hacks necessary to start udev immediatly after the package has been installed, rather than after the system is rebooted. -- vbi -- Sam Morris http://robots.org.uk/ PGP key id 5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#357703: udev breaks syslog
On Thu, 2006-03-30 at 18:22 +0200, Adrian von Bidder wrote: > > (Taking advantage of the fact that IIRC processes printing log messages open > and close the socket for every messages, so looking a few times until > abs(the intersection of all processes on that socket) == 1 should be safe. It's not that obvious. There are function (at least in C) to open a socket to syslog (openlog). If a program use this, then it will keep the connection open till the end of the program. (Or till the next closelog call. :) ) In my destop system there are about 6 stable connection into /dev/log. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#357703: udev breaks syslog
Sam Morris <[EMAIL PROTECTED]> writes: > > That much is easy, but how do you turn a process ID into a script that > can be invoke-rc.d'd? Make it part of the Debian spec? define a known script name (logging-daemon) that must exist in /etc/init.d/ and can be a symlink to another one. submit a small patch to each logging daemon to add/remove this link when the package is installed/removed? -- rich walker | Shadow Robot Company | [EMAIL PROTECTED] technical director 251 Liverpool Road | need a Hand? London N1 1LX | +UK 20 7700 2487 www.shadow.org.uk/products/newhand.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: You've been subscribed to a list at Zinester.com
please help me by a car
Re: Bug#357703: udev breaks syslog
On Mar 30, Peter Palfrader <[EMAIL PROTECTED]> wrote: > A common interface for adding additional locations of logging sockets > would also be nice. So that packages could tell the local syslogd to > please create a socket in /chroots/bind/dev/log and then chroot by > default. *Many* years ago I opened a sysklogd bug with a patch to do this, but I recently closed it because it was ignored. -- ciao, Marco signature.asc Description: Digital signature
Re: Bug#357703: udev breaks syslog
On Thu, Mar 30, 2006 at 06:22:23PM +0100, Rich Walker wrote: > Sam Morris <[EMAIL PROTECTED]> writes: > > > > > That much is easy, but how do you turn a process ID into a script that > > can be invoke-rc.d'd? > > Make it part of the Debian spec? > > define a known script name (logging-daemon) that must exist in > /etc/init.d/ and can be a symlink to another one. > > submit a small patch to each logging daemon to add/remove this link when > the package is installed/removed? Sounds ugly to me. Here's another suggestion: start-stop-daemon is in a /very/ good position to know which PID belongs to which initscript. Patch it so that it writes the PIDs to some "database"[1] somewhere; then patch invoke-rc.d to be able to use that "database". Probably best to do that through some well-defined interface, rather than having invoke-rc.d directly reading out that db, though. [1] "database", as in, "some way to store PIDs and which initscript they belong to", not necessarily as in "libdb", and absolutely not as in "SQL-engine with data files". -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Maintainers Guide
Hello Anthony, Anthony DeRobertis <[EMAIL PROTECTED]> wrote: > Jeremy Stanley wrote: >>This has to include a copyright year, also. >> >> ...and following additional discussion, the resolution is: >> >>After considering the suggestion, I have decided to close this >>bug. >> > The year really should be included. What if upstream does not provide this information? I'm helper of the jed-extra package that includes a collection of scripts for the editor jed. They are collected at http://jedmodes.sourceforge.net/. Many of them do not include any information about the year anybody did work on them. What to do in this case? Can we pack them or is it a risk? Regards, Jörg. -- "UNIX was not designed to stop people from doing stupid things, because that would also stop them from doing clever things." -- Doug Gwyn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DebConf6: Final call for registrations / reconfirmations
On 3/31/06, Joerg Jaspert <[EMAIL PROTECTED]> wrote: > Lets repeat that, as this is important: You *NEED* to confirm that you > attend DebConf before the 3th April 2006, 23:59:59 UTC or YOU MUST PAY > YOURSELF. The 3th of April? andrew -- Andrew Donnellan http://andrewdonnellan.com http://ajdlinux.blogspot.com Jabber - [EMAIL PROTECTED] --- Member of Linux Australia - http://linux.org.au Debian user - http://debian.org Get free rewards - http://ezyrewards.com/?id=23484 OpenNIC user - http://www.opennic.unrated.net
Bug#360163: ITP: libannexlib-ocaml -- Library of miscellaneous OCaml code
Package: wnpp Severity: wishlist Owner: Ewan Mellor <[EMAIL PROTECTED]> * Package name: libannexlib-ocaml Version : 0.13.2 Upstream Author : Shawn Wagner <[EMAIL PROTECTED]> * URL : http://raevnos.pennmush.org/code/annexlib * License : LGPL Description : Library of miscellaneous OCaml code Annexlib contains miscellaneous and generally useful routines that are not in the OCaml standard library. Highlights include wildcard globbing, lots of string searching and manipulation routines, locale support, ~user-style path expansion, and more. Since it includes some native stubs, this library will be packaged as two Debian packages -- libannexlib-ocaml and libannexlib-ocaml-dev. Proposed packages are available at http://www.ewanmellor.org.uk/annexlib.html. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#360163: ITP: libannexlib-ocaml -- Library of miscellaneous OCaml code
On Fri, Mar 31, 2006 at 01:19:28AM +0100, Ewan Mellor wrote: > * Package name: libannexlib-ocaml Please X-Debbugs-Cc debian-ocaml-maint for ITP related to OCaml. That said, I think the package name should reflect upstream's being "annexlib". The binary name can be those you proporse. Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Re: Bug#357703: udev breaks syslog
On Thu, Mar 30, 2006 at 10:51:03PM +0200, Wouter Verhelst <[EMAIL PROTECTED]> wrote: > On Thu, Mar 30, 2006 at 06:22:23PM +0100, Rich Walker wrote: > > Sam Morris <[EMAIL PROTECTED]> writes: > > > > > > > > That much is easy, but how do you turn a process ID into a script that > > > can be invoke-rc.d'd? > > > > Make it part of the Debian spec? > > > > define a known script name (logging-daemon) that must exist in > > /etc/init.d/ and can be a symlink to another one. > > > > submit a small patch to each logging daemon to add/remove this link when > > the package is installed/removed? > > Sounds ugly to me. > > Here's another suggestion: start-stop-daemon is in a /very/ good > position to know which PID belongs to which initscript. Patch it so that > it writes the PIDs to some "database"[1] somewhere; then patch > invoke-rc.d to be able to use that "database". Probably best to do that > through some well-defined interface, rather than having invoke-rc.d > directly reading out that db, though. It already does store the pid if called with the --pidfile option. Just make it mandatory. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
