First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 121743
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Network Proxy Developers <net-proxy@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: David Morgan <david.morgan@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 121743 depends on: Show dependency tree
Bug 121743 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-02-05 15:06 0000 
I realise that this has only just been released, but there was also a 20060115
version (and possibly others), so I don't think you can complain about me being
impatient.


Renaming the previous ebuild and emerging worked for me - 20060115 was working
fine for me from about a couple of days after it was released, and 20060203
seems to have been working fine for about 10 minutes so far.

------- Comment #1 From Alin Năstac 2006-02-06 11:09:36 0000 ------- 
fixed in cvs.

don't expect frequent bumps on this one - all I can give you is one bump at
every 3 months or so.
if you want your adzapper to be as up2date as possible, run one of
/etc/adzapper/update-* scripts from cron... or join the dev team and claim
adzapper maintanership. ;)
First Last Prev Next    No search results available      Search page      Enter new bug