Re: 642371 to Should the scim-bridge package be removed?

2012-01-24 Thread Neil Williams
On Tue, 24 Jan 2012 00:09:22 +
Dale Amon  wrote:

> On Mon, Jan 23, 2012 at 10:27:22PM +, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> > 
> > > retitle 642371 Should this package be removed?
> > Bug #642371 [src:scim-bridge] RM: scim-bridge -- ROM; dead upstream, 
> > unmaintained, RC bugs, unfit for KDE4/QT4
> > Changed Bug title to 'Should this package be removed?' from 'RM: 
> > scim-bridge -- ROM; dead upstream, unmaintained, RC bugs, unfit for 
> > KDE4/QT4'
> > > retitle 637066 Should this package be removed?
> > Bug #637066 [src:gramofile] RM: gramofile -- RoM; unmaintained upstream, 
> > low popcon
> > Changed Bug title to 'Should this package be removed?' from 'RM: gramofile 
> > -- RoM; unmaintained upstream, low popcon'
> > > thanks
> > Stopping processing here.
> > 
> > Please contact me if you need assistance.
> > -- 
> > 637066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637066
> > 642371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642371
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> 
> Answer to topic: NO Unless someone intends to write new software
> to parse tapes and record tracks into individual wav files...

Unless someone intends to look after the existing software and maintain
it within Debian then the answer will be yes - remove it. Fix it or let
it be removed due to inaction. Simple.

Unmaintained software which is dead upstream and has not been ported to
updated libraries in Debian is always a candidate for removal.

Those who care about this software need to step up and do the work.
That's all there is to it. It's not enough to just protest or complain -
unless someone does the work, the package remains a candidate for
removal. The RC bugs mentioned originally don't seem to be open any
longer, so there is time for the work to be done.

If the work isn't done, I'll reassign the removal bug myself.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpaX1SZMzPkD.pgp
Description: PGP signature


Bug#655512: Bug #655512: adept: FTBFS: /usr/include/xapian/keymaker.h:125:7: error: expected primary-expression before '.' token

2012-01-24 Thread Aron Xu
I tried to rebuild version adept_3.0~beta7.2+qa1 in pbuilder on a
linux-amd64 machine, and the build works fine for me. Looking at the
logs of kfreebsd-amd64 and mips, the errors were not same. I would
like to ask if it's possible to retry the build on these two
architectures?

-- 
Regards,
Aron Xu



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMr=8w6f5qebyvav3lnsdmshedcmeftwoa+zypujswey+zb...@mail.gmail.com



Bug#647231: libvisual-plugins: FTBFS(!linux): error: possibly undefined macro: AM_PATH_ALSA

2012-01-24 Thread peter green

Note: I have no particular relationship to this package, i'm just trying to
reduce the number of uninstallable packages in armhf testing.


configure.ac:210: warning: macro `AM_PATH_ALSA' not found in library
configure.ac:210: error: possibly undefined macro: AM_PATH_ALSA
 If this token and others are legitimate, please use m4_pattern_allow.
 See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1


AM_PATH_ALSA is defined in /usr/share/aclocal/alsa.m4 which is
in package libasound2-dev which only exists on linux. 


Previously this was not an issue because configure was not rebuilt as part of
the build, however in his QA upload Steve Langasek changed the package build to
rebuild configure and hence made it FTBFS on non-linux architectures.

Having throught about this I see several possible soloutions

1: go back to including configure in the packaging rather than building it at
  package build time.
2: move alsa.m4 to a package that exists on all architectures
3: include a copy of alsa.m4 in the libvisual-plugins source
4: include a dummy definition of AM_PATH_ALSA that does nothing in 
  the libvisual-plugins source and only use it on architectures other

  than linux.

Option 1 is probablly the simplest fix but shipping generated code rather than 
doing the generation at build time seems like a step backwards to me.


Option 2 seems good in theory (after all autoconf is mean to generate configure
scripts that run on platforms other than the ones they were generated on so 
having
AM_PATH_ALSA available on architecture without alsa isn't too unreasonable IMO) 
but the question would be where to move it to and how much disruption would said

move cause...

Option 3 is code duplication that is generally frowned upon

Option 4 seems like the best option if the asla guys don't want to provide 
alsa.m4 on non-linux architectures.


I am CCing Steve (as the last person to touch the package and the one who
introduced the FTBFS) and the ALSA maintainers list to get their opinions on 
this.








--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f1f0ef0.8020...@p10link.net



Processed: libxp dependencies

2012-01-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 657253 by 623660 623661 623662 623663 623664 623665 623667 657260
Bug #657253 [libxp6] Xprint is deprecated, so remove libxp?
Was not blocked by any bugs.
Added blocking bug(s) of 657253: 623661, 623665, 623664, 623667, 623660, 
623662, 657260, and 623663
> block 657253 by 623646 657257 623643 623645 623642 623644 623650 623649
Bug #657253 [libxp6] Xprint is deprecated, so remove libxp?
Was blocked by: 623661 623665 623664 623667 623660 623662 657260 623663
Added blocking bug(s) of 657253: 623642, 623645, 623644, 657257, 623649, 
623646, 623643, and 623650
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
657253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13274547498229.transcr...@bugs.debian.org