Your message dated Sun, 2 Dec 2018 21:23:15 +0100 with message-id <20181202202315.GA3120@crossbow> and subject line Re: Bug#827552: Package list updated has caused the Debian Bug report #827552, regarding Package list not updated since days to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 827552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827552 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Package list not updated since days
- From: Bernhard <bewoern1@gmail.com>
- Date: Fri, 17 Jun 2016 19:35:28 +0200
- Message-id: <1466184928.2451.7.camel@gmail.com>
Package: apt Version: 1.2.10 Severity: normal Since version 1.2.10, the package list is no more updated automatically. I have to update the package list manually with "apt-get update". In /var/log/syslog, there is the entry: systemd[1]: apt-daily.timer: Adding 10h 13min 50.543133s random time or similar. If you need more informations, please let me know. Best regards BernhardAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Bernhard <bewoern1@gmail.com>, 827552-done@bugs.debian.org
- Subject: Re: Bug#827552: Package list updated
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Sun, 2 Dec 2018 21:23:15 +0100
- Message-id: <20181202202315.GA3120@crossbow>
- In-reply-to: <99e3c6a09b24ec5389babeffbba50f0c56d29824.camel@gmail.com>
- References: <1466184928.2451.7.camel@gmail.com> <99e3c6a09b24ec5389babeffbba50f0c56d29824.camel@gmail.com>
Hi Bernhard, On Wed, Nov 28, 2018 at 06:50:39PM +0100, Bernhard wrote: > >From my point-of-view, this bug report can be closed. For the record, you can easily close your (or in fact any) bug by sending a mail to -done as I am doing now. That is in fact a very good way to contribute to Debian: Triaging bugreports. This way everyone can contribute to the great support everyone is expecting and deserving as that is how this opensource stuff works "behind the scene". > Thank you for the great support. I smell irony, but as the end of the year is approaching I will take what I can get as bug triage tends to be a rather thankless task otherwise. Thanks for the bugreport – even if you didn't get a reply it was surely put into consideration in the reworkings of the cronjob which happend in the meantime. Can't speak of myself in this case as I tend to skip over cronjob issues as I am not a user of it myself, but from experience I know that reading the reports tends to stick in the back of my head to be applied to good use later even if the original context is "lost". It would of course be nicer if every bugreport would get a reply instantly and/or be closed everytime we fix a related issue – at best also instantly with the reply – but in practice we (as in apt team) are too thinly staffed to do that. Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---