Re: what if a package needs to be "recalled"

2011-11-23 Thread Michael Gilbert
On Wed, Nov 23, 2011 at 7:43 PM, Michael Gilbert wrote: > On Wed, Nov 23, 2011 at 7:12 PM,  wrote: >>> "YP" == Yves-Alexis Perez writes: >> >> YP> I'm not sure telling people to use --no-sandbox without telling them >> YP> what they lose is a good idea. Sandboxing is here for a reason. > > I fi

Re: what if a package needs to be "recalled"

2011-11-23 Thread Michael Gilbert
On Wed, Nov 23, 2011 at 7:12 PM, wrote: >> "YP" == Yves-Alexis Perez writes: > > YP> I'm not sure telling people to use --no-sandbox without telling them > YP> what they lose is a good idea. Sandboxing is here for a reason. I find the "no-sandbox" label sufficiently descriptive, but for compl

Re: what if a package needs to be "recalled"

2011-11-23 Thread jidanni
> "YP" == Yves-Alexis Perez writes: YP> I'm not sure telling people to use --no-sandbox without telling them YP> what they lose is a good idea. Sandboxing is here for a reason. Wish it was documented. Say on the man page. Of course if they don't use it, they won't be able to browse anything

Re: what if a package needs to be "recalled"

2011-11-23 Thread Yves-Alexis Perez
On dim., 2011-11-20 at 20:56 -0500, Michael Gilbert wrote: > If this thread is specifically related to the broken sandbox in > chromium right now, then you can use "chromium --no-sandbox" until we > find an appropriate fix the bug (or help us do that). No need to come > up with crazy versioning so

Re: what if a package needs to be "recalled"

2011-11-20 Thread Michael Gilbert
On Sun, Nov 20, 2011 at 7:01 PM, peter green wrote: >> Or he can repackage 14.xxx as "15.xxx.1" but then other >> packages depending on > 14 etc. will get the version wrong and the >> numbering will be misleading. > > It's possible to use a version number like 15.xxx+really14.xxx but it's ugly > to

re: what if a package needs to be "recalled"

2011-11-20 Thread peter green
Just curious, let's say version 15.xxx of a package is released but then found to be faulty, and upstream isn't releasing a new version soon. OK.. faulty is a rather vauge term Can the developer somehow recall it? Not really, it's probablly theoretically possible to remove a package from

Re: what if a package needs to be "recalled"

2011-11-20 Thread Jonathan Nieder
Russell Coker wrote: > Isn't this one of the reasons for the epoch field? No. If chromium 14.0.835.202~r103287-1 actually worked[1], the thing to do would be to upload a package with version number 15.0.874.106~r107270+really14.0.835.202~r103287-1. That way, the blip in version numbering can be

Re: what if a package needs to be "recalled"

2011-11-20 Thread Russell Coker
Isn't this one of the reasons for the epoch field? -- My bloghttp://etbe.coker.com.au Sent from an Xperia X10 Android phone -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.

what if a package needs to be "recalled"

2011-11-20 Thread jidanni
Just curious, let's say version 15.xxx of a package is released but then found to be faulty, and upstream isn't releasing a new version soon. Can the developer somehow recall it? But then peoples' apts won't automatically catch 14.xxx as the new version if 15.xxx is already installed. Or he can rep