This worked well in my case! Thanks a lot!
jazzun4141 wrote on 2007-11-17: (permalink)
You have to open a terminal and then do:
sudo apt-get update
And then:
Sudo apt-get upgrade
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug noti
above packages are enabled and available to download.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
You have to open a terminal and then do:
sudo apt-get update
And then:
Sudo apt-get upgrade
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
@Neal
Thanks for expressing your understanding of this situation. I'm glad
there seems to be a consensus that this is important for general users
of Ubuntu. I now understand that I need to be patient for the fix to
hit the mirrors.
--
libsmbclient: upgrade fails with error 403
https://bugs.lau
@wgroiss - did you do sudo apt-get update first?
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Again, read the definitions of bug statuses
https://wiki.ubuntu.com/Bugs/Status
"Fix released" just means that the engineering work has been done and
released. Note that in some cases you may even have to dist-upgrade,
though not in this case. You may have to wait for a mirror update, you
may
@ itismike:
Yes, read my notes. I thought (wrong) that You don't know how to update
it, but I fully agree that such work-around doesn't deserve a "Fix
Released" status.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because
@ Neal McBurnett:
So it should be "Confirmed" or "In Progress", but not "Fix Released", as
the issue has not been fixed yet, has it?
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, wh
@m_gol:
I understand the command-line work-around. But work-arounds aren't
what mainstream Linux desktop users need. I think we're in agreement
that this needs to be 'fixed' to work with the default GUI update
manager before closing the bug.
--
libsmbclient: upgrade fails with error 403
https:
This is not fixed on the us server, even after an upgrade I still got
the 403s. Switching to the main repos fixes the issue.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Changing status back to "fix released". Invalid means that there was no bug to
begin with.
See also https://wiki.ubuntu.com/Bugs/Status
See this bug to learn about the automatic daily apt-get update process, and the
user interface issues with how to know if you really are up to date.
https://bu
The command-line upgrade works for me this morning on Dapper. Thanks!
I too, though, tried to upgrade a friend's system from Feisty to Gutsy
yesterday evening, and the entire upgrade failed just because of these
three files. The change to the repositories seems to have disabled a
lot more than j
@ itismike:
You have to open a console and write:
sudo apt-get upgrade
Then everything will be ok.
Bu that's what I'm talking about - You shouldn't force people to use
apt-get manually. They don't need to learn this.
** Changed in: samba (Ubuntu)
Status: Fix Released => Invalid
--
libsm
This is still broken - screenshots attached. Why is this bug marked as
'Fix Released'?
** Attachment added: "stillBrokenForGUI.tar.gz"
http://launchpadlibrarian.net/10455912/stillBrokenForGUI.tar.gz
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You rece
Super, but I can still see a problem. Yes, 'apt-get upgrade' works fine,
but Ubuntu update manager doesn't use 'apt-get upgrade'. Ubuntu is
oriented at usual people, that often want only to check e-mail, write a
document and talk to others. They don't have to realize that there is a
text console so
Updated packages are available for all releases. Please see
http://www.ubuntu.com/usn/usn-544-2 for more information.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Changed in: samba (Ubuntu)
Status: In Progress => Fix Released
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
WTF?
Here, too, still can't upgrade via the update manager, but apt-get works
fine
I agree with those above that it would have been much better to remove the
packages from the system than blocking all updates for a day
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad
Works not from gui, but from console:
GUI:
W: Beim Herunterladen der Datei
»http://security.ubuntu.com/ubuntu/pool/main/s/samba/smbclient_3.0.26a-1ubuntu2.1_i386.deb«
ist ein Fehler aufgetreten:
403 Forbidden
W: Beim Herunterladen der Datei
»http://security.ubuntu.com/ubuntu/pool/main/s/samb
Seems to be fixed at least for i386.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
As mentioned above; it really would be a good idea to remove the broken
security updates from the package. I am trying to upgrade from Feisty to
Gutsy and cannot because of the forbidden access. Also anyone attempting
to install the update will just get an error which cannot be good PR for
Ubuntu.
Synaptic show me this errors
W: Failed to fetch
http://security.ubuntu.com/ubuntu/pool/main/s/samba/smbclient_3.0.24-2ubuntu1.3_i386.deb
403 Forbidden
W: Failed to fetch
http://security.ubuntu.com/ubuntu/pool/main/s/samba/samba-common_3.0.24-2ubuntu1.3_i386.deb
403 Forbidden
W: Failed to
Please remove the broken security updates (and any items depending)
from the Packages and Sourcess, then regenerate the Release and GPG sigs
as Max suggested.
Doing this will do the following:
1. It will stop people from griping.
2. Allow canonical (or who ever is looking into the security update
Disabling the files by removing permissions is causing all apt-get
operations involving these files (e.g. an attempt to upgrade to
unrelated other security updates) to fail.
Wouldn't it be better to disable the update by removing it from the
Packages (and Sources) files (and regenerating the Relea
Just so everyone knows what is happening: Gutsy and Feisty packages are
ok and can be downloaded without problem. Edgy and Dapper packages have
been disabled due to a regression. Updated packages for Dapper and Edgy
will be provided soon.
--
libsmbclient: upgrade fails with error 403
https://bu
Turns out there were more problems with the patch and all releases have
been disabled. Updated packages for Dapper, Edgy, Feisty and Gutsy will
be provided soon.
--
libsmbclient: upgrade fails with error 403
https://bugs.launchpad.net/bugs/163116
You received this bug notification because you ar
There was a regression in the Dapper and Edgy packages, and this update
has been disabled. We are currently working on an updated package.
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jamie-strandboge)
Status: New => In Progress
--
libsmbclient: upgrade
27 matches
Mail list logo
