Re: Debian Sources List Generator
On Tue, 11 Jun 2013 09:14:51 -0500
Cybe R. Wizard wrote:
> On Tue, 11 Jun 2013 01:38:35 -0700
> Alan Ianson <agianson@gmail.com> wrote:
>
> > On Tue, 11 Jun 2013 09:25:49 +0200 (CEST)
> > Pierre Frenkiel wrote:
> >
> > > On Tue, 11 Jun 2013, Alan Ianson wrote:
> > >
> > > > It looks like a mirror. Is it listed as such at
> > > > deb-multimedia.org?
> > >
> > > Yes, it is, alas.
> > > I already experienced that, as said by Chris Bannister
> > > "The deb-multimedia repository is toxic to a healthy wheezy
> > > system" It took me sevaral days to get rid of the mess introduced
> > > by this repo.
> > >
> > > I'll then have to install Ubuntu (at least as a virtual
> > > machine), as it is difficult nowadays to live without some
> > > packages which are missing in Debian.
> >
> > What mess did this repo make? I have been using deb-multimedia for
> > years and have never had any mess.
> >
> The latest Debian Project News email had this:
> ----------
> Expiration of debian-multimedia.org
> -----------------------------------
>
> debian-multimedia.org was a popular unofficial repository of Debian
> packages. Last year, this service moved to a new domain, and despite
> efforts from Debian, the debian-multimedia.org domain recently
> expired, and has now been registered by someone unknown to Debian.
> "This is a good example of the importance of the use of cryptography
> to secure APT repositories", DPL Lucas Nussbaum said [9]. The Debian
> project would like to emphasise the need to consider possible
> security issues when using third-party repositories and the
> importance of not blindly adding keys to the APT keyring.
>
> 9:
> http://lists.debian.org/debian-devel-announce/2013/06/msg00000.html
> ----------
I saw that, looks like some cyber squatter took the old domain over.
Christian Marrilat is a debian developer and works on a number of
things for debian aside from d.m.o. How he manages all the stuff he
does is beyond me but I appreciate all that he has done for debian and
it's users.
Reply to: