will 0.4.9-1 get into Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/368419
Title:
apt-mirror i18n files
To manage notifications about this bug go to:
Will 0.4.9-1 get into Precise?
Does the fix correct the mirroring of the i18n packages?
(trying to rsync from postmirror.sh doesn't work reliably anyway.
Whatever the server(s) are that it rsyncs to have very limited
connection numbers... my rsyncs never succeeded reliably.)
--
You received
can you point me to the actual change... I don't see it under Raring or
Raring-proposed under source...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/368419
Title:
apt-mirror i18n files
To manage
SRU: thanks.
...but I meant, can you point me into a source repo/file/whatever that
shows the actual change which constitutes the fix...
apt-mirror isn't mission critical for me; I'll just smash the fix into
my installation (if possible.) I've no time to learn the SRU process and
to petition to
#448095 has over 80 comments -- I've read through it carefully several
times and I don't see that there's a clear, works-on-Lucid work around.
But that's ok -- jdthood's suggest above in comment 15 sounds like the
straightforward work around I was seeking. (Since I don't need the
dynamic feature
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
...just removing (apt-get purge resolvconf) the package fixes the
problem for me.
I don't need the /etc/resolv.conf file being dynamically modified.
Simply purge the package, remove the # this file is auto
...just removing (apt-get purge resolvconf) the package fixes the
problem for me.
I don't need the /etc/resolv.conf file being dynamically modified.
Simply purge the package, remove the # this file is auto generated...
comment in /etc/resolv.conf and my problem is solved.
--
You received this
...I'd be perfectly satisfied with a work-around. As it is, I've waded
through all the comments on this bug and all the dupes and there's just
a mess of try-this-try-that, etc. I suspect, I might be able to remove
the dns- options from my interfaces file, and then somehow disable/break
the auto
I have some 10.04 LTS systems which are afflicted by this, and some
which aren't.
Is there really no solution to this, in an LTS distro? Seriously?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
