Ingo: Using 3 debmirror statements is ok as long as you don't cleanup
the mirror. But if you use a --cleanup (or post cleanup) then the last
debmirror statement will deem the files downloaded by the previous
statements as unneeded and hence, delete them.
Brak:
I've switched to using apt-mirror. T
** Summary changed:
- debmirror try to mirror section main/debian-installer on all dists
+ missing main/debian-installer in repo causes debmirror to fail
** Description changed:
- When you try to create a mirror that include:
- --dist=dapper,dapper-updates,dapper-security
+ Debmirror can be used
** Changed in: debmirror (Ubuntu)
Assignee: (unassigned) => MOTU
--
missing main/debian-installer in repo causes debmirror to fail
https://bugs.launchpad.net/bugs/34376
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
I'll try to describe this to be more easy.
I have a netboot setup in my LAN so that I can boot and install ubuntu
from the a local server. To netboot and install, the main/debian-
installer section needs to be available in my local mirror. I use
preseeding to configure mirror information and pack
More information added.
--
debmirror try to mirror section main/debian-installer on all dists
https://bugs.launchpad.net/bugs/34376
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The "File not found" error is probably due to an incorrect "root="
parameter. maybe you should try editing the grub configuration by typing
'e' and set teh root to /dev/sda1 or whatever (USB drives start with
sda).
Also, the ability to choose where GRUB is installed is not available in
the "normal
The "File not found" error is probably due to an incorrect "root="
parameter. maybe you should try editing the grub configuration by typing
'e' and set teh root to /dev/sda1 or whatever (USB drives start with
sda).
Also, the ability to choose where GRUB is installed is not available in
the "normal
I just noticed that the background color change does not take effect
immediately after a change of theme but does change if the applet is
reloaded or after logging out and logging in again.
PS: Updated Subject
--
deskbar applet does not use theme background for Glider theme
https://launchpad.net
Public bug reported:
Binary package hint: pppoe
SUMMARY: pppoe-server, which is part of the pppoe package tries to
invoke /pppd instead of /usr/sbin/pppd.
BACKGROUND:
When it receives an auth request from a pppoe client, the pppoe-server daemon
needs to invoke /usr/sbin/pppd.
After the daemon
Public bug reported:
Binary package hint: deskbar-applet
When I switch to the "Glider" theme, the deskbar (in button mode) does
not chanegt it's background color to match the panel's (GTK's) color. It
continues to maintain the "Ubuntu Human" theme color.
This is not a transparency issue. Neither
** Attachment added: "Image depicting difference in panel and applet background
colors"
http://librarian.launchpad.net/5548542/Deskbar-Bkground.png
--
deskbar applet does not use theme background for Glider theme
https://launchpad.net/bugs/77110
--
ubuntu-bugs mailing list
ubuntu-bugs@list
The screenshot was taken in Fiesty with deskbar package version
2.17.2-0ubuntu2.
I think the background for the history drop-down also uses the "Human"
theme color, but not sure if this is expected behavior. Attached image
shows the comparison.
** Attachment added: "Color difference between panel
12 matches
Mail list logo
