#399: Integration of Debian security updates
Susan Dridi wrote:
> 64 Studio wrote:
>
>> #399: Integration of Debian security updates
>> -------------------------------+--------------------------------------------
>> Reporter: qharley@wbs.co.za | Owner: free
>> Type: task | Status: new
>> Priority: high | Milestone: 2.1
>> Component: packages | Version: 2.0
>> Severity: major | Keywords:
>> -------------------------------+--------------------------------------------
>> The Debian Etch security updates should be integrated into 2.1 just before
>> release, so that all the security updates up to the release date is
>> included in the latest 64studio version. That way users that forgets
>> about the security updates, or those that only follows the Stable releases
>> also have access to the advantages of these updates to date.
>>
>
> I have a question on this. Should one normally have the following line
> in /etc/apt/sources.list.d/64studio.list :
>
> # Security updates
> deb http://security.debian.org/ etch/updates main
>
> And should it always be there, for example, when doing a dist-upgrade?
>
> I always comment out the Debian stuff and any other sources when doing
> that, but maybe I should always leave security in?
>
Hi Susan,
I believe that when doing a dist-upgrade it is best to have only the
64studio repository of choice activated. Just afterwards, enable the
debian security repository, and do a "mark all upgrades" in Synaptic,
and get the updates.
Common things updated regularly includes the Mozilla packages (Iceweasel
-dove etc) and other security loopholes.
Cheers,
Quentin
_______________________________________________
64studio-devel mailing list
64studio-devel@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel
|
