Bug#959994: codeville: Consider removing this package

2020-05-08 Thread Michael Janssen (Debian)
Hello.

I agree with this assessment.  If you can submit it immediately, that would
be fine with me.

Marie Janssen --- Jamuraa --- jamu...@base0.net --- jamu...@debian.org

On Thu, May 7, 2020 at 8:48 PM Boyuan Yang  wrote:

> Source: codeville
> Severity: serious
> Version: 0.8.0-2.1
> Tags: sid  bullseye
> X-Debbugs-CC: jamu...@debian.org
>
> Dear Debian codeville maintainer,
>
> It seems that package codevilla has a dead upstream since at least 2014.
> It is
> a discontinued VCS thus it doesn't make any sense to keep it in Debian
> archive. Besides, this software is now affected by python2 removal.
>
> As a result, I am proposing to have this package removed from Debian. I
> will
> submit a removal request to FTP Masters 7 days later (after May 14, 2020).
> If
> you have any thoughts, please let me know *immediately*.
>
> --
> Best Regards,
> Boyuan Yang
>


Bug#536903: bogosort: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field: libc6 dpkg (>= 1.15.4) | install-info

2009-08-08 Thread Michael Janssen (Debian)
On Sat, Aug 8, 2009 at 9:09 AM, Chris Lamb wrote:
> Simon McVittie wrote:
>
>> However, I'm not sure whether Debian really benefits enough from having
>> bogosort to resolve this RC bug by fixing it rather than removing it:
>
> I agree. I also value Ansgar contribution - sorry to shoot it down.
>
> Michael, you're currently listed as the maintainer of bogosort. Would you
> object greatly if one of us filed an RM bug?
>
> Due to timing issues wrt squeeze (and also I understand you are very busy
> these days) I think it would be better if this defaulted to one of us filing
> the bug if no objection is forthcoming in, say, 3 weeks.

I originally packaged it as a curiosity, so I have no objection to it
being removed from the distribution.  It's not as useful as a shuffler
now that shuf is in an essential package, and there are better ways to
tax your CPU than running pathologically bad sorting algorithms.

Michael Janssen --- Jamuraa --- jamu...@base0.net --- jamu...@debian.org



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#323556: debian BTS 323556: bittorent-gui vs. wxPython

2005-09-06 Thread Michael Janssen
On Wed, 07 Sep 2005, Paul Wise wrote:

> On Tue, 2005-09-06 at 12:41 -0700, Larry Doolittle wrote:
> 
> > I see the same error, of course.  Poking around the
> > various wxgtk packages in sid at the moment, I don't
> > see a libwxgtk2.4-1-python.  Maybe the debs changed again?
> > I guess the right dependency now is python-wxgtk2.4.
> > I haven't tried anything yet.
> 
> Looks like they changed it again :) Updated the patch and am attaching
> it to the bug report with this message.
> 
> > Have you heard any rumblings on this from either the
> > wxgtk folk or the bittorrent folk?
> 
> Nope, but I think it is part of the addition of wx2.6 and general
> cleanup of wx packages that has been coming for a while. Yet another
> transition for the post-sarge fun.


Well, good thing I didn't upload that one.   I'll get this change in
and upload tomorrow.  Thanks for the (further) heads up.


-- 
Michael Janssen --- Jamuraa --- [EMAIL PROTECTED] --- [EMAIL PROTECTED]



Bug#315510: bittorrent: 3.2.4-4 fails to connect to peers (3.2.4-3sarge0.1 works fine)

2005-06-23 Thread Michael Janssen
On Thu, 23 Jun 2005, Tim Van Holder wrote:

> Package: bittorrent
> Version: 3.4.2-3sarge0.1
> Severity: grave
> Justification: renders package unusable
> 
> 
> After upgrading bittorrent to 3.4.2-4 it ceased to work - it will
> start up fine but wait forever on the 'connecting to peers' prompt.
> Downgrading to the version on stable fixes this, so it must be
> a recently introduced change.  I'm behind a NAT firewall, so perhaps
> the changes in port usage are to blame?

Can you give me more information on how the new one doesn't work?  I
did test it behind a NAT and on a "normal" connection, so I don't
think it is related to that.  If you could run a lsof with the program
running it may be useful.   Also it could be the case that you just
did not wait long enough - NATed peers have a startup time which is
much slower because other peers cannot connect to them, and there is a
certain amount of wait time for a new peer in the swarm.

-- 
Michael Janssen --- Jamuraa --- [EMAIL PROTECTED] --- [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]