Hi Osamu,

On Sat, Jan 24, 2009 at 05:09:03PM +0900, Osamu Aoki wrote:
> Package: apticron
> Version: 1.1.26
> Severity: normal
> 
> First some reminder: 
> 
> 1) I see this package has been updated with different package
> description at this stage of release.  The content you added is best
> suited in README.Debian. This may caused translation mismatch issue for
> the package description.

Thanks for reminding me. Indeed, it's not a good time to change package
description, you're right. However, by checking Debian Description Tracking[0] I
noted apticron has no translations for lenny. I think the current description
is adequate, although README file really still lacks useful information.

[0] http://ddtp.debian.net/ddt.cgi?desc_id=26565

> 2) To get this released for lenny, you need to write to
> [email protected] with "please unblock ..." mail with
> required information.

Sure. I'm just trying to address a bug reported in launchpad[1] that also
affects Debian. If I fix it next days, I push the new apticron version and ask
for unblock. It's just to not bother the release team twice without a good
reason. If I don't fix that bug, then I ask them to push the current apticron
to lenny. So, don't worry about it.

[1] https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/290386

> Now to the bug report.
> 
> I think this package should describe its value clearly to the user for
> the current APT system.  Let's look into situation.
> 
> It seems to me, this apticron package is a quick fix to the current apt
> feature which seems to lack capability to send mail for prompting users
> to install packages when it is configured to do download only.

Yes, it's valid point of view. I would add here the capability to:

  * warn the user about packages put in hold by aptitude/dselect[2]
  * integrate to apt-listchanges
  * be really simple to get it working

[2] http://pastebin.com/f204aa6c1

> Please note, APT package since 0.5.28 Ubuntu hoary and 0.5.29 Debian
> unstable (Sat, 13 Nov 2004) has its own script /etc/cron.daily/apt,
> which can do:
>  * fancy auto-clean with rule
>  * check and download upgradable packages automatically
>  * automatic unattended upgrade 
>     + need to install unattended-upgrades package
>     + aimed for security upgrade and have its blacklist capability
>     + mail capability (The extent of this, i do not know for sure?)
> 
> These can be enabled via apt configuration variables (usually stored in
> /etc/apt/apt.conf.d/02backup and 50unattended-upgrades).
> 
> Since this is enhancement script to apt, this should clearly document
> what part of apt this package will enhance etc.  Also recommending to
> install cron-apt without mentioning apt's own capability is not kind to
> the user.  We as users wonder why?  When it is written in package
> description, this impact is big.

Agreed. Once I improve the README file, the cron-apt suggestion should go out
from the package description.
 
> Let's compare these:
> 
>                    apt's cron script             cron-apt script
> 
> enable by          adding parameter              manually installing to cron
> 
> download only      shell script(main)            shell script
> 
> auto upgrade       python script                 shell script
>                    complicated checks            simple apt-get -y upgrade
>                    
> Except for cron-apt script depending on python for auto-upgrade, I see
> no reason to recommend it over apt.  At least both methods should be
> mentioned.
> 
> Although I have no relation with Ubuntu, considering Ubuntu uses this
> apt's feature extensively, I think this is quite stable part of code.
> 
> I am not very familiar with the whole picture.  So I think further study
> might be needed to be correct.
> 
> I hope to see more balanced documentation for what to do in
> README.Debian might be useful to everyone.

I'll try to compile all these info and improve apticron's README.Debian file. I
hope to get it for lenny.
 
> (Also, adding patch to apt itself to do what apticron does might benefit
> more people.)

Sure, have you pinged apt's devels about this issue? I've seen they got some
code from cron-apt for apt's cron script. Maybe apticron could help on some
part of this feature. I can't focus on this now.

Best regards,
 
-- 
Tiago Bortoletto Vaz
http://tiagovaz.org
0xA504FECA - http://pgp.mit.edu
GNU/Linux user #188687

Attachment: signature.asc
Description: Digital signature

Reply via email to