Re: RFS: gremind -- Simple reminder program for GNOME
I demand that Sebastian Krause may or may not have written... [snip] Being a Tk application tkremind is naturally ugly. When I tried out tkremind I didn't really like it. If this is because of aliased fonts, then installing tk8.5 and, if you can't get rid of 8.4, setting the 'wish' alternative appropriately will help: # update-alternatives --config wish [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. I am not young enough to know everything. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: ljcrop
I'm looking for a sponsor for ljcrop, a graphical front end for the JPEG-cropping functionality of jpegtran. (This would close ITP bug 521315.) The package would be lintian-clean but for what I think is a false positive. lintian (in testing) complains about a dependency on wish, but that can't be right: Depends: wish | tk8.5, libtk-img, libjpeg-progs The package can be found in http://tartarus.org/~ds/pkg/. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Let's keep the pound sterling I know what is around the corner. I just don't know where the corner is. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ljcrop
I demand that Tristan Greaves may or may not have written...
Darren Salt wrote:
The package would be lintian-clean but for what I think is a false
positive. lintian (in testing) complains about a dependency on wish, but
that can't be right:
Depends: wish | tk8.5, libtk-img, libjpeg-progs
http://lintian.debian.org/tags/virtual-package-depends-without-real-package-depends.html
You have in your debian/control file:
Depends: wish | tk8.5, libtk-img, libjpeg-progs
As per the warning note, put the real package _first_ ('wish' is the
virtual here), i.e.:
Depends: tk8.5 | wish, libtk-img, libjpeg-progs
Fixed reuploaded.
--
| Darren Salt| linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy less and make it last longer. INDUSTRY CAUSES GLOBAL WARMING.
That wouldn't be cricket.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: evilvte (updated package)
I demand that gregor herrmann may or may not have written... [snip] In this case VTE based super lightweight terminal emulator or maybe lightweight terminal emulator based on VTE might work. The latter's fine, IMO, but the former should be VTE-based [snip] -- | Darren Salt| linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | Army | + Output less CO2 = avoid boiling weather. TIME IS RUNNING OUT *FAST*. Any given program costs more and takes longer. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: unable to build gdb from source
I demand that Kamaraju S Kusumanchi may or may not have written... Can some one tell me what I am doing wrong here? I am unable to build gdb from source on a machine running sid. I did $apt-get source gdb $cd gdb-6.6.dfsg/ $ dpkg-buildpackage -us -uc -rfakeroot The build log is attached in this email. [...] Any ideas on why this is happening? Should I file a bug? From your build log: rmdir /home/raju/downloaded packages source/gdb-6.6.dfsg/objdir rmdir: /home/raju/downloaded: No such file or directory rmdir: packages: No such file or directory rmdir: source/gdb-6.6.dfsg/objdir: No such file or directory Your problem is a combination of unquoted strings and spaces in file/directory names; specifically, downloaded packages source. Renaming that directory so that its name contains no spaces (actually, no characters which have special meaning to the shell) will be enough to work around the problem. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Let's keep the pound sterling Take my advice, I'm not using it right now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: Kenta Cho's games
I demand that Miriam Ruiz may or may not have written... [snip] I finally finished all of Kenta Cho's games, and it is time to find sponsorship for them. Some of them are already in the archive, but there are new debian releases, so those should be easier: [snip] These games, or at least the two which I've had a quick look at, use GL_LINE_SMOOTH which, for r300, is currently implemented in software. This causes these games to be unplayably slow due to their reliance on line graphics. Currently, the solution is to use driconf to globally disable low-impact fallbacks. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Let's keep the pound sterling You do not have mail. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: uniconvertor
I demand that Andreas Wenning may or may not have written... On Fri, 2008-03-14 at 01:20 -0200, Mauro Lizaur wrote: [snip] The binary name is uniconv, I think it should be uniconvertor The problem is, that inkscape directly uses the name uniconv. If the executable is renamed to uniconvertor, inkscape won't pick its existence up. So should I change the package name to uniconvertor, and make uniconv also work (via symlink)? Or should I just keep the name as uniconv. If it should be changed, I think that I'd choose to symlink it, file a bug against inkscape, then (after lenny is released) kill the symlink and have the package break or conflict with older (presently current) inkscape. I'd probably go with what a DD says, though. :-) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 = avoid massive flooding.TIME IS RUNNING OUT *FAST*. Drop that pickle! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to build packages from tarballs without makefiles
I demand that Carlo Segre may or may not have written... On Sun, 9 Apr 2006, David Liontooth wrote: [snip] I need a bit more help -- where do I add them to rules? CFLAGS = -Wall -g Can I add the Link with line to give CFLAGS = -Wall -g -lGLU -lGL -lXmu -lXext -lX11 [snip] BTW, a library package may not be the best thing to learn packaging. A package which produces a single executable is much easier. ... and, since it's a library, you *must* add -fPIC to CFLAGS. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Buy less and make it last longer. INDUSTRY CAUSES GLOBAL WARMING. Error 216: Tagline out of paper -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mini-dinstall, repository signing and apt-get authentication
I demand that Neil Williams may or may not have written...
[snip]
I'm now trying a brute force method:
$ cp /home/neil/Release.amd64 ./Release
$ md5sum Packages Release
$ md5sum Packages.gz Release
$ echo SHA1: ./Release
$ sha1sum Packages ./Release
$ sha1sum Packages.gz ./Release
then signing the Release file to create Release.gpg
What I use for my repository is attached. (Licence is GPL = v2.)
--
| Darren Salt| linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| Say NO to UK ID cards. http://www.no2id.net/
I will never lie to me.
#! /bin/sh
i=unstable
ARCH=amd64
exec Release
cat EOF
Archive: $i
Origin: www.youmustbejoking.demon.co.uk
Label: ymbj
Suite: $i
Codename: $i-ds
EOF
echo Date: `date --rfc-822 --utc`
cat EOF
Architectures: $ARCH
Components: main contrib non-free
Description: ymbj Debian packages archive ($i)
EOF
find * -name Packages -o -name Packages.gz -o -name Packages.bz2 \
-o -name Sources -o -name Sources.gz -o -name Sources.bz2 | sort |
perl -we '
use Digest::MD5;
use Digest::SHA1;
sub write_sum ($@)
{
my $hashclass = shift @_;
$hashclass = eval Digest::$hashclass;
foreach my $file (@_)
{
my $fd;
open $fd, $file or die $^E;
my $hash = $hashclass-new;
$hash-addfile ($fd);
my @stat = stat ($file) or die $^E;
printf %s %8s %s\n, $hash-hexdigest, $stat[7], $file;
undef $hash;
close $fd;
}
}
my @args;
while () { chomp; push @args, $_; }
exit 0 unless @args;
print MD5Sum:\n;
write_sum (MD5, @args);
print SHA1:\n;
write_sum (SHA1, @args);'
signature.asc
Description: PGP signature
Re: binary files in diff
I demand that Frank Gevaerts may or may not have written... I need to add a binary file (a png icon) to my package. What is the best way to do this, since the normal .diff generation does not support this ? UUcode seems to be the usual way (needs sharutils). -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL. The gent who wakes up and finds himself a success hasn't been asleep. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Build-Depends-Indep and build target
I demand that Joachim Reichel may or may not have written...
The underlying problem is that build-arch/indep are not mandatory and thus
building must call the build target.
Any chance that this will be changed for lenny? If build-arch and
build-indep are optional and there is no reliable way to find out whether
these targets exist [...]
This, perhaps?
if make -f debian/rules -n build-arch; then
make -f debian/rules build-arch
else
make -f debian/rules build
fi
Then there's the problem of which targets (in the upstream makefile) should
be run from build-{arch,indep}. I don't see any obvious targets for splitting
up the building in this way in a typical automake-generated makefile (I
checked both xine-lib and gxine), which would appear to make
build-{arch,indep} pointless in this case, and would also provide an
explanation of why these targets are not mandatory.
[snip]
--
| Darren Salt| linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Output less CO2 = avoid boiling weather. TIME IS RUNNING OUT *FAST*.
Mind your own business, Spock. I'm sick of your halfbreed interference.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie question about compiler warnings.
I demand that Neil Williams may or may not have written... On Sun, 14 Jan 2007 12:54:17 -0800 Brandon Barnes [EMAIL PROTECTED] wrote: Are we allowed to disable compiler warnings? What is the preferred method, if the code is fine, and would require a huge overhaul to fix? Warnings are only a problem if -Werror is also set. If upstream don't use -Werror, the warnings may actually be useful in debugging the package and/or FTBFS bugs from porters. Agreed. In particular, I've found gcc's -Wformat=2 and -Wformat-security to be of use. (Fixing -Wformat-security warnings does tend to cause other warnings, but that's good.) As the humble opinion of one DD, hiding any output that does not stop the build is a BadIdea(TM) in most cases - as well as being unnecessary. For C, -Wno-format-zero-length is probably a good idea if using -Wformat (at least, it is for gxine where the warnings which it suppresses are noise). (Which is why I don't mind commented dh_ lines in rules but that's a different thread.) I'd remove those which I'm sufficiently sure will never be needed for $PACKAGE. [snip] If so, should I disable them in Makefile, or debian/rules? No. I would recommend leaving them in - you may be grateful for the evidence in times to come. Warnings are issued for a reason - until upstream fix the code, I'd always recommend to leave the warning in place. Certain ones should be left in anyway, IMO. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Kill all extremists! All is well that ends well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: generating patches for debian packages
I demand that Kamaraju S Kusumanchi may or may not have written... I am looking for some tricks for generating patches for the debian source packages. Let's say I download the source of a package foo apt-get source foo Now I change somefiles inside foo. How can I easily generate a patch so that I can send it to bts/maintainer etc.,? Currently what I do is unpack the source again into another temp directory and then use diff -r and then delete the temp directory. But this is time consuming. Is there any easy way? Are there any books which deal with practical issues such as these? You could add a new changelog entry (use dch, or do it manually), then $ debuild $ interdiff -zp1 ../foo_1.2-3.diff.gz ../foo_1.2-3+my-patches.diff.gz | filterdiff -x \*/debian/rules ../foo.patch (Doing this requires devscripts and patchutils.) If the source uses tools such as dpatch or quilt then that may not work quite so well - you could use the same tools or you could hack it a bit: patch the source (debian/rules patch or debian/rules apply-patches or something like that), configure it (debian/rules configure) then, BEFORE doing anything else, make a copy of the source tree (hard-linking files is good, so long as your text editor breaks links when saving). Diffing is suddenly easier. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Lobby friends, family, business, government.WE'RE KILLING THE PLANET. Do not merely believe in miracles, rely on them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: mercurial-buildpackage
I'm looking for a sponsor for mercurial-buildpackage, which I'm taking over. (Co-maintainers would be appreciated.) * Package name: mercurial-buildpackage Version : 0.10 Upstream Author : Jens Peter Secher jpsec...@gmail.com, Darren Salt li...@youmustbejoking.demon.co.uk * URL : http://anonscm.debian.org/hg/collab-maint/mercurial-buildpackage * License : ISC Section : devel It builds one binary package: mercurial-buildpackage - Suite to maintain Debian packages in Mercurial repository To access further information about this package, you should visit: http://mentors.debian.net/package/mercurial-buildpackage Alternatively, you can download the package with dget: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-buildpackage/mercurial-buildpackage_0.10.dsc Reviewing can also be done via the repository (URL is above). I suspect that that may be more convenient for seeing what changes I've made. -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | http://www.asciiribbon.org/ When working towards a solution, it helps to know the answer. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/526ca2f65c%li...@youmustbejoking.demon.co.uk
Bug#661633: RFS: mercurial-buildpackage
Package: sponsorship-requests I'm looking for a sponsor for mercurial-buildpackage, which I'm taking over. (Co-maintainers would be appreciated.) * Package name: mercurial-buildpackage Version : 0.10 Upstream Author : Jens Peter Secher jpsec...@gmail.com, Darren Salt li...@youmustbejoking.demon.co.uk * URL : http://anonscm.debian.org/hg/collab-maint/mercurial-buildpackage * License : ISC Section : devel It builds one binary package: mercurial-buildpackage - Suite to maintain Debian packages in Mercurial repository To access further information about this package, you should visit: http://mentors.debian.net/package/mercurial-buildpackage Alternatively, you can download the package with dget: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-buildpackage/mercurial-buildpackage_0.10.dsc Reviewing can also be done via the repository (URL is above). I suspect that that may be more convenient for seeing what changes I've made. -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | http://www.asciiribbon.org/ Blackberries are red when they are green. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/526e266720%li...@youmustbejoking.demon.co.uk
Re: Use of DM-Upload-Allowed field
I demand that Sandro Tosi may or may not have written... [snip] the DMUA flag should be set by the sponsor (or by the sponsoree after a request for the sponsor), At the request of the sponsor, surely. [snip] -- | Darren Salt| linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | Army | + They're after you... There are two ways to write bug-free code; only the third way works. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51009e153c%li...@youmustbejoking.demon.co.uk
Re: RFS: gnome-media-player
I demand that Bilal Akhtar may or may not have written...
I am looking for a sponsor for the following package. The source package
dsc can be found on
http://expatsinksa.com/gnome-media-player_0.1.2-1.dsc . I had to host it
on my own website since mentors.d.n is broken.
* Package name: gnome-media-player
Version : 0.1.2
Upstream Author : Michael Lamothe michael.lamo...@gmail.com
[snip]
WRT xine-lib, you should be making use of xine-list-1.1 (or xine-list-1.2, if
you happen to be using libxine-dev from experimental). This is used to ensure
that the MIME types list for your desktop file is correct; see also gxine
source (specifically, debian/gxine.postinst.in and debian/gxine.postrm, and
the corresponding rules in debian/rules).
You need to depend on ${xine-x:Depends} (I want to get rid of libxine1's
dependencies on libxine1-x and libxine1-console) and, once the next xine-lib
upload is done, you should also be able to recommend ${xine-ffmpeg:Depends}
instead of libxine1-ffmpeg.
To do this, you need to run dh_xine prior to running dh_gencontrol. This is
not automated with dh 7 (actually, not yet; I have local changes which should
allow this).
As things stand, just dh_xine will do; after the next xine-lib upload,
dh_xine x ffmpeg will generate the substvars referenced above (for all
packages created from your source package; debhelper's -p option applies).
(Don't ask me about how to do this with cdbs...)
--
| Darren Salt| linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | back!
| URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys)
Having the fewest wants, I am nearest to the gods.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/511b3ffc70%li...@youmustbejoking.demon.co.uk
Re: Advice sought regarding binaries in upstream source
I demand that Andree Leidenfrost may or may not have written... I am the co-maintainer for packages mindi and mondo which had bugs #233606 and #233605 filed a while ago. These bugs where about the packages containing binaries in the upstream source. This was true, the binaries have been removed since and the bugs closed. However, this means that we are currently not distributing the pristine upstream sources of mindi and mondo, which I am not overly happy with. (I am highlighting this fact by adding sub-versions to the upstream versions in the package names.) I doubt that this would be considered to be a problem, and may well be a Good Thing: the source takes up slightly less space in the archive, and there's no possibility of upstream's binaries being used during the build process. [snip] Should the answer be that the binaries indeed have to be removed from the upstream source in the orig.tar.gz file, I would also very much like to know whether my current approach of appending a sub-version to the upstream version number is approriate (example: 2.03 - 2.03.1). Bad idea. What if there's an upstream 2.03.1? -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Insanity is just a state of mind. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reorganizando el wiki y la lista de blogs
I demand that Adrian von Bidder may or may not have written... On Tuesday 25 January 2005 20.00, Antonio Ognio wrote: Saludos, Please respect that debian-mentors is an english mailing list. babelfishized: Er... turned into a Babel fish? ;-) [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Oh, sarge too... A bird in the hand is worth what it will bring. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
I demand that martin f krafft may or may not have written... also sprach Margarita Manterola [EMAIL PROTECTED] [2005.04.12. +0200]: It makes sense for software developers to have their own ./debian directory so that they can use debian/rules binary to compile and test their software while developing it. Huh? Why not just use ./Makefile? I use both in gxine: debian/rules to get a known good version of the package built and installed, then Makefile (with modified source) to build a modified executable which can use the installed files. What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. That's a matter for the Debian maintainer and upstream. All that I can say is that I've marked bugs as fixed in the Debian changelog without there being any complaint... -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Always the dullness of the fool is the whetstone of the wits. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: gxine 0.4.4 (source NMU)
Re. http://sourceforge.net/mailarchive/message.php?msg_id=11562029, I've prepared an NMU of gxine which fixes the RC bug and several other bugs which are present in 0.4.1. There are a few small packaging changes which shouldn't cause any problems; in particular, gnome-xine is dropped since it's not present outside sid (within Debian). gxine-0.4.4.tar.gz: URL:http://prdownloads.sourceforge.net/xine/gxine-0.4.4.tar.gz?download (yes, I just released it...) .diff.gz, .dsc: URL:http://zap.tartarus.org/~ds/debian/. I can also prepare a .diff.gz and .dsc for an NMU of xine-lib (libxine1, libxine-dev) if it would help. An upload is needed to close a security hole (see URL:http://xinehq.de/index.php/security/XSA-2004-8; bug 305343). -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Don't overuse exclamation marks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gxine 0.4.4 (source NMU)
I demand that Matthew Palmer may or may not have written... On Tue, Apr 26, 2005 at 10:28:03PM +0100, Darren Salt wrote: Re. http://sourceforge.net/mailarchive/message.php?msg_id=11562029, I've prepared an NMU of gxine which fixes the RC bug and several other bugs which are present in 0.4.1. There are a few small packaging changes which shouldn't cause any problems; in particular, gnome-xine is dropped since it's not present outside sid (within Debian). Sponsoring an NMU is a really, really bad idea. It kind of mucks up the chain of control more than a little bit. I'd suggest that you make appropriate notations in the bug logs for the various bugs that you close with the new upstream release, and then notify the maintainer directly, Most of it is in CVS (tag gxine-0_4_4-release); the bugs mentioned there are already tagged fixed-upstream. I've forgotten to mention in the changelog that bug 305106 is to be closed - I'll close this manually if necessary - and bug 295184, IMO, shouldn't be closed yet because only the build-dep part has been applied to 0.4.4. I applied the rest of it to CVS HEAD only. as well as the QA (debian-qa@lists.debian.org) and security ([EMAIL PROTECTED]) teams (because of #305343) That affects xine-lib. The relevant bug here is 289412/295344, which isn't security-critical; this message is CCed accordingly. (I'll see any responses if they're in -mentors or CCed to me.) and let them take care of it. Whether it's uploaded with my name or a DD's name in the changelog entry for 0.4.4, I don't particularly mind. It's probably easiest to start with my .diff.gz or the debian directory from CVS, though. -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html OS/2? Where's the other half? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: splay upload anyone?
I demand that John Hedges may or may not have written... [snip] I'd appreciate an upload ... are you willing, despite my stubborness? Good luck with it. Nobody bothered to upload gxine before the freeze... I propose that the next release is called hell rather than etch ;-\ -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html The good news: Micro$oft to be broken up. The bad news: into only two pieces. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: z80asm, assembler for the Zilog Z80 microprocessor
I demand that Bas Wijnen may or may not have written... Erik Schanze wrote: [snip] Seriously, I think you should improve your long description to explain to an (unexperienced) user what this package is for. What can you do with this assembler? Why should you install it? What are the results of the programms (e.g. machine-code) for? How about this one?: The Z80 microprocessor is used in old home computers, such as the ZX-spectrum and MSX, and in several newer devices, such as the TI-83 graphical calculator and the GameBoy. That's ZX Spectrum... can this assembler output tape image (TAP or TZX) files for use with an emulator? (I could also add ZX80, ZX81, TS1000, TS1500, TS2068, TC2048, TC2068...) And, AFAIK, the Gameboy's CPU isn't exactly Z80 - it's missing at least the IX and IY registers and the corresponding instructions. [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | We've got Shearer, you haven't Pieces of nine! Pieces of nine! ...sorry, parroty error... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to deal with #307726 ?
I demand that Carlos Z.F. Liu may or may not have written... In Bug#307726, some users reported that the Close button in the About dialog is noneffective. It only happened when users were using gtk 2.6.1 or 2.6.2. The problem would be fixed after they upgrade libgtk2.0-0 to version 2.6.4. I read the source code of leafpad, and didn't think it's leafpad's fault. How can I deal with it? Should I reassign the bugreport to libgtk2.0-0? In the next release of leafpad, should I specify libgtk2.0-0 (= 2.6.4) manually? AFAICS, you may as well just close the bug: libgtk2.0-0 2.6.4 is in sarge. -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling A clean, neat, desk is a sign of a very sick mind. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: latex2html makes twice table captions
I demand that Mauro Darida may or may not have written... On Tuesday 17 May 2005 20:44, Sven Mueller wrote: Could you give us a (as minimal as possible) .tex file (and possibly the output .html you get) to reproduce this? Sure, they are attached below. [snip] Hmm... arm PDA (Sharp Zaurus), Acorn Archimedes For the Archimedes, that'd be arm26. You mean Acorn Risc PC and Iyonix - and, at least on Acorn hardware, StrongARM is required, or at least it was when I last checked. -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC How come we never talk any more? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: performance tip for the package development stage
I demand that Shachar Shemesh may or may not have written... I'm sorry if this is well known. I haven't seen it anywhere, and I thought I'd share it with everybody. During the initial package development stage, there is a lot of repeated compilation of the same package over and over again. [... summary: use ccache] Alternatively, try to alter the source so that you don't need multiple compilations. (This worked for vdr.) -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | We've got Shearer, you haven't This tagline intentionally left blank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian architectures
I demand that Mauro Darida may or may not have written... On Saturday 21 May 2005 16:21, Darren Salt wrote: Hmm... arm PDA (Sharp Zaurus), Acorn Archimedes (What are those hard spaces doing there? I didn't put them there...) For the Archimedes, that'd be arm26. Thank you for your feedback. Could you please elaborate more? I was talking about debian architectures for Sarge, and I don't know any arm26 architecture. Am I correct? Yes, which is why it's wrong to refer to the older Acorn ARM-based machines - it may give the impression that they're supported. In .../dists/sarge/main/installer-arm/current/images/ (see your local mirror), there are directories riscpc and riscstation, below each of which is one kernel. While the RiscStation kernel should work on any RiscStation machine (memory says that they all use the ARM7500FE), I can't say the same for the Risc PC kernel - is it built for ARM610, ARM700/ARM710 or SA110? (I'd guess SA110.) [snip] -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html Great on toast, scones and arteries. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian architectures
I demand that Mauro Darida may or may not have written... On Monday 23 May 2005 19:30, Darren Salt wrote: RiscStation machine (memory says that they all use the ARM7500FE), I can't say the same for the Risc PC kernel - is it built for ARM610, ARM700/ARM710 or SA110? (I'd guess SA110.) So, what do you suggest ? a. remove acorn archimedes b. replace acorn archimedes with RiscStation machine (any common model?) c. ? c: Replace with RiscStation machines (any model) and with the Risc PC. According to the Risc PC configuration file in kernel-image-2.4.27-arm, ARM610, ARM710 (presumably, also ARM700) and SA110 are supported. -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html Stop that! It's silly! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new upstream Cogito conflicts with GNU Interactive Tools
I demand that Junichi Uekawa may or may not have written... [snip] My recommended action is: 1. tell them /usr/bin/git name is already taken, and we're renaming it to piggy I'd say sum, but that's already taken too. ;-) -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling Those who in quarrels interpose must often wipe a bloody nose. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lxmusserv, yadex: current maintainers still interested in these packages?
Both lxmusserv and yadex have some outstanding bugs and have not seen any maintainer activity for... quite some time now. lxmusserv has some patches in the BTS which fix relatively minor bugs and allow it to work properly here (emu10k1) without hitting timing issues due to incomplete or buggy OSS sequencer emulation in ALSA. (Note that I'm using stock kernel.org kernels here.) yadex is seriously out of date, and even if 1.7.0 isn't uploaded (I only just noticed this version yesterday, and haven't yet filed a bug on it), it still needs to be compiled with g++ 3.3. I have updated/patched versions in my apt archive (see .sig) which deal with all of the bugs except for no. 199282. If the maintainers don't respond, then I'll adjust my packages for NMU or take-over, filing bugs as appropriate. (Sponsorship will be needed.) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html Can't learn to do it well? Learn to enjoy doing it badly!
Re: packaging newbie...: .svn directories / perldoc -- manpage
I demand that Colin Watson may or may not have written... On Tue, Jul 06, 2004 at 08:50:38AM +0200, Adrian 'Dagurashibanipal' von Bidder wrote: (i) I have the package in subversion, so the .svn directories are included in the diff. Can I avoid this easily? $ grep DEBUILD_DPKG_BUILDPACKAGE_OPTS .devscripts DEBUILD_DPKG_BUILDPACKAGE_OPTS=-i'(?:^|/).*~$|(?:^|/)\..*\.swp|DEADJOE|(?:/CVS|/RCS|/\.svn|/\.deps)(?:$|/)' -ICVS -I.svn -uc -us Hmm, extra bits... autom4te.cache? [snip] -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling Barney of Borg: I assimilate you; you assimilate me...
Re: Putting accented characters in manpages?
I demand that Romain Beauxis may or may not have written...
Le Jeudi 6 Octobre 2005 06:57, Rogério Brito a écrit :
W: pfb2t1c2pfb: manpage-has-errors-from-man
usr/share/man/man1/pfb2t1c.1.gz /tmp/zmanpkICfH:25: warning: can't find
numbered character 243
. It is probably caused by the special characters in your name, which
were put unencoded into the man page.
I had the same issue for a manpage too.
I discovered that you can put those caracters in a special encoding like I
did:
.SH AUTHOR
This manual page was written by Lo\[:i]c Le Guyader
[EMAIL PROTECTED],
for the Debian GNU/Linux system (but may be used by others).
It works with the command line man, but not with kde's man viewer. And I
can't remeber where I found this... sorry
groff_char(7) seems likely. I find that \(zz works (for arbitrary zz given in
\[zz]) with man and xman, although I have no idea whether this works in KDE's
man viewer.
For character 243, you want \['o] or \('o.
--
| Darren Salt | nr. Ashington, | linux (or ds) at
| sarge,| Northumberland | youmustbejoking
| RISC OS | Toon Army | demon co uk Say NO to UK ID cards
| http://www.no2id.net/
A phaser on stun is like a day without orange juice.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpatch upstream source
I demand that François-Denis Gonthier may or may not have written... On 2 November 2005 09:13, Junichi Uekawa wrote: I'm working on some big changes for the new upstream of the erlang packages. The biggest change is that the package is now fully using dpatch, *but*, basing myself on some other package I've seen (coreutils for example), I've put the compressed upstream right in the package. It is extracted using a dpatch scriptlet. Is it okay to do that, for one thing? Out of interest, I would be interested in the advantages of having a tarball like that. oh, and it totally helps to keep _all_ changes in check. If I change anything outside dpatch-edit-patch, it'll be gone at the next cleaning. It's a bit of a hassle but since I always feared that a change I've made to the upstream source could end up silently in the diff and break the build on some platforms, I think it's a good thing to force myself to go through dpatch. Use lsdiff (in patchutils) to find out if a patch is in the wrong place: $ lsdiff -z ../foo_1.2.3-4.diff.gz | grep -v /debian/ You can move the offending patches into a file in debian/patches/ with filterdiff and dpatch-edit-patch: $ filterdiff -zx '*/debian/*' ../foo_1.2.3-4.diff.gz | patch -Rp1 $ dpatch-edit-patch 99_bar $ filterdiff -zx '*/debian/*' /proc/$PPID/cwd/../foo_1.2.3-4.diff.gz | patch -p1 $ exit All that remains is to update the list of patches and to rebuild... (I've deliberately done this a few times, and have also accidentally let patches through...) -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Wishful thinking on your part doesn't constitute reality on mine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [gmail] Re: sponsor quake3 quake3-data packages
I demand that Justin Pryzby may or may not have written... On Thu, Nov 10, 2005 at 09:09:59PM +0100, Marc Leeman wrote: [snip] I decided to put the files in /root/ (like it was in the quake2 package). The main reason for this is that the downloads are considerable and I can assume that users don't want to discard them as easily as a temp file (2x around 40 MB). AFAIK, this is also the strategy of realplayeri (when I still used it). Maybe there is a better location for such files. Indeed /root/ feels like a bad place. I would suggest /tmp/ or something in /var/. Maybe /var/cache/, because information isn't lost if it gets deleted? /var/cache/install/$PACKAGE? -- | Darren Salt | linux (or ds) at | nr. Ashington, | sarge,| youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html What happens if you tie some buttered bread to a cat's back - then drop it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Native package or not?
I demand that Joey Hess may or may not have written... Bernhard R. Link wrote: The general suggestion is to not include the debian/ directory in the release tarball. The reason is that by the format of the Debian source packages no files can be removed by another person's .diff.gz and some tools like debhelper act on (non)existance of specific files. patch is capable of deleting files and even subdirectories when the diff shows that all the lines in a file are removed. The only limitation I know of is that a patch cannot represent the deletion of an empty file, and it cannot represent removing all lines in a file while leaving it empty. ... two limitations. The only two limitations I know of... The former it can't (AFAICS) but the latter it can. Using the attached files: $ echo test $ patch -p0 -i test1.diff # -1,1 +1,0 $ ls -s test 0 test $ $ echo test $ patch -p0 -i test2.diff # -1,1 +0,0 $ ls -l test ls: test: No such file or directory $ diff -N treats empty as non-existent, and patch may fail to ask about -R. [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Memory should be the starting point of the present. --- test +++ test @@ -1,1 +1,0 @@ - --- test +++ test @@ -1,1 +0,0 @@ -
Re: question about CFLAGS modifiers to ./configure
I demand that Miriam Ruiz may or may not have written... DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... -Wl,-z,defs in CFLAGS causes warnings about unused linker flags. It belongs in LDFLAGS. [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE. Power corrupts, and absolute power corrupts absolutely. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HELP!!! New Maint App Process
I demand that Duncan Findlay may or may not have written... On Fri, Oct 25, 2002 at 01:52:43PM -0400, Deva Seetharam wrote: [snip] 1. how does one get an advocate? The best way is to package a piece of software, and make the packages available somewhere. And, preferably, package it because you find it to be useful. Apply to be a NM, and post a message to [EMAIL PROTECTED] asking for a sponsor. A sponsor will take a look at your package and (assuming all goes well) upload them. If they are sufficiently impressed, they will likely be your advocate. The how doesn't matter too much; I've done things in a somewhat different order - get my key signed and have one of the signers be my advocate; wait for an application manager, and ask him to sponsor a (trivial) package. I have other packages (see the URL in my .sig), at least some of which should become official Debian packages, or at least distributed-with-Debian packages. None have sponsors as yet... [snip] -- | Darren Salt | linux (or ds) at | nr. Ashington, | Linux PC, Risc PC | youmustbejoking | Northumberland | No Wodniws here | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys) He who lives without folly is less wise than he believes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: lib765{,-dev}, libdsk{,-dev}, FUSE (xfuse-*)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm looking for sponsors for the following packages: lib765 (lib765, lib765-dev) - an emulation of the uPD765a floppy drive controller libdsk (libdsk, libdsk-dev) - handles various floppy disk image formats xfuse (xfuse-common, xfuse-gtk, xfuse-x11, xfuse-svga, xfuse-fb, possibly a few other bits depending on how it's packaged) - FUSE, a ZX Spectrum emulator I haven't quite decided how to package xfuse: specifically, whether to use libdl (which is used in the version available on my website; see .sig). Comments welcome... -- | Darren Salt | nr. Ashington, | linux (or ds) at | Linux PC, Risc PC | Northumberland | youmustbejoking | No Wodniws here | Toon Army | demon co uk | This space reserved for future expansion To catch intelligent fish, you use a neural net. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0-sb1 (RISC OS) iD8DBQE9zsTnsBKtjPGfWZ8RAgVZAKCU4gYr2DzynhWm4QEXGRtUbGyQ3gCdHxys M7jdIf5rRv2yyoVKofREXp4= =fe1o -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to obtain current package version number?
I demand that Colin Watson may or may not have written... On Tue, Mar 04, 2003 at 11:52:09PM +0100, Marc Haber wrote: On Tue, 4 Mar 2003 16:41:48 +, Colin Watson [EMAIL PROTECTED] wrote: Why not just preprocess the postinst in debian/rules to embed its own version number directly into it? Nice idea, thanks! Is an executeable script (for example an init script) allowed to parse /var/lib/dpkg/info/$PACKAGE.postinst? No - but you could do the same preprocessing for the init script, couldn't you? How would you handle the case where the init script has been locally modified? -- | Darren Salt | nr. Ashington, | linux (or ds) at | Debian woody, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | This space reserved for future expansion The following statement is not true. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: out-of-date-standards-version 3.5.6
I demand that Antti-Juhani Kaijanaho may or may not have written... On 20030321T182926+0100, Marcin Juszkiewicz wrote: License : GNU Public Licence You *could* of course spell that correctly... There are no _spelling_ errors there. (Sorry, no time to give any useful comments.) I see that... -- | Darren Salt | linux (or ds) at | nr. Ashington, | Debian woody, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html If you didn't get caught, did you really do it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: out-of-date-standards-version 3.5.6
I demand that Thomas Viehmann may or may not have written... Darren Salt wrote: License : GNU Public Licence You *could* of course spell that correctly... There are no _spelling_ errors there. While there are no words mispelled, What? There's one, right there :-) the *name* of the license (or licence) is. Just because my name is spelled as Tomas with or without various accents in some languages, I still prefer it correctly spelled. So one ought to spell GPL with License for correctness and consistency. If not, one might wind up as in [0]. You're right: cheque would be correct... gdr -- | Darren Salt | linux (or ds) at | nr. Ashington, | Debian woody, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | I don't ask for much, just untold riches... Beauty seldom recommends one to another. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [debian-mentors] config.sub and config.guess | .diff.gz bloat
I demand that Geert Stappers may or may not have written... [snip] find . -name exact-name-of-file | xargs rm -f or find . -name exact-name-of-file -print0 | xargs -0r rm -f can be reduced to rm -f exact-name-of-file They can't: consider what happens when ./foo/exact-name-of-file exists. My message is: avoid surprises from find. :-) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | I don't ask for much, just untold riches... Proposals, as understood by the proposer, will be judged otherwise by others. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Development packages.
I demand that Stephen Frost may or may not have written... * Roger Leigh ([EMAIL PROTECTED]) wrote: I used a statically-linked binary just a few days ago. I needed to resize an NTFS partition on a newly-delivered system which came with Windows XP. In the event, I was able to get a statically linked binary, copy it onto a floppy and run this after booting from a rescue disk. So, it's very useful for rescue situations, where you can't rely on a whole suite of shared libs, or any installation at all. Boot Knoppix or similar from a CD. Knoppix or similar may not have the required binary. ;-) PCs today are more often installed with CDs than floppies anyway. That's really a pretty poor reason. It's possible that you may not have a CD-ROM drive for, or in, a particular machine: I don't for my laptop, and if I did, I may not always carry it or, for that matter, the floppy drive (which is removable) with the computer. [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Oh, sarge too... You are standing on my toes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lxmusserv, yadex: current maintainers still interested in these packages?
Both lxmusserv and yadex have some outstanding bugs and have not seen any maintainer activity for... quite some time now. lxmusserv has some patches in the BTS which fix relatively minor bugs and allow it to work properly here (emu10k1) without hitting timing issues due to incomplete or buggy OSS sequencer emulation in ALSA. (Note that I'm using stock kernel.org kernels here.) yadex is seriously out of date, and even if 1.7.0 isn't uploaded (I only just noticed this version yesterday, and haven't yet filed a bug on it), it still needs to be compiled with g++ 3.3. I have updated/patched versions in my apt archive (see .sig) which deal with all of the bugs except for no. 199282. If the maintainers don't respond, then I'll adjust my packages for NMU or take-over, filing bugs as appropriate. (Sponsorship will be needed.) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.linux.html Can't learn to do it well? Learn to enjoy doing it badly! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: packaging newbie...: .svn directories / perldoc -- manpage
I demand that Colin Watson may or may not have written... On Tue, Jul 06, 2004 at 08:50:38AM +0200, Adrian 'Dagurashibanipal' von Bidder wrote: (i) I have the package in subversion, so the .svn directories are included in the diff. Can I avoid this easily? $ grep DEBUILD_DPKG_BUILDPACKAGE_OPTS .devscripts DEBUILD_DPKG_BUILDPACKAGE_OPTS=-i'(?:^|/).*~$|(?:^|/)\..*\.swp|DEADJOE|(?:/CVS|/RCS|/\.svn|/\.deps)(?:$|/)' -ICVS -I.svn -uc -us Hmm, extra bits... autom4te.cache? [snip] -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling Barney of Borg: I assimilate you; you assimilate me... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HELP!!! New Maint App Process
I demand that Duncan Findlay may or may not have written... On Fri, Oct 25, 2002 at 01:52:43PM -0400, Deva Seetharam wrote: [snip] 1. how does one get an advocate? The best way is to package a piece of software, and make the packages available somewhere. And, preferably, package it because you find it to be useful. Apply to be a NM, and post a message to debian-mentors@lists.debian.org asking for a sponsor. A sponsor will take a look at your package and (assuming all goes well) upload them. If they are sufficiently impressed, they will likely be your advocate. The how doesn't matter too much; I've done things in a somewhat different order - get my key signed and have one of the signers be my advocate; wait for an application manager, and ask him to sponsor a (trivial) package. I have other packages (see the URL in my .sig), at least some of which should become official Debian packages, or at least distributed-with-Debian packages. None have sponsors as yet... [snip] -- | Darren Salt | linux (or ds) at | nr. Ashington, | Linux PC, Risc PC | youmustbejoking | Northumberland | No Wodniws here | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys) He who lives without folly is less wise than he believes.
RFS: lib765{,-dev}, libdsk{,-dev}, FUSE (xfuse-*)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm looking for sponsors for the following packages: lib765 (lib765, lib765-dev) - an emulation of the uPD765a floppy drive controller libdsk (libdsk, libdsk-dev) - handles various floppy disk image formats xfuse (xfuse-common, xfuse-gtk, xfuse-x11, xfuse-svga, xfuse-fb, possibly a few other bits depending on how it's packaged) - FUSE, a ZX Spectrum emulator I haven't quite decided how to package xfuse: specifically, whether to use libdl (which is used in the version available on my website; see .sig). Comments welcome... -- | Darren Salt | nr. Ashington, | linux (or ds) at | Linux PC, Risc PC | Northumberland | youmustbejoking | No Wodniws here | Toon Army | demon co uk | This space reserved for future expansion To catch intelligent fish, you use a neural net. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0-sb1 (RISC OS) iD8DBQE9zsTnsBKtjPGfWZ8RAgVZAKCU4gYr2DzynhWm4QEXGRtUbGyQ3gCdHxys M7jdIf5rRv2yyoVKofREXp4= =fe1o -END PGP SIGNATURE-
Re: out-of-date-standards-version 3.5.6
I demand that Antti-Juhani Kaijanaho may or may not have written... On 20030321T182926+0100, Marcin Juszkiewicz wrote: License : GNU Public Licence You *could* of course spell that correctly... There are no _spelling_ errors there. (Sorry, no time to give any useful comments.) I see that... -- | Darren Salt | linux (or ds) at | nr. Ashington, | Debian woody, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html If you didn't get caught, did you really do it?
Re: out-of-date-standards-version 3.5.6
I demand that Thomas Viehmann may or may not have written... Darren Salt wrote: License : GNU Public Licence You *could* of course spell that correctly... There are no _spelling_ errors there. While there are no words mispelled, What? There's one, right there :-) the *name* of the license (or licence) is. Just because my name is spelled as Tomas with or without various accents in some languages, I still prefer it correctly spelled. So one ought to spell GPL with License for correctness and consistency. If not, one might wind up as in [0]. You're right: cheque would be correct... gdr -- | Darren Salt | linux (or ds) at | nr. Ashington, | Debian woody, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | I don't ask for much, just untold riches... Beauty seldom recommends one to another.
RFS: playmidi
I'm looking for a sponsor for playmidi. I've fixed some of the reported bugs and applied an extra patch or two of my own. The diff and dsc files aren't available for download but I'll send them to anybody who's interested in sponsorship. I've also considered splitting the package (ref. bug 28471), but I'm not sure that the hassle of doing this is worth the gain wrt dependencies: the main problem is in moving ownership of the debconf configuration data to another package. There's some pre-debconf-handling cruft there too which I'm cautious about removing because it postdates potato - or would it be better to just forget that question and ask afresh? -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html Many pages make a thick book, except for pocket bibles on very thin paper.
Re: RFS: playmidi
I demand that Brian Nelson may or may not have written... Darren Salt [EMAIL PROTECTED] writes: I'm looking for a sponsor for playmidi. I've fixed some of the reported bugs and applied an extra patch or two of my own. The diff and dsc files aren't available for download but I'll send them to anybody who's interested in sponsorship. Are you planning to adopt playmidi? If so, you will really need to take over as upstream as well, since it appears to be quite dead. For that reason, I'm CC'ing upstream. Lack of response by the end of this month will be taken as don't care about it, in which case I may decide to hijack upstream. Otherwise, it would probably be best to just remove playmidi from the archive. Maybe. OTOH, I use it and I know that one other uses it... aside from that, well - popularity-contest data? I've also considered splitting the package (ref. bug 28471), but I'm not sure that the hassle of doing this is worth the gain wrt dependencies: the main problem is in moving ownership of the debconf configuration data to another package. There's some pre-debconf-handling cruft there too which I'm cautious about removing because it postdates potato - or would it be better to just forget that question and ask afresh? Debconf usage is definitely preferable to manually asking questions in the maintainer scripts. True; I don't plan to change that. (I should have typed forget the original answer.) However, splitting an already small package into even smaller pieces is discouraged; the ftp-masters will likely reject it. Then I'll just leave them in one package and mark that bug as 'wontfix'. Also, note that svgalib is very much dead. Maybe nobody will notice if I simply don't build that version :-) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | I don't ask for much, just untold riches... He who hesitates is sometimes saved.
Re: RFS: playmidi
I demand that nil may or may not have written... What the hell? It's taken this long to contact the actual maintainer of playmidi (me)? (Taken to private mail.) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling Warning: this tagline is dangerous. Do not read it.
Re: RFS: playmidi
I demand that Brian Nelson may or may not have written... Matthew Palmer [EMAIL PROTECTED] writes: [snip] I have a question for you, though: why is it, do you think, that someone would have thought that playmidi was quite dead upstream? [...] I made the claim based upon the fact that playmidi doesn't appear to have had a release since 1998. The most recent timestamp on the files in the latest release from http://playmidi.openprojects.net is September 30, 1998. 4.5 years between releases for a tiny utility sounds dead to me. I was inclined to agree with that. Now, though, I'm prepared to wait; I'm told that a new release is planned for next month. Would either of you be prepared to sponsor it? :-) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | Let's keep the pound sterling People are perfect; their implementations aren't.
Re: [debian-mentors] config.sub and config.guess | .diff.gz bloat
I demand that Geert Stappers may or may not have written... [snip] find . -name exact-name-of-file | xargs rm -f or find . -name exact-name-of-file -print0 | xargs -0r rm -f can be reduced to rm -f exact-name-of-file They can't: consider what happens when ./foo/exact-name-of-file exists. My message is: avoid surprises from find. :-) -- | Darren Salt | linux (or ds) at | nr. Ashington, | woody, sarge, | youmustbejoking | Northumberland | RISC OS | demon co uk | Toon Army | I don't ask for much, just untold riches... Proposals, as understood by the proposer, will be judged otherwise by others.
Re: Advice sought regarding binaries in upstream source
I demand that Andree Leidenfrost may or may not have written... I am the co-maintainer for packages mindi and mondo which had bugs #233606 and #233605 filed a while ago. These bugs where about the packages containing binaries in the upstream source. This was true, the binaries have been removed since and the bugs closed. However, this means that we are currently not distributing the pristine upstream sources of mindi and mondo, which I am not overly happy with. (I am highlighting this fact by adding sub-versions to the upstream versions in the package names.) I doubt that this would be considered to be a problem, and may well be a Good Thing: the source takes up slightly less space in the archive, and there's no possibility of upstream's binaries being used during the build process. [snip] Should the answer be that the binaries indeed have to be removed from the upstream source in the orig.tar.gz file, I would also very much like to know whether my current approach of appending a sub-version to the upstream version number is approriate (example: 2.03 - 2.03.1). Bad idea. What if there's an upstream 2.03.1? -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Insanity is just a state of mind.
Re: Development packages.
I demand that Stephen Frost may or may not have written... * Roger Leigh ([EMAIL PROTECTED]) wrote: I used a statically-linked binary just a few days ago. I needed to resize an NTFS partition on a newly-delivered system which came with Windows XP. In the event, I was able to get a statically linked binary, copy it onto a floppy and run this after booting from a rescue disk. So, it's very useful for rescue situations, where you can't rely on a whole suite of shared libs, or any installation at all. Boot Knoppix or similar from a CD. Knoppix or similar may not have the required binary. ;-) PCs today are more often installed with CDs than floppies anyway. That's really a pretty poor reason. It's possible that you may not have a CD-ROM drive for, or in, a particular machine: I don't for my laptop, and if I did, I may not always carry it or, for that matter, the floppy drive (which is removable) with the computer. [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Oh, sarge too... You are standing on my toes.
