Your message dated Wed, 4 Jul 2012 14:55:53 +0100
with message-id
<CAPQ4b8=xS0Bs9cbu4yMtHPNYokPsTbr2LdVs4pcoN8FNx=i...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (usplash-theme-debian)
has caused the Debian Bug report #521214,
regarding misc fixes for Yeeloong
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
521214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521214
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: usplash-theme-debian
Severity: normal
Tags: patch
The debian theme needs a few fixes to work on a Yeeloong:
- Add mipsel to architecture list
- Add 1024x600 to size list
- Fix ratio calculation in themesetup.sh (it needs to match exactly
with the check in libusplash.c)
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -ur usplash-theme-debian-4.old/debian/control usplash-theme-debian-4/debian/control
--- usplash-theme-debian-4.old/debian/control 2007-07-09 00:49:36.000000000 +0200
+++ usplash-theme-debian-4/debian/control 2009-03-25 17:54:35.000000000 +0100
@@ -3,14 +3,14 @@
Priority: optional
Maintainer: maximilian attems <[email protected]>
Uploaders: David Härdeman <[email protected]>, Petter Reinholdtsen <[email protected]>, Otavio Salvador <[email protected]>
-Build-Depends: debhelper (>= 5.0.0), libusplash-dev, imagemagick, librsvg2-bin
+Build-Depends: debhelper (>= 5.0.0), libusplash-dev, imagemagick, librsvg2-bin, bc
Standards-Version: 3.7.2.2
XS-Vcs-Git: git://git.debian.org/git/collab-maint/usplash-theme-debian.git
XS-Vcs-Browser: http://git.debian.org/?p=collab-maint/usplash-theme-debian.git
Package: usplash-theme-debian
Section: misc
-Architecture: amd64 i386 powerpc sparc
+Architecture: amd64 i386 powerpc sparc mipsel
Depends: ${shlibs:Depends}
Provides: usplash-theme
Description: Debian usplash theme
diff -ur usplash-theme-debian-4.old/Makefile usplash-theme-debian-4/Makefile
--- usplash-theme-debian-4.old/Makefile 2007-07-09 00:39:34.000000000 +0200
+++ usplash-theme-debian-4/Makefile 2009-03-25 21:20:38.000000000 +0100
@@ -20,7 +20,7 @@
# This is the list of sizes to build and include in the theme
# By convention, the sizes should go from smaller to larger
-sizes = 640x480 800x600 1024x768 1280x1024
+sizes = 640x480 800x600 1024x600 1024x768 1280x1024
# This creates a list with entries like background_800x600.png...
backgrounds = $(addsuffix .png, $(addprefix background_, $(sizes)))
diff -ur usplash-theme-debian-4.old/themesetup.sh usplash-theme-debian-4/themesetup.sh
--- usplash-theme-debian-4.old/themesetup.sh 2007-06-27 15:26:17.000000000 +0200
+++ usplash-theme-debian-4/themesetup.sh 2009-03-25 17:54:25.000000000 +0100
@@ -84,7 +84,8 @@
WIDTH=${size%x*}
HEIGHT=${size#*x}
- if [ $(( $WIDTH / 16 )) -eq $(( $HEIGHT / 9 )) ]; then
+ # This needs to match the ratio check in libusplash.c
+ if [ `echo "$WIDTH > $HEIGHT * 1.55" | bc` = 1 ]; then
RATIO="USPLASH_16_9"
else
RATIO="USPLASH_4_3"
--- End Message ---
--- Begin Message ---
Hello,
Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved in due time.
usplash-theme-debian has been removed from unstable [1] a couple of
years ago and only present in oldstable by now [2], same for usplash
[3].
[1]
http://packages.qa.debian.org/u/usplash-theme-debian/news/20100927T143534Z.html
[2] http://packages.qa.debian.org/u/usplash-theme-debian.html
[3] http://packages.qa.debian.org/u/usplash.html
The bugs are now orphan (without maintainer assigned) so they probably
will not be noticed/modified further. So I think that the best
solution is to close them now, doing it. Please comment if you want
to handle the reports in some other way (reassigned to other packages,
etc.).
Cheers.
--- End Message ---
