[Bug 34376] Re: missing main/debian-installer in repo causes debmirror to fail
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. There are some inconveniences 1: using a different mirror server for the same repo (ex: hardy) will result in a complete download of the repo 2: a slightly complex directory structure If you want to use apt-mirror, here is what you can do: $ sudo apt-get install apt-mirror $ delete all the lines in /etc/apt/mirror.list and replace with the following: ==Cut Here= # config ## # set base_path/home/Repository-hardy # # if you change the base path you must create the directories below with write privlages # set mirror_path $base_path/mirror set skel_path$base_path/skel set var_path $base_path/var set cleanscript $var_path/clean.sh # set defaultarch running host architecture set nthreads 20 set tilde 0 # # end config ## deb http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu hardy-backports main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu hardy main/debian-installer restricted/debian-installer universe/debian-installer multiverse/debian-installer #deb http://archive.ubuntu.com/ubuntu hardy-updates main/debian-installer restricted/debian-installer universe/debian-installer #deb http://archive.ubuntu.com/ubuntu hardy-backports main/debian-installer #deb http://archive.ubuntu.com/ubuntu hardy-security main/debian-installer universe/debian-installer ==Cut Here= As you can see, the debian-installer for hardy-updates, backports and security have been commented out. This is because they are not available on the server yet (at the time of this writing). You need to check manually on the server occasionally and then enable them in the mirror.list file. This debmirror issue has not been resolved even after nearly 2 years. I hope that someone gets to fix it and make it a better alternative to apt-mirror. --NV -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34376] Re: missing main/debian-installer in repo causes debmirror to fail
** 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 to create a local mirror which in turn can be used + for netboot based installation in a LAN. + + When you try to create a mirror that includes: + + --dist=feisty,feisty-updates,feisty-security and --section=main,restricted,universe,multiverse,main/debian-installer - debmirror fails: - Won't mirror without dists/dapper-security/main/debian-installer/binary-i386/Packages.gz signature in Release at /usr/bin/debmirror line 1300. + debmirror fails with a HTTP 404 error. - cause main/debian-installer is only presente on dists dapper, the same - happens for breezy until a few days, but it seens some security/updates - appear for the debian-installer, and dists/breezy-security/main/debian- - installer was created. + The main/debian-installer section is needed for netboot installations. + When Feisty was started (or fro that matter dapper, edgy), the main + /debian-installer section was only present in feisty (but not in fesity- + updates, feisty-security). + + IMHO, this is not an issue with debmirror and creating the main/debian- + installer section for all the repositories on the server, by default, + will resolve the issue. ** Tags added: feisty gutsy -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34376] Re: missing main/debian-installer in repo causes debmirror to fail
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34376] Re: debmirror try to mirror section main/debian-installer on all dists
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34376] Re: debmirror try to mirror section main/debian-installer on all dists
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 packages so that
souces.list points to my local server instead of archive.ubuntu.com
(and installation requires almost no manual intervention). To that
extent, my debmirror configuration automatically fetches the following:
DIST=feisty
SECTIONS=main,restricted,universe,multiverse,main/debian-installer
I run the debmirror script every night in a cronjob so that it stays
updated with http://gb.archive.ubuntu.com. That means that updates that
come to feisty repo will automatically hit my local mirror. This
configuration allows me to install feisty with only the feisty repo
available (updates, backports and security updates not available in
local mirror and not available to clients).
But this means that the client has to use the internet and connect to
archive.ubuntu.com to download other repos (fesity-updates, feisty-
backports, feisty-security). I trust my LAN server and have no fear of
it getting compromised, so I would like to host all the repos (including
feisty-security) locally.
If I change the debmirror configuration to:
DIST=feisty,feisty-updates,feisty-backports,feisty-security
SECTIONS=main,restricted,universe,multiverse,main/debian-installer
It will try to download all updates but will fail when trying to get
main/debian-installer from feisty-security (or backports, updates).
Removing main/debian-installer will eliminate the problem, and all the
repos will be downloaded. But I won't be able to netboot and install.
(Note: debmirror automatically cleans the mirror, so anything that is
not in the DIST and SECTIONS will be removed. This means that I cannot
have 2 scripts; one to download main/debian-installer without all the
other repos and another script to download the other repos without main
/debian-installer)
FYI, in dapper, I am able to download all repos and the main/debian-
installer section since dapper-security has a main/debian-installer
section. But the section was added later, until which I had the same
problem as I described above.
Summarizing the usecase problem is that I if feisty-security does not
have a main/debian-installer section, local mirrors cannot serve feisty-
security to their clients. If they do add feisty-security, then they
will not be able to netboot and do automated installs.
Two possible solutions come to mind (and also suggested by Carlos Javier):
1. Modify debmirror to ignore repos that do not have main/debian-installer
2. Create main/debian-installer sections automatically for all repos
The second option sounds more simple and easy. (When feisty was
released, there was feisty-security available, but no packages in it.
This allowed the feisty ISO to enable the security repo without clients
getting any 404 errors. Later, when packages were added to feisty-
security, it trickled down to clients (through update-manager) without
any additional sources.list modification.
Hope that helped.
--NetVenture
FYI, here is my debmirror wrapper script for dapper:
#/bin/bash
DEST=/home/Repository-ubuntu-dapper
HOST=gb.archive.ubuntu.com
ARCH=i386
DIST=dapper,dapper-security,dapper-updates,dapper-backports
SECTION=main,universe,multiverse,restricted,main/debian-installer
/usr/bin/debmirror --dist=${DIST} --section=${SECTION} ${DEST}
# End of script
--
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77110] deskbar applet does not use theme background for Glider theme
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 is it an issue in Entry mode. ** Affects: deskbar-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- deskbar applet does not use theme background for Glider theme https://launchpad.net/bugs/77110 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77110] Re: deskbar applet does not use theme background for Glider theme
** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77110] Re: deskbar applet does not use theme background for Glider theme
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 background and history drop-down http://librarian.launchpad.net/5548569/Deskbar-hist.png -- deskbar applet does not use theme background for Glider theme https://launchpad.net/bugs/77110 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77110] [Updated] deskbar applet does not use new theme background until relogin
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/bugs/77110 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72967] pppoe-server compiled with incorrect path to pppd
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 is started, it chdir()'s to / and on receiving an auth request, it invokes the pppd binary from current dir (which is /). It should actually invoke /usr/sbin/pppd instead. A bug has been filed in debian but has been left unattended for long. This probably effects dapper too. This forum thread describes one practical instance of this problem: http://ubuntuforums.org/showthread.php?t=291926highlight=pppoe Debian Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380584 ** Affects: rp-pppoe (Ubuntu) Importance: Undecided Status: Unconfirmed -- pppoe-server compiled with incorrect path to pppd https://launchpad.net/bugs/72967 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68070] Re: Edgy: install to USB drive leaves system unbootable
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 CD. You need to use the alternate CD for this, IMO. --NV -- Edgy: install to USB drive leaves system unbootable https://launchpad.net/bugs/68070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68070] Re: Edgy: install to USB drive leaves system unbootable
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 CD. You need to use the alternate CD for this, IMO. --NV -- Edgy: install to USB drive leaves system unbootable https://launchpad.net/bugs/68070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
