Your message dated Wed, 06 Jul 2011 14:23:39 +0200
with message-id <4e1453cb.7020...@thykier.net>
and subject line Re: Bug#632828: xca: Should this package be orphaned?
has caused the Debian Bug report #632828,
regarding xca: Should this package be orphaned?
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 ow...@bugs.debian.org
immediately.)
--
632828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xca
Severity: serious
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Tino Keitel
Currently xca FTBFS in sid and has been removed from testing due to
changes in how linking is done. I believe (but have not tested it)
that the patch from #605141 should fix the issue (and also close
#615796).
Due to a lack of reply to these bugs, I wonder if you still have
time to maintain this package. It is perfectly okay, if this is
the case, though please either put it up for adoption or request
a co-maintainer.
Otherwise, please look into fixing the above mentioned RC bugs
so that xca can migrate to testing. Feel free to ask for help
if they are giving you issues (incl. using the help tag).
Please note that if you do not reply to this bug within 14 days
I will take it as a lack of time or interest package and orphan
it on your behalf.
If you do not have time right now (e.g. due to vacation),
please give me a very short reply with when you will be available
again. In this case, I may NMU your package to fix the FTBFS
but I will leave this bug open to prevent testing migration
till you return.
Thanks for your time,
~Niels
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJOFCBZAAoJEAVLu599gGRC1ikP/127LX2b9Oz/t8Lddp+suBxx
B3gM7zNxVbzQHOHsANpi/JQ9ThskI/vD8/UVS2P8Xn3V+ynuaNJThdDZdLitwJ4+
5uPxmRqFjwe5MwzK/y2xjDl8G9gBFXSdNa5tTx/a2SoeFhD52LFi4ApCQyTj7/hb
s97pN+a3m853bDLQ6bdoZhqMXpc8DWJNqWLVUBvV78gW6TiaZJ8ksz4OGGGMIB4X
G5qOYKJDV8vhjG3VhQxuPEswlV/i1frerNvGkT/SaGYXNaxsvYV+EH04VZHpW7L2
lPMOvPDlQcLJFDToXPsus2y/Jt2Xm21JAg5mhKs6JzWjqLPDHYNEnRZxMTWFzp9B
geLtfaOLTtBGR1AWgURHPD5ADpXrE3Tb4SzGBViUDKFP8WyhYVDf4U4wklMk29u5
IgZf3dN0ypI6/nVn1aROGr60f46hKWnR3juDbmHaN2VJUdRbaWAvIWTak3DEPvmr
BPyMO7cvfMKPLj2FE++PqU+PqqWkU/pL12qsYdRJSJzK8X68p3h+kv6maGxhEZhC
L8phPu0iO/7UgLVhL+N8oy/J7q1tRaZRElh1fGa2FU9x3R6iCsHxCWjhh9DgHl1/
3wRZkOnZY/TC+Qtm9tcpei45rMLE2kV6jDBHOL6NO7mTXs1nRWk34EzNpoRGGQrx
13EFPtEOm5sFM05mPVdD
=SFut
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2011-07-06 14:01, Tino Keitel wrote:
> On Wed, Jul 06, 2011 at 10:44:12 +0200, Niels Thykier wrote:
>> Package: xca
>> Severity: serious
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Hi Tino Keitel
>>
>> Currently xca FTBFS in sid and has been removed from testing due to
>> changes in how linking is done. I believe (but have not tested it)
>> that the patch from #605141 should fix the issue (and also close
>> #615796).
>>
>> Due to a lack of reply to these bugs, I wonder if you still have
>> time to maintain this package. It is perfectly okay, if this is
>> the case, though please either put it up for adoption or request
>> a co-maintainer.
>> Otherwise, please look into fixing the above mentioned RC bugs
>> so that xca can migrate to testing. Feel free to ask for help
>> if they are giving you issues (incl. using the help tag).
>
> Hi,
>
> I initially used the patch attached in the BTS, but the upstream author
> fixed it in a different way after I sent him the patch. I already
> prepared a new package taken from a new upstream snapshot which
> contains the fix, but did not get a reply from my sponsor yet. I also
> intended to mark the bugs as "upload pending", but forgot...
>
> Just FYI, the package can be found here:
>
> http://tikei.de/debian/xca/
>
> Regards,
> Tino
Hi,
Looks like there is no reason for this bug then. :)
The dates on the files at http://tikei.de/debian/xca/ suggests this
package is rather new, if so then lets wait for your usual sponsor.
If you sponsor is busy or on vacation, feel free to contact me
privately and I will look at doing a one-time sponsoring of this
package. :)
Thanks for the quick reply,
~Niels
--- End Message ---
