Use of the "general" and "base" packages (Re: general: after about 1 month...)
Hi Holger,
Holger Levsen wrote:
> On Sonntag, 24. Juni 2012, Jonathan Nieder wrote:
>> retitle 678519 after about a month, routing gets wedged
>> # not a general problem affecting a large portion of the archive
>> reassign 678519 base
>
> reassigning bugs from general to base is pretty useless, as both pseudo-
> packages bugs are "maintained" by the same persons...
>
> Basically the base-pseudo package is pretty useless as well, all it's
> (current) bugs should probabyl be carefully assigned to the kernel, for
> #678519 I just wasnt sure yet if its really a kernel or user configuration
> problem...
>
> The general pseudo-package has some approriate bugs OTOH.
>
> But mostly bugs filed against those two pseudo-packages really need to be
> assigned to a real package.
I figured the discussion of which package is resposible was more on
topic for virtual-pkg-base-maintainers@ than debian-devel@. Though I
could easily be wrong.
In any event, I reassigned the bug to the kernel a few minutes later.
Hoping that clarifies,
Jonathan
Reply to:
- References:
- Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- From: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
- Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- From: Henrique de Moraes Holschuh <hmh@debian.org>
- Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- From: Jonathan Nieder <jrnieder@gmail.com>
- Re: Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- From: Holger Levsen <holger@layer-acht.org>
- Prev by Date:
Re: Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- Next by Date:
Debian BSP, Dublin, Ireland
- Previous by thread:
Re: Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.
- Next by thread:
Bug#678572: ITP: foremancli -- commandline search interface to Foreman
- Index(es):