Bug#962291: 9base: please include ssam executable
Package: 9base Version: 1:6-7+b1 Severity: wishlist Dear Maintainer, It would be great to include the `ssam` executable in the 9base package, as that is an excellent way to execute structured regular expressions on a linux system. The script is present upstream: https://git.suckless.org/9base/file/ssam/ssam.html Thanks, Karl -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages 9base depends on: ii libc6 2.28-10 9base recommends no packages. Versions of packages 9base suggests: pn wmii2 -- no debconf information
Bug#916865: [bumprace] Replaced audio files
Hi and a happy new year! I've included the new files in the upstream release, updated the credits screen and tagged a 1.5.7 release. https://bitbucket.org/karlb/bumprace/downloads/?tab=tags If you can spot any problem with this release let me know Karl On Wed, Dec 19, 2018 at 10:12 PM Christian T. Steigies wrote: > > On Wed, Dec 19, 2018 at 06:15:21PM +0100, Bruno Kleinert wrote: > > Package: bumprace > > Version: 1.5.4-3 > > Severity: normal > > Tags: patch > > > > --- Please enter the report below this line. --- > > Hi Christian, > > > > since audio files were removed in #613344, I gathered free/libre > > replacements at https://opengameart.org/. Please find attached a > > modified source package and consider forwarding the changes to the > > upstream author. Thank you in advance! > > This is great, thanks! I already started to upgrade the packaging, there is > also a new upstream version, so chances are good to get this upstream. > > Looking at the FAQ: > https://opengameart.org/content/faq#q-how-to-credit > it seems that the artists should be mentioned in the credits screen of > bumprace as well? > > I am a bit busy the next month, in case I can not finish this in time, > please upload this version. > > thanks, > Christian
Bug#756525: black-box: update config.{sub, guess} to fix FTBFS for ppc64el port"
I've resigned as a debian developer, so I can't push any changes. As far as I can see, there is no new maintainer, yet. Maybe some debian dev can do a NMU upload. On Thu, Oct 30, 2014 at 7:35 PM, Paulo Flabiano Smorigo wrote: > Dear Maintainer, > > Can you please consider the patch from Ravi in order to build this > package for all archs? > > Currently, black-box is failing to build for ppc64el and arm64: > https://buildd.debian.org/status/package.php?p=black-box&suite=sid > > Thanks in advance! > -- > Paulo Flabiano Smorigo > IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728868: O: black-box
Package: wnpp Severity: normal I'm orphaning black-box. If I spend any time on this game, it would be better spent fixing bugs upstream than improving the debian package. The package is pretty low on maintenance, so feel free to adopt it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728867: O: penguin-command
Package: wnpp Severity: normal I'm orphaning penguin-command. If I spend any time on this game, it would be better spent fixing bugs upstream than improving the debian package. The package is pretty low on maintenance, so feel free to adopt it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#528345: python-zsi: Error on import ('DefaultHandlerChain' is not defined)
> I am unable to import ZSI.twisted.WSresource. Tested with python2.4 > and 2.5. As there is not much to do wrong on import, I assume this is > a bug in the package. Moving the DefaultHandlerChain class to the top of the file seems to solve this problem. Bye, Karl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#528345: python-zsi: Error on import ('DefaultHandlerChain' is not defined)
Package: python-zsi Version: 2.1~a1-2 Severity: important I am unable to import ZSI.twisted.WSresource. Tested with python2.4 and 2.5. As there is not much to do wrong on import, I assume this is a bug in the package. Any information on this will be appreciated. Thanks, Karl Python 2.5.2 (r252:60911, Jan 4 2009, 17:40:26) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import ZSI.twisted.WSresource Traceback (most recent call last): File "", line 1, in File "/var/lib/python-support/python2.5/ZSI/twisted/WSresource.py", line 256, in class WSAddressHandlerChainFactory: File "/var/lib/python-support/python2.5/ZSI/twisted/WSresource.py", line 257, in WSAddressHandlerChainFactory protocol = DefaultHandlerChain NameError: name 'DefaultHandlerChain' is not defined -- System Information: Debian Release: 5.0.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages python-zsi depends on: ii python2.5.2-3An interactive high-level object-o ii python-support0.8.4 automated rebuilding support for P ii python-xml0.8.4-10.1 XML tools for Python python-zsi recommends no packages. python-zsi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#500796: black-box: new upstream version available
Hi Javier, I just uploaded the new package. I tried to split your changes correctly between upstream and the debian diff, so that non-debian users can also take advantage of your changes. I currently only have a stable dev system here, so I could only verify debhelper 5 compat and standards 3.7.2 . But apart from that, everything should be included. Thanks a lot for your help, Karl On 05.10.2008, at 01:56, Javier Serrano Polo wrote: El ds 04 de 10 de 2008 a les 18:24 +0200, en/na Karl Bartel va escriure: Where can I find your patch (preferably with a short summary of bugs it fixes)? I'll send you my last packaging. The changes are: * Clean up dependencies (shlibdeps). * Remove compilation warnings. * Fix buffer overflows (very important). * Erase previous level text. * Fix level command option. * Reuse path calculation function. * Avoid repeated crystal generation. * Fix window title. * Added menu icon. * Added desktop file. * Upgrade rules to compat 7. * Install manpage. The binary package is lintian clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500796: black-box: new upstream version available
The patch looks great! I've already put together a new upstream release and I plan to upload a new deb sometime this week. Thanks, Karl On 05.10.2008, at 01:56, Javier Serrano Polo wrote: El ds 04 de 10 de 2008 a les 18:24 +0200, en/na Karl Bartel va escriure: Where can I find your patch (preferably with a short summary of bugs it fixes)? I'll send you my last packaging. The changes are: * Clean up dependencies (shlibdeps). * Remove compilation warnings. * Fix buffer overflows (very important). * Erase previous level text. * Fix level command option. * Reuse path calculation function. * Avoid repeated crystal generation. * Fix window title. * Added menu icon. * Added desktop file. * Upgrade rules to compat 7. * Install manpage. The binary package is lintian clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500796: black-box: new upstream version available
Hi Javier, Do you have any intention to package version 1.4.7? Current version has an important bug (not in the BTS). My patch's against 1.4.6-2.2 and fixes several issues but I'm likely to upgrade to 1.4.7. I intend to package a more recent version. I'm sorry for the enormous delay. I would like to do a round of bug fixing before uploading. Where can I find your patch (preferably with a short summary of bugs it fixes)? Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#184437: Patch applied upstream
This patch really seems to work around the problem. I applied it upstream and I'll update the debian package soon. Better solutions than the one in this patch are still welcome, of course. -- Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#184437: Please, God. Make this patch work.
Hi Brandon, I have a simple patch that fixes this segfault for me. Here it is: This seems to work well. It's a pity not to use this nice music, but since it is clearly better than an occasional crash. While debugging, I tried replacing that line in sound.c with 4 pennights. I thought it would crash more. It didn't crash at all. I also tried moving it to the front, back, and second position. It didn't crash under those seemingly identical situations. Like I said, weird. I guess this is the reason why I didn't succeed in identifying the mod file, which causes the crash. Also worthy of note, is that every time I got penguin-command to crash , it was playing song #2 (starting from 0). Here is a log I have been keeping. I only added to this log sometimes when penguin-command would crash. I am not including the core dumps. If someone wants them, email me. Interesting. I will think a bit more about this (and test a bit more myself). It might be a good clue. Core was generated by `penguin-command'. Program terminated with signal 11, Segmentation fault. #0 0xb7eb1413 in SDL_LowerBlit () from /usr/lib/libSDL-1.2.so.0 (gdb) backtrace #0 0xb7eb1413 in SDL_LowerBlit () from /usr/lib/libSDL-1.2.so.0 #1 0xb7eb16b4 in SDL_UpperBlit () from /usr/lib/libSDL-1.2.so.0 #2 0x0804ceea in Blit (Xpos=136111496, Ypos=510, image=0x805a750) at gfx.c:331 #3 0x0804bdab in DrawCannon (x=20, y=0) at game.c:160 #4 0x0804c0ad in ProcessEvents () at game.c:322 #5 0x0804c314 in StartGame () at game.c:429 #6 0x0804b1df in main (argc=136100536, argv=0x0) at main.c:460 (gdb) Notice that this has some things in common with the trace that Karl provided a few years ago, but some things are distinctly different. It probably crashes in Blit, because the function is the most memory intensive one. This really looks like memory corruption. Thanks for your hard work. I'd like to do some more testing before applying the patch, to get sure it really works around this bug (and hopefully get some more details). The crash doesn't occur very frequently, so It'll probably take some time. I'll write again within the next week. Thanks again, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409602: Fixed in upstream
This bug could be reproduced and is fixed in upstream release 1.4.3 . Thanks for your detailed bug description. This made finding the bug fairly easy. -- Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380704: Please stop Build-Depending on automake
Hi Karl, You're one of the last holdouts for this transition. So you said in your previous email you would upload near the end of August. Will you upload soon, or can I NMU your black-box? You can NMU. I'm terribly sorry for being slow and as well as giving you a false estimate. -- Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380704: Please stop Build-Depending on automake
Thanks for the bug report and patch. I'll fix it in the next upload, which will probably be done near the end of this month. -- Karl On 01.08.2006, at 04:10, Eric Dorland wrote: Package: black-box Severity: wishlist Tags: patch The automake maintainer is working towards reclaiming the automake package name, which currently rests on automake1.4, the oldest version of automake. Your package Build-Depends on automake, hence this bug report. Please see http://wiki.debian.org/AutomakeTransition for more information on this transition. Your package appears to work with the latest automake1.9 package. Attached is a patch to update the build-dependency. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#369551: castle-combat: Unhandled error in Deferred when shooting
On 06.06.2006, at 11:15, Karl Bartel wrote: Thanks for the patch. It will be included in the next upstream release, which will be released this month, if everything works out as planned. I just uploaded a new release. The code worked out quite different than in the patch, because I wanted to add a "Sound on/off" switch without adding an additional conditional around each line where a sound is played. This bug should be fixed nevertheless. I didn't manage to disable my sound card (well, I didn't try very hard...) to verify this, so it would be great if you could let me know whether it works for you. Thanks for your help, Karl On 05.06.2006, at 18:46, John Lightsey wrote: On Tue, 2006-05-30 at 18:07 +0300, Timo Juhani Lindfors wrote: Package: castle-combat Version: 0.8.0-2 Severity: grave Justification: renders package unusable When two local players play the game it throws ... File "/usr/share/games/castle-combat/scripts/cannon.py", line 21, in __init__ sound.cannon.play() exceptions.AttributeError: 'module' object has no attribute 'cannon' when player #1 tries to fire the cannon. If you can't reproduce this please ask for more info. Thanks for pointing this out. This problem comes up when you play castle-combat without any sound device. The cannon sound is loaded in sound.py after "if pygame.mixer.get_init():". This will be false when there is no sound device and the cannon sounds will not be loaded. When the cannon (and wall hit) sounds are played in cannon.py there is no test to see if the sounds were successfully loaded. I'm not certain if calling pygame.mixer.get_init() each time a cannon shot sound is played would cause a notable performance hit and my knowledge of python is still very limited, so I'll just add an "enabled" flag to sound.py and check it in cannon.py before the sounds are played. A patch with the changes I'm applying to the next Debian release of castle-combat is attached to this message. John <16-no_sound_device.dpatch> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#369551: castle-combat: Unhandled error in Deferred when shooting
Thanks for the patch. It will be included in the next upstream release, which will be released this month, if everything works out as planned. -- Karl On 05.06.2006, at 18:46, John Lightsey wrote: On Tue, 2006-05-30 at 18:07 +0300, Timo Juhani Lindfors wrote: Package: castle-combat Version: 0.8.0-2 Severity: grave Justification: renders package unusable When two local players play the game it throws ... File "/usr/share/games/castle-combat/scripts/cannon.py", line 21, in __init__ sound.cannon.play() exceptions.AttributeError: 'module' object has no attribute 'cannon' when player #1 tries to fire the cannon. If you can't reproduce this please ask for more info. Thanks for pointing this out. This problem comes up when you play castle-combat without any sound device. The cannon sound is loaded in sound.py after "if pygame.mixer.get_init():". This will be false when there is no sound device and the cannon sounds will not be loaded. When the cannon (and wall hit) sounds are played in cannon.py there is no test to see if the sounds were successfully loaded. I'm not certain if calling pygame.mixer.get_init() each time a cannon shot sound is played would cause a notable performance hit and my knowledge of python is still very limited, so I'll just add an "enabled" flag to sound.py and check it in cannon.py before the sounds are played. A patch with the changes I'm applying to the next Debian release of castle-combat is attached to this message. John <16-no_sound_device.dpatch> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335421: penguin-command(GNU/k*BSD): FTBFS: out of date config.sub/config.guess
The current version of penguin-command fails to build on GNU/kFreeBSD, because of outdated config.guess and config.sub. I will take care of this tomorrow. -- Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335402: penguin-command: FTBFS: missing build-depends on libsdl-image1.2-dev
it seems you forgot a build-depends on libsdl-image1.2-dev, the package has failed to build on six arches so far. You are right. I removed the old sdl-image code from the penguin- command sources, which were included in earlier versions and forgot to update the build deps. Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303705: penguin-command now uninstallable on non-i386
Thanks! I'll fix this in the next upload. I guess it is about time for that next upload. Absolutely. Hope you're OK, Karl. I'm OK, but sometimes a grave bug is needed to bring my attention back to my old games. I just uploaded a new version. Thanks for the heads up and sorry that it took me so long, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303705: Incorrect libpng build-dependencies
Package: penguin-command Currently, penguin-command build-depends on libpng2-dev | libpng3-dev | libpng12-0-dev. On i386, it was built against libpng12, but on other architectures it makes it build against libpng10. This is wrong, as SDL uses libpng12. In some cases, it can make some partial upgrades from woody fail. Thanks! I'll fix this in the next upload. Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
