> I tried with multiple numbers - 100, 50, 10.
> No luck, none of them helped.
I killed apt-listbugs with a signal on i386/kfreebsd,
and it died in
Parsing Found/Fixed information... 0%
Exception `SignalException' at /usr/lib/ruby/1.8/debian.rb:78 - SIGTERM
Terminated
This is dpkg-ruby try
Hi,
> I tried with multiple numbers - 100, 50, 10.
> No luck, none of them helped.
strange.
> As I had mentioned in my earlier posts, this issue is only seen when the
> number of packages passed is too high. In both the cases for me, the meta
> package being installed was xserver-xorg which l
On Tuesday 07 August 2007, Junichi Uekawa wrote:
> in lib/debian/bts.rb there is a constant
>
> ParseStep = 200
>
> This is the value which determines how many bugs to process at a time.
> Reducing this number will make things slow, and it should really be
> determined dynamically based on
Hi,
> I might agree with you on that because the Hurd OS is running under KVM
> with 128M of RAM allocated for it.
> Although KVM is fast I've felt that Hurd is not _very_ good at memory
> management.
> This could be true because when I lower down the number of packages, the
> installation procee
g into RAM. What do you say ?
Ritesh
-Original Message-
From: Junichi Uekawa [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 07, 2007 4:39 AM
To: Sarraf, Ritesh
Cc: [EMAIL PROTECTED]; Junichi Uekawa
Subject: Re: Fwd: Re: Bug#436059: apt-listbug remains frozen on hurd
Hi,
At Mon, 6 Aug
Hi,
At Mon, 6 Aug 2007 20:23:14 +0530,
Ritesh Raj Sarraf wrote:
>
> Hi Junichi,
>
> Please ignore my previous mail because that is not containing the correct
> information. It is timing out at the network level only. It was a network
> issue.
>
> Here's the proper log that you were wanting:
uot;sid lenny
fixed-upstream" {}fixed_date=[] {}package="xserver-xorg-core"
{}found_date=[]>
#nil}
{}fixed_versions=["xorg-server/2:1.3.0.0.dfsg-8"] {}mergedwith=428882
{}found=# {}unarchived="" {}blockedby=""
{}keywords="sid lenny fixed-upstream"
On Sunday 05 August 2007, Junichi Uekawa wrote:
> Try the following NOW, as documented in README.Debian
>
>
> (echo 'VERSION 2'; echo '' ;
> ls -1 /var/cache/apt/archives/*_*.deb |
> sed 's/^/x x x x /') |
> /usr/sbin/apt-listbugs apt -d
Hi Junichi,
Unfortunately my domain
At Sun, 5 Aug 2007 22:32:27 +0530,
Ritesh Raj Sarraf wrote:
>
> On Sunday 05 August 2007, Junichi Uekawa wrote:
> > Try the following NOW, as documented in README.Debian
> >
>
> You should have explained that "NOW" earlier. :-)
> By the time I saw your email, I had already done an apt-get clean.
On Sunday 05 August 2007, Junichi Uekawa wrote:
> Try the following NOW, as documented in README.Debian
>
You should have explained that "NOW" earlier. :-)
By the time I saw your email, I had already done an apt-get clean.
>
> (echo 'VERSION 2'; echo '' ;
> ls -1 /var/cache/apt/archives/*
Hi,
> > > I've configured apt-listbugs to run on Hurd.
> > >
> > > On execution from with apt, apt-listbugs is able to fetch Bug Reports but
> > > it freezes for ever on the message "Parsing Found/Fixed information...".
> > >
> > > The freeze is only for the app and can be interrupted.
> > >
> > >
On Sunday 05 August 2007, Junichi Uekawa wrote:
> Hi,
>
> > I've configured apt-listbugs to run on Hurd.
> >
> > On execution from with apt, apt-listbugs is able to fetch Bug Reports but
> > it freezes for ever on the message "Parsing Found/Fixed information...".
> >
> > The freeze is only for the
Hi,
>
> I've configured apt-listbugs to run on Hurd.
>
> On execution from with apt, apt-listbugs is able to fetch Bug Reports but
> it freezes for ever on the message "Parsing Found/Fixed information...".
>
> The freeze is only for the app and can be interrupted.
>
> Please let me know if you
Package: apt-listbugs
Version: 0.0.82
Severity: normal
I've configured apt-listbugs to run on Hurd.
On execution from with apt, apt-listbugs is able to fetch Bug Reports but
it freezes for ever on the message "Parsing Found/Fixed information...".
The freeze is only for the app and can be interru
14 matches
Mail list logo
