On Mon, Jan 14, 2008 at 12:59:34PM -0800, Jack T Mudge III wrote:
> It seems to me that removing old packages just because they are old misses an
> important point: There are people who use them. Perhaps warning them that the
> packages are ancient and may be dangerous to their health is a good t
Luk Claes wrote:
Jack T Mudge III wrote:
On Monday 14 January 2008 07:13:01 am Riku Voipio wrote:
It's not only lack of 64bit that makes xview a problem. If security
issues withing xview are found, it is unlikely that they get fixed
in a timely manner.
Sometimes I wish there were a security wa
Riku Voipio wrote:
If none of the alternative players is acceptable, rather than using
voodoo patches to resurrect a dead library, the time could be spent
making a 1:1 GUI copy of workman with something modern, like
python-gtk2.
What a great idea.
I had this idea that workman was a CLI app, b
Steve Langasek wrote:
On Mon, Jan 14, 2008 at 12:59:34PM -0800, Jack T Mudge III wrote:
It seems to me that removing old packages just because they are old misses an
important point: There are people who use them. Perhaps warning them that the
packages are ancient and may be dangerous to their
On Mon, Jan 14, 2008 at 03:09:53PM +0200, Riku Voipio wrote:
> After considering porter NMU on xview, I think x11 toolkit can safely
> be canned as museumware. Most damning is the lack of 64bit support.
> See #228957 and #320155, although a patch was produduced nobody bothered,
> applying it, nor i
On Tue, Jan 15, 2008 at 03:35:10PM +0100, Martin Buck wrote:
> > - only few reverse dependencies
> > - relatevely low popcon count 500
> Rank #6235 might be relatively low, but in that case, there are 1s of
> packages that would be candidates for removal...
Low installation count alone does
tim hall wrote:
> Luk Claes wrote:
>> Jack T Mudge III wrote:
>>> On Monday 14 January 2008 07:13:01 am Riku Voipio wrote:
It's not only lack of 64bit that makes xview a problem. If security
issues withing xview are found, it is unlikely that they get fixed
in a timely manner.
>>> S
Hi,
While working on packages with a lot of bugs, I noticed the state of
coreutils: there hasn't been any maintainer upload to unstable since
08/2006, it has been failing to build on mips and mipsel for nearly a
year, and it seems that some bug triaging is really necessary (nearly
300 bugs open, a
Paul Wise <[EMAIL PROTECTED]> wrote:
> On Jan 15, 2008 6:29 AM, Jack T Mudge III <[EMAIL PROTECTED]> wrote:
>
>> Sometimes I wish there were a security warning system in dpkg. Say, a user
>> loads up Synaptic (or Adept, depending), and when they try to install a
>> dangerous package -- maybe a ser
Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> While working on packages with a lot of bugs, I noticed the state of
> coreutils: there hasn't been any maintainer upload to unstable since
> 08/2006,
The last upload of 6.10 to experimental is from December 2007, though.
Cheers,
Moritz
--
T
On 15/01/08 at 23:56 +0100, Moritz Muehlenhoff wrote:
> Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> > While working on packages with a lot of bugs, I noticed the state of
> > coreutils: there hasn't been any maintainer upload to unstable since
> > 08/2006,
>
> The last upload of 6.10 to experimen
Package: qa.debian.org
Severity: wishlist
It would be good if the PTS would link to the Debian Security Tracker.
The URL format is
http://security-tracker.debian.net/tracker/source-package/SRCPKGNAME
Cheers,
Moritz
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
Package: qa.debian.org
Severity: normal
Hello,
The entry "Testing status" refers to the list of bugs that are
holding back a package. This entry is a hyperlink but links to only
one of the bugs even when there is more than one bug that is
holding back the package.
Regards,
Kapil.
-- System In
13 matches
Mail list logo
