Fetching security updates for Dapper fails, as *smb* packages have wrong
access permissions on web server. Other updates were fetched properly.
I have tried getting them using wget and Firefox and it is the same, so
problem lies for sure on web server. Here is the message from Firefox:
"Forbidden
Am 17.11.2007 um 10:04 schrieb Krzysztof Lichota:
> Fetching security updates for Dapper fails, as *smb* packages have
> wrong
> access permissions on web server. Other updates were fetched properly.
Same experience on my Gutsy installation.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl
See https://bugs.launchpad.net/ubuntu/+source/samba/+bug/163042
basically a bad push and permissions were changed on the debs to
prevent them from being downloaded.
Wouldn't a new release without the broken packages fix the problem of
people trying to download something they can't?
--
Ubuntu-de
On Sat, Nov 17, 2007 at 08:21:54PM +1100, Serge de Souza wrote:
> See https://bugs.launchpad.net/ubuntu/+source/samba/+bug/163042
>
> basically a bad push and permissions were changed on the debs to
> prevent them from being downloaded.
>
> Wouldn't a new release without the broken packages fix t
Matt Zimmerman napisał(a):
> On Sat, Nov 17, 2007 at 08:21:54PM +1100, Serge de Souza wrote:
>> See https://bugs.launchpad.net/ubuntu/+source/samba/+bug/163042
>>
>> basically a bad push and permissions were changed on the debs to
>> prevent them from being downloaded.
>>
>> Wouldn't a new release
On Sat, Nov 17, 2007 at 12:14:41PM +0100, Krzysztof Lichota wrote:
> Matt Zimmerman napisał(a):
> > Preparing and testing a new update is something which takes time, and should
> > not be rushed. This temporary emergency measure (which is admittedly
> > confusing for users) prevents further downlo
Am 17.11.2007 um 11:33 schrieb Matt Zimmerman:
> - This regression only affects specific configurations (apparently
> those
> using the deprecated smbfs module)
Obviously a pretty common configuration, as I'm looking at a fresh
installation of the just released Gutsy Gibbon without additio
On Sat, Nov 17, 2007 at 12:57:32PM +0100, Markus Hitter wrote:
>
> Am 17.11.2007 um 11:33 schrieb Matt Zimmerman:
>
>> - This regression only affects specific configurations (apparently those
>> using the deprecated smbfs module)
>
> Obviously a pretty common configuration, as I'm looking at a fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Zimmerman wrote:
> The security team should follow up to ubuntu-security-announce to notify
> users who received the USN once they have prepared a response.
>
Updated packages are now available via security.ubuntu.com. The website
has been update
It seems like there has been a lot of complaints about how the
update-manager handles the 403 error. Considering the only time the 403
would normally occur is this situation, maybe the update manager could be
smarter about it?
On Nov 17, 2007 11:20 AM, Jamie Strandboge <[EMAIL PROTECTED]> wrote:
On Sat, Nov 17, 2007 at 11:24:07AM -0400, Cody A.W. Somerville wrote:
> It seems like there has been a lot of complaints about how the
> update-manager handles the 403 error. Considering the only time the 403
> would normally occur is this situation, maybe the update manager could be
> smarter abou
Reinhard Tartler wrote:
> Scott Ritchie <[EMAIL PROTECTED]> writes:
>
>> These are clearly not Wine bugs, but it's unclear to me where I should
>> refile them. Wine's exposing a bug somewhere else (probably the driver
>> or X), but what should I do?
>
> We haven't done that so far, but would tha
On Saturday 17 November 2007 15:13, Scott Ritchie wrote:
> It would be much more efficient if launchpad could just let me set a bug
> as still in need of triage rather than against the Wine package. I see
> no reason why I should have to file a separate bug containing the same
> information (and,
Scott Ritchie <[EMAIL PROTECTED]> writes:
> Reinhard Tartler wrote:
>> Scott Ritchie <[EMAIL PROTECTED]> writes:
>>
>>> These are clearly not Wine bugs, but it's unclear to me where I should
>>> refile them. Wine's exposing a bug somewhere else (probably the driver
>>> or X), but what should I d
For adding a task on an other package, I go to the pink 'Actions' menu
in upper left, click on 'Also affects distribution', choose 'Ubuntu'
as distribution in upper textbox, and the the package you guess the
bug apply in lower textbox. Then click 'continue' button.
I really suggest you guess the p
15 matches
Mail list logo
