On Tue, 29 May 2007, Steinar H. Gunderson wrote:
It should be mentioned that at some point during this cycle, sid was indeed
in sources.list, but pinned away.
I believe the problem to be there. I also used a similar setup and
update-manager seems to happily ignore pinning. Or at least used to
On Mon, Jun 11, 2007 at 12:03:33PM +0200, Raphael Hertzog wrote:
It should be mentioned that at some point during this cycle, sid was indeed
in sources.list, but pinned away.
I believe the problem to be there. I also used a similar setup and
update-manager seems to happily ignore pinning. Or
On Mon, 11 Jun 2007, Steinar H. Gunderson wrote:
On Mon, Jun 11, 2007 at 12:03:33PM +0200, Raphael Hertzog wrote:
It should be mentioned that at some point during this cycle, sid was indeed
in sources.list, but pinned away.
I believe the problem to be there. I also used a similar setup and
Le lundi 4 juin 2007 16:23, Steinar H. Gunderson a écrit :
On Thu, May 31, 2007 at 02:35:50AM +0200, Steinar H. Gunderson wrote:
I don't have physical access to the machine; however, I've started a
tcpdump. I'll check in 24 hours or so what it actually has reported (I
guess update-notifier
On Thu, May 31, 2007 at 02:35:50AM +0200, Steinar H. Gunderson wrote:
I don't have physical access to the machine; however, I've started a tcpdump.
I'll check in 24 hours or so what it actually has reported (I guess
update-notifier will eventually ask for a new Packages file?).
It's been a few
On Tue, May 29, 2007 at 08:05:52AM -0400, Filipus Klutiero wrote:
I'd check if update-manager is using the sid source
in /usr/share/update-manager/channels/Debian.info
Or just monitor network activity while checking updates.
Yes, indeed, Debian.info shows getting sid from
Le mercredi 30 mai 2007 11:52, Steinar H. Gunderson a écrit :
On Tue, May 29, 2007 at 08:05:52AM -0400, Filipus Klutiero wrote:
I'd check if update-manager is using the sid source
in /usr/share/update-manager/channels/Debian.info
Or just monitor network activity while checking updates.
On Wed, May 30, 2007 at 06:24:17PM -0400, Filipus Klutiero wrote:
I think we misunderstand. /usr/share/update-manager/channels/Debian.info is
not a configuration file, but shipped by update-manager.
Ah, OK. It just looked a lot like a configuration file :-)
I also have http.us.debian.org in
Le mercredi 30 mai 2007 20:35, Steinar H. Gunderson a écrit :
On Wed, May 30, 2007 at 06:24:17PM -0400, Filipus Klutiero wrote:
I also have http.us.debian.org in that file, but my system does not seem
affected by the problem. What I wanted to ask is, can you deny/confirm
that the
On Mon, May 28, 2007 at 09:36:07PM -0400, Filipus Klutiero wrote:
When was the system installed?
It was installed as sarge while sarge was testing. Then it was held at sarge
for a while until etch froze, after which it was upgraded to etch. When etch
was released, it was continued to be held at
On Tue, May 29, 2007 at 11:22:49AM +0200, Steinar H. Gunderson wrote:
Would you be able to find which Packages update-manager uses?
Is this different from the regular apt Packages somehow?
FWIW, I checked the access logs of debian.samfundet.no (since I run it),
which is the mirror specified in
Le mardi 29 mai 2007 05:22, Steinar H. Gunderson a écrit :
On Mon, May 28, 2007 at 09:36:07PM -0400, Filipus Klutiero wrote:
Would you be able to find which Packages update-manager uses?
Is this different from the regular apt Packages somehow?
I don't know. Thanks for your check of the
Le lundi 28 mai 2007 18:23, Steinar H. Gunderson a écrit :
On Mon, May 28, 2007 at 05:51:06PM -0400, Philippe Cloutier wrote:
The system seems to have not only sid sources, but also experimental
sources (in addition to stable and testing). Please provide sources.list.
The bug was reported
13 matches
Mail list logo