Bug#505111: will suggest removal from testing
On Saturday 07 August 2010, Neil McGovern wrote: As there isn't a resolution in sight, I'll add a hint at the end of August for the removal of the package unless there's significant progress to fixing the issue. I still feel this is an overreaction as only the original reporter has ever seen the issue in practice. No one else has ever reported being affected by the issue. The described use case requires an combination of factors which is quite unlikely to occur in practice. I'm also CCing Colin Watson as he is the original author of rescue mode and its primairy maintainer. Maybe he'll be motivated to look into this or comment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590667: debmirror: fails to move installer MD5SUMS file in place on mirror
On Wednesday 28 July 2010, Stefan Kisdaroczi wrote: the file dists/squeeze/main/installer-i386/current/images/MD5SUMS didn't get updated on my mirror. The attached patch fixed it for me. Thanks for reporting the issue. The patch looks correct. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590993: installation-reports: netboot install report broken mirror if installation CD is used as mirror
tags 590993 patch thanks It would be better if debian-cd was modified to only include the symlink for the suite actually specified in the Release file. The attached patch (tested) implements this. diff --git a/tools/start_new_disc b/tools/start_new_disc index cf00344..779f242 100755 --- a/tools/start_new_disc +++ b/tools/start_new_disc @@ -66,9 +66,6 @@ fi if [ ! -d $CDDIR/dists/$CODENAME ] ; then mkdir -p $CDDIR/dists/$CODENAME -for name in stable unstable frozen testing; do - ln -sf $CODENAME $CDDIR/dists/$name -done fi # Commodity link for tools which want local in dists/local/local ... @@ -336,6 +333,12 @@ if [ -e $MIRROR/dists/$CODENAME/Release ] ; then sed -i -e s/^Suite: .*$/Suite: stable/ dists/$CODENAME/Release sed -i -e s/^Description: .*$/Description: Debian $DEBVERSION Released $RDATE/ dists/$CODENAME/Release fi + + # Create the suite symlink + SUITE=$(sed -n /^Suite:/ s/.*: //p dists/$CODENAME/Release) + if [ -n $SUITE ] [ x$SUITE != x$CODENAME ]; then + ln -sf $CODENAME dists/$SUITE + fi else echo ERROR: Release file ($MIRROR/dists/$CODENAME/Release) is missing ! exit 1
Bug#590993: installation-reports: netboot install report broken mirror if installation CD is used as mirror
reassign 590993 debian-cd severity 590993 normal thanks Since you are trying something that's not really supported, this is certainly *not* a grave issue. After all, a CD image is not a mirror even if both contain a repository. It is correct that the error occurs because CD images have symlinks for all suites to the release (codename) included on the CD. This is mostly for historic reasons and no longer has any purpose (since current versions of the installer select by codename instead of suite). In a bit more detail. The latest versions of choose-mirror (including the current Etch and Lenny versions) perform validity checks on the Release files and will reject a mirror as broken if the Release file under a suite symlink lists a different suite inside the Release file. It would be better if debian-cd was modified to only include the symlink for the suite actually specified in the Release file. Reassigning accordingly. Looks like my whole attempt to use the ISO image as netboot installation source is futile, as the files are not signed on the CD, so netinst gives up in the next step. This can be worked around by telling the installer to ignore the signatures. See the installation guide for details. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589579: debian-installer: i386 kernel flavour selection is poor
On Sunday 18 July 2010, Ben Hutchings wrote: 3. The 686 flavour is considered unsuitable for some AMD K7 processors Problem 3 appears to be due to a workaround for an incorrect kernel configuration. The comment on this exclusion is 'May not have SSE support', but this has never been a requirement for the 686 flavour. (The Pentium Pro and Pentium II don't have SSE either.) This has been discussed, changed, and revisited several times. There have been long threads about it and IIRC also various bug reports from users. Can you really *guarantee* that 686 will work with *all* K7 processors? I've not checked the archives, but I'm not sure whether SSE support really was the reason for the current code, or whether there were also other factors. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589579: debian-installer: i386 kernel flavour selection is poor
On Sunday 18 July 2010, Ben Hutchings wrote: + if grep -q '^flags.*\blm\b' $CPUINFO; then Has this been tested with busybox shell? Does busybox' grep understand '\b'? I don't recall us using it anywhere else in D-I. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589579: debian-installer: i386 kernel flavour selection is poor
On Sunday 18 July 2010, Ben Hutchings wrote: On Sun, 2010-07-18 at 23:11 +0200, Frans Pop wrote: On Sunday 18 July 2010, Ben Hutchings wrote: + if grep -q '^flags.*\blm\b' $CPUINFO; then Has this been tested with busybox shell? Does busybox' grep understand '\b'? I don't recall us using it anywhere else in D-I. This works with 'busybox grep' from the busybox package, so unless it is an optional feature it should work in d-i. OK. Thanks for verifying. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
On Saturday 17 July 2010, Petter Reinholdtsen wrote: I eagerly await Bills view on the proposed change for popularity-contest, which I believe i a better place to implement the change. No, it is not reasonable to ask packages to change functionally correct and policy-compliant dependencies only because of D-I [1]. popcon falls back to mail if the HTTP method fails, which does happen occasionally. Therefore a Recommends of an MTA is reasonable. Why do you feel the need to second-guess me on this? I spent several days analyzing the whole issue of Recommends and making various changes to deal with minor issues that arose from it. All changes where posted for review and discussed on the d-boot list. popcon is not the only package that needed an exception, so the --no-recommends option is needed anyway. Using it for popcon is a perfectly acceptable solution. So: as the reported issue is already fixed in current daily built D-I images and as the Recommends in popcon is functionally correct, there is absolutely zero need to make any changes in popcon. [1] The issue in D-I is mainly one of ordering: we install popcon before running tasksel and installing prio standard packages. The fact that we uninstall popcon if a user chooses not to participate is another weirdness in D-I which should not be reason to make any changes in the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
(Daniel: sorry for the private duplicate of this mail; no need to CC me.) On Saturday 17 July 2010, Daniel Richard G. wrote: On Sat, 2010 Jul 17 13:35+0200, Frans Pop wrote: So: as the reported issue is already fixed in current daily built D-I images and as the Recommends in popcon is functionally correct, there is absolutely zero need to make any changes in popcon. Okay, now I'm a little confused. So I see in the pkgsel ChangeLog that you addressed this back in late February. And I see that the current d-i downloads (netboot in particular) are dated early July, the same for both sid and squeeze. So why did this problem come up at all? Petter mentioned that version 0.26 of pkgsel was being used, but why would an early-July build of d-i use a version of pkgsel from last December? I'm not sure what image was used by the bug reporter, but I assume a current D-I alpha 1 image. The alpha1 images date from mid February. Until today, the version of pkgsel in testing was 0.26, which does not have my latest changes. This also means that current squeeze_d-i images still have the old version. As you can see from [1] my final work on Recommends handling in D-I was done _after_ the alpha1 release. I verified earlier today that with a daily built D-I image exim4 does not get pulled in when popcon is installed during pkgsel. Cheers, FJP [1] http://lists.debian.org/debian-boot/2010/02/msg00148.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
On Sunday 18 July 2010, Daniel Richard G. wrote: On Sat, 2010 Jul 17 21:40+0200, Frans Pop wrote: I'm not sure what image was used by the bug reporter, but I assume a current D-I alpha 1 image. The alpha1 images date from mid Februari. These received a refresh a few days ago: http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/curr ent/images/netboot/ No, that's no update. Only a date change for some reason. The images are still identical to the alpha1 release from February. One way to see that is to check the kernel version: it uses 2.6.30 instead of 2.6.32. Another is to check the /etc/lsb-release file or the versions of udebs listed in /var/lib/dpkg/status. But this same error would have occurred if I had used d-i from sid. When you say release, do you mean, from daily builds to unstable, rather than unstable to testing? The error would *not* have occurred if you had used images based on D-I from sid. If you look at http://www.debian.org/devel/debian-installer/, you will see three sets of links: - squeeze Alpha1 release (these are the ones you used) - current weekly snapshot - daily built images The first is the old release I was talking about and will soon be replaced with the new release. The second currently also still has the old version of pkgsel as weekly CD snapshots take udebs from testing and the current build is from last Monday (before the migrations of new versions done earlier today). The next build will use the new version (but is likely to be unusable because of the preparation for the new release which means that temporarily things from the old and new release will be mixed up and that is almost certain to cause breakage). The third set are the images that have the lastest version of all installer components from unstable. The page linked above is the only authoritative source for the various images available to install testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
On Sunday 18 July 2010, Daniel Richard G. wrote: So if I had used the one from http://http.us.debian.org/debian/dists/sid/main/installer-amd64/current/ images/netboot/ it would have worked? No. Those are *not* daily built images. Follow the relevant links from the page I referred to! For netboot you need other images. But it's identical to the one for squeeze... Correct. Both are the last D-I release, not daily builds. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588608: aptitude (priority important) depends on libboost-iostreams (priority optional)
Steve Langasek wrote: This manual represents the opinion of a single developer. And what does that have to do with the price of bananas in Iceland? The fact that aptitude is currently the recommended tool for package management has various reasons: user interface, features, dependency handling, etc. That status has evolved over the last 3 or so release cycles. You have even been part of some of the discussions (for example sarge - etch upgrade issues) aptitude is the primary tool used by Debian Installer (and because of that its current priority of important is actally necessary). It is also recommended in both the Release Notes (for stable release upgrades) and the Installation Guide. So what's listed in the Debian Reference is a correct reflection of aptitude's current status and not, as you imply, the result of some single developer being on crack. The growing dependency chain of aptitude *is* of some concern and may be reason to re-evaluate its role, but in no way does that change its _current_ status. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579954: installation-guide: Add link from accessibility section to boot screen section
tag 579954 pending thanks On Sunday 02 May 2010, Samuel Thibault wrote: It has been reported that it would be useful to add a link from the accessibility to the boot screen section, as the attached patch does, since the latter describes precisely how keypresses work there. I've added the link, but using a simpler change. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580508: installation-guide: Fix brltty driver/table code URL
tag 580508 pending thanks On Thursday 06 May 2010, Samuel Thibault wrote: The chapter numbers of the brltty manual have unfortunately changed. The attached patch points at its index instead of directly to a chapter number. Updated. I've used a different patch as IMO the text where the URLs are used needed updating too and because I don't like having two entities for the same URL. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
On Thursday 15 July 2010, Daniel Richard G. wrote: From the looks of it, exim4 is installed because of a Recommends: by the cron package: Recommends: exim4 | postfix | mail-transport-agent, lockfile-progs How exactly did you determine this? I doubt it is cron as Recommends are not installed during base system installation (debootstrap). The only correct way to check what pulls exim in is to check the syslog for the installation. Please send a (gzipped!) copy (you can find it on the installed system in /var/log/installer). Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589213: Do not install Exim in minimal system
On Thursday 15 July 2010, Petter Reinholdtsen wrote: I suspect the change you propose can not be implemented by debian-installer, but instead would have to be done by changing cron or any other package pulling in the mta package. At least the way d-i is designed at the moment. And on what do you base that statement? To make things simple: it's false. There are differences in the way Recommends are handled and options to tune whether Recommends are installed in some stages. Please make some effort to understand how things work before making wild guesses. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583388: Non-US keyboard problem with graphical installer
On Tuesday 06 July 2010, Cyril Brulebois wrote: 5. Fix for real: Edit /var/lib/dpkg/info/keyboard-configuration.config, and add the following line in ask_debconf(), right before the if part, once all choices have been merged together: choices=`echo $choices | sed 's/,$//'` Nice job tracing this. It's an error that crops up once in a while (in most cases because a comma _inside_ one (translated) option in the option list is not escaped and causes a count difference). The proposed fix could well be OK, but maybe the code can be fixed a bit earlier so the trailing comma is avoided in the first place? It's in general better to create the option list correctly than to clean it up afterwards. 'ask_debconf()' sounds like a rather general function that should be fed correct input rather than have this overhead. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583388: Non-US keyboard problem with graphical installer
On Tuesday 06 July 2010, Cyril Brulebois wrote: Frans Pop elen...@planet.nl (06/07/2010): The proposed fix could well be OK, but maybe the code can be fixed a bit earlier so the trailing comma is avoided in the first place? Whatever unbreaks g-i. Not really. There's also such things as doing things right or wrong, not to mention performance. If you care enough to investigate an issue like this, it takes only very little extra time to find the real trouble spot and fix things there instead of just papering over the real bug and making the code less efficient and maintainable than it already is. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586404: udev-udeb: Very slow installation in Squeeze caused by udevadm settle
On Sunday 04 July 2010, Petter Reinholdtsen wrote: Looks so, I never expected that the two packages could get out of sync. Is there some way to get the udevadm settle command work also with older udevd versions? Can the protocol be changed? This is a D-I release management problem and should IMO not be fixed any other way. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571939: [sparc] segfault when quitting aptitude
found 571939 0.6.3-2 thanks I can still reliably reproduce this segfault. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Petter Reinholdtsen wrote: In Debian Edu, we automatically search for error: in the installation log to detect errors during installation. Then it seems you need to make an exception for this error. When PXE installing, I get this one: Jun 28 23:18:29 main-menu[555]: (process:2840): wget: server returned error: HTTP/1.0 404 Not Found So, one wget results in a 404. As choose-mirror tries various possible suites and codenames and wgets are used for other purposes as well, a 404 is always a possibility. It is a bogus error message that is creating noise and confusion in the Debian Edu test installation. It's not bogus. It's a useful message for troubleshooting and debugging. The only thing that is a pity is that logging of the error messages to stderr gets delayed until the component completes. The URLs in the log seem to work, so I do not understand why wget is complaining. Is there some other wget calls that are not reported to the log? Did you check the code? The only wget calls I find in choose-mirror do not throw away error messages. Perhaps they should? If so, this untested patch should implement it: NACK. The errors are too useful to suppress. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Petter Reinholdtsen wrote: [Frans Pop] So, one wget results in a 404. As choose-mirror tries various possible suites and codenames and wgets are used for other purposes as well, a 404 is always a possibility. Sure, but all the URLs listed in the log are working, so it seem strange that one of them give 404. So either it's due to a temporary mirror issue (which you'd want to know about), or it's from an unlogged wget. Or it's from a wget from a subprogram called by choose-mirror, in which case you patch won't even help. It's not bogus. It's a useful message for troubleshooting and debugging. The only thing that is a pity is that logging of the error messages to stderr gets delayed until the component completes. It is bogus, as all the URLs in the log are working when I test them manually, and it is close to impossible to figure out what URL was failing. No, it's not bogus. There *is* a wget that's failing. Whether it affects the end result of the install or not is another matter. wgets in choose-mirror can fail for various valid reasons. Most of them you want to know about for troubleshooting purposes. Examples are: (temporarily) broken mirrors, incomplete mirrors, broken proxies. I've seen 403s and 404s that have helped a lot tracing the cause of failed installs. Removing valid information from logs for cosmetic reasons is wrong. The URLs in the log seem to work, so I do not understand why wget is complaining. Is there some other wget calls that are not reported to the log? Did you check the code? Yes. Only found the two mentioned in the patch, and neither seem to use a non-existing URL. :/ So, you'll need to look a bit deeper. Usually we fix the *cause* of errors. We don't suppress errors for cosmetic reasons. The only wget calls I find in choose-mirror do not throw away error messages. Perhaps they should? If so, this untested patch should implement it: NACK. The errors are too useful to suppress. I disagree. The error in question is almost useless. There is no way to see which URL was missing, and the message show up in the wrong location in the log. A useful error message would make it possible to figure out what is wrong. This one do not. :( But it's currently all we have! And, as mentioned before, it *has* helped me a number of times in the past, both while tracing issues from installation reports and while debugging. Improving the error handling is valid. Simply removing the messages without replacing them with something else (better) is plain wrong. If the error message continue to come from d-i, we need to filter it out in debian-edu, but I thought it best to try to get rid of it first. If you can't come up with a proper solution for choose-mirror then that is the correct way to go. The primary purpose of the syslog is to help users and developers to find the cause of issues. Removing real error messages for cosmetic reasons does not improve the installer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Frans Pop wrote: NACK. The errors are too useful to suppress. I disagree. The error in question is almost useless. There is no way to see which URL was missing, and the message show up in the wrong location in the log. A useful error message would make it possible to figure out what is wrong. This one do not. :( Note that the order of the errors does match the order of calls. Together with other info I've always been able to match things up properly. I agree (and said so in my initial reply) that the current situation is not ideal, but that does not make the errors useless. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586428: Please clear the apt cache
On Sunday 20 June 2010, Martin Michlmayr wrote: * Otavio Salvador ota...@ossystems.com.br [2010-06-19 12:35]: The following patch, which clears the cache after debootstrap and then again at the end (after kernel/extra packages), works for me. OK to apply? Conceptually it is OK but why not move it to post-base-installer.d? Well, my idea was to clean it twice, once after debootstrap and once at the end (after kernel and extra packages). Doing it in post-base-installer.d would not clean the kernel and extra packages. IMO it should only be done once during base-installer: at the very end (and only if successful). Doing it twice does not gain anything. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586434: Let's clean the apt cache
On Saturday 19 June 2010, Martin Michlmayr wrote: I see no reason for leaving .deb files in /var/cache/apt/archives on a fresh installation, so let's run apt-get clean before reboot. This has been suggested and discussed before. IIRC (but I may be mistaken) Joey has always been against it. The main reason IIRC is that leaving the packages makes it unnecessary to download them again if part of e.g. tasksel fails for whatever reason and the user has to install some packages manually (after ignoring that error - which is a real option as the base system should still be functional - and completing the installation). Think of a (partially) failed desktop install over a relatively slow network connection. IMO that argument is valid, but I also don't think that by itself it's enough to decide one way or another. I have no very strong feelings about this. Cleaning up is a good idea in general, but I don't think there is any huge gain in doing it here. I don't see any real problem with leaving the system admin responsible to do this cleanup (which he has to do anyway for any later package installs/updates). Any disk space savings are IMO illusionary as the cache will fill up again anyway during later updates and any system that does not have sufficient disk space to hold a decent package cache will also have serious problems during later stable updates. I can only see a real gain for installs to embedded systems that are not expected to be updated in any regular way. But those should not be installed using D-I anyway, or at least already always require some customized post-installation. Note also that this is not an issue for packages that are installed from CD as they are not copied to the cache. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586434: Let's clean the apt cache
On Sunday 20 June 2010, Frans Pop wrote: The main reason IIRC is that leaving the packages makes it unnecessary to download them again if part of e.g. tasksel fails for whatever reason and the user has to install some packages manually [...]. Note that the above argument is only really valid for packages installed *after* base-installer. If base-installer fails we generally consider the whole installation broken so only cleaning the cache at the end of that (and not also during finish-install) could be something to consider. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586434: Let's clean the apt cache
On Sunday 20 June 2010, Frans Pop wrote: Any disk space savings are IMO illusionary as the cache will fill up again anyway during later updates and any system that does not have sufficient disk space to hold a decent package cache will also have serious problems during later stable updates. I mainly mean upgrades from one stable release to the next (e.g. lenny - squeeze). Point releases and individual security updates are much smaller and thus less of a problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586434: Let's clean the apt cache
On Sunday 20 June 2010, Christian PERRIER wrote: Maybe, for more corner cases where keepign the cache would be good, could we have a low priority option (or a preseed-only choice) to *not* clean the cache? I don't think it has anything to do with user choice or preseeding. Making this a debconf option makes absolutely no sense IMO. The only reason I see to keep the cache is when some packages (after base-installer) fail to install. If we want to cover that case it should be detected automatically by testing the result of tasksel [1]. The final cleanup could be omitted in that case. [1] Checking installation of packages using apt-install is much harder to do as there are many different calls and failure may be expected in some cases. It also gains much less as their total size is much less. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586428: Please clear the apt cache
On Sunday 20 June 2010, Rick Thomas wrote: If you are *very* short of disk space, doing it twice might make sense. Nonsense. If you're that short on diskspace you have a totally unusable system anyway. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586434: Let's clean the apt cache
On Sunday 20 June 2010, Petter Reinholdtsen wrote: [1] Checking installation of packages using apt-install is much harder to do as there are many different calls and failure may be expected in some cases. It also gains much less as their total size is much less. I believe it would not be very hard. We would have to add code to apt-install, and to the udeb handling the queue updated by apt-install before base-installer is exeucted. No need to update all those calling apt-install for this. You missed the main point. apt-install can fail without there being an error (example: package being apt-installed isn't available; this is quite common). So you cannot test the result. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586428: Please clear the apt cache
On Saturday 19 June 2010, Martin Michlmayr wrote:
cleanup () {
+ rm -f /target/var/cache/apt/archives/*.deb 2/dev/null || true
rm -f $KERNEL_LIST $KERNEL_LIST.unfiltered
}
Shouldn't this call 'apt-get cleanup' in /target instead?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583733: tasksel: please install kde-config-tablet if a tablet is found
On Sunday 30 May 2010, Sune Vuorela wrote: Please install kde-config-tablet if a tablett (wacom-like)_is found and the user is installing kde task. Why not always, so that a wacom tablet that's plugged in later can still be configured? I guess that could be done. it was just 'why install it if not used'.. But then I looked in system settings and saw it showed up in the same category as 'joystick', which is installed by default and probably even more rarely used compared to a tablet. So I guess installing it unconditionally is okay. In that case it should be a Recommends from one of the KDE meta packages and not installed by tasksel. Please reassign accordingly. Note that tasksel *does* now install Recommends by default (if available). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583767: [xml/sgml-pkgs] Bug#583767: Add udeb
On Sunday 30 May 2010, Christian PERRIER wrote: Quoting Mike Hommey (m...@glandium.org): I don't know if all udebs are automatically included in d-i, but if they are, I doubt d-i people will like the additional 1.3MB uncompressed. They aren't automatically included. But udebs we don't use do need to be specifically excluded from inclusion on CD images (to keep the size of bc/netinst down as much as possible and to keep maximum space available for real packages on CD/DVD1). There is a cost. But in this case I don't think the cost is high enough to object to the udeb. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505609: [SOLVED] Unbootable after kernel upgrade: Lilo can't load kernel
reopen 505609 reassign 505609 linux-2.6 affects 505609 lilo thanks Stephen Powell wrote: The real question is, Why didn't the map installer get run during the kernel upgrade? [...] So is this a bug in the kernel maintainer scripts? Or is it a feature? I don't know. I'll leave that up to the kernel maintainers to decide. Reopening and reassigning to the kernel team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582223: partman - Wants to overwrite swap partition/lv
severity 582223 normal tags 582223 wontfix thanks On Wednesday 19 May 2010, Bastian Blank wrote: partman wants to overwrite the swap partitions on a already setup machine. As swap partition can contain hibernation data, this is an data-destroying operation. Doing any system install while the system is in hibernation is asking for trouble and IMO is simply user error. I don't think we need to support that case. See also the warning at the top of: http://www.debian.org/releases/testing/i386/ch05s01.html.en Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581873: [languagechooser] unable to select language more than once
*Exactly* when did you do this? I suspect it was after the step of loading additional components? Before that point changing the language should work fine. After that point the language setting *is* changed, but you get English because other translations have been deleted to save memory. I've committed a change in rootskel so that translations only get dropped if the system has less than 250MB RAM. If we could display the dialog saying that changing the language is no longer possible that would probably not be needed, but since that does not work I think it's better to just keep translations when possible. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581873: [languagechooser] unable to select language more than once
On Monday 17 May 2010, Holger Wansing wrote: The earliest possibility to reach the main menu in standard priority is when network configuration via DHCP fails or if I abort it before it succeeds. I would say it is during keyboard selection (if you ignore the localechooser dialogs). And you don't have to make DHCP fail; you can also go back to the menu when asked to confirm the hostname. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581873: [languagechooser] unable to select language more than once
reassign 581873 2.09 localechooser block 581873 by 470258 thanks On Sunday 16 May 2010, Holger Wansing wrote: If I remember now, that I wanted to do an italian installation (for example, every other choice does the same), and I go back to the change language step as soon as I can access the main menu, it doesn't work as expected. *Exactly* when did you do this? I suspect it was after the step of loading additional components? Before that point changing the language should work fine. After that point the language setting *is* changed, but you get English because other translations have been deleted to save memory. You can keep all translations for the whole installation by booting with DEBCONF_DROP_TRANSLATIONS=0 (IIRC). See changelog for cdebconf (0.117). I know, that it's maybe to late at that installation step to change the language, but shouldn't it be unpossible, to reach that dialogs then? That functionality is already there, but disabled because of #470258. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576576: option to skip installer for specific releases
On Monday 05 April 2010, Kees Cook wrote: In addition to the patches waiting in bug 455082, here is a patch to add a --skip-installer option to skip d-i files for specific dists (this is very handy for Ubuntu). Can you give an example of a debmirror command where this is needed? I tried with security.debian.org [1] which does not have a d-i section for lenny, but I don't get any errors (even without --dry-run). So it seems that non-existing sections are already skipped without any problems. Also note that if none of the dists that are being mirrored have a d-i section, then the easiest solution is to simply not specify it. [1] debmirror --dry-run --host=security.debian.org --method=http \ --dist=lenny/updates --root=debian-security \ --section=main,main/debian-installer \ --nosource --verbose --ignore-release tmp Mirroring to tmp from http://security.debian.org/debian-security/ Arches: i386 Dists: lenny/updates Sections: main,main/debian-installer Pdiff mode: use Will clean up AFTER mirroring. Attempting to get lock, this might take 2 minutes before it fails. Get Release files. [0%] Getting: dists/lenny/updates/Release... ok [0%] Getting: dists/lenny/updates/Release.gpg... ok gpgv: Signature made Tue 11 May 2010 09:27:15 PM CEST using RSA key ID 55BE302B gpgv: Good signature from Debian Archive Automatic Signing Key (5.0/lenny) ftpmas...@debian.org Get Packages and Sources files and other miscellany. dists/lenny/updates/main/binary-i386/Packages.gz needs fetch [ 2%] Getting: dists/lenny/updates/main/binary-i386/Packages.gz... ok dists/lenny/updates/main/binary-i386/Release needs fetch [100%] Getting: dists/lenny/updates/main/binary-i386/Release... ok Parse Packages and Sources files and add to the file list everything therein. [...] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580978: installation-reports: fails to see NIC firmware drivers on USB stick
On Monday 10 May 2010, Frans Pop wrote: On Monday 10 May 2010, Bonno Bloksma wrote: I have an ext2 formatted usb stick The installation guide specifies that the stick should be *FAT* (or VFAT) formatted. ext2 may work with some installation methods, but not with all. It is also important that the file is in a correct subdirectory. See http://d-i.alioth.debian.org/manual/en.i386/ch06s04.html for details. Also, check the syslog for the installation. It should contain info on how/where the installer is looking for the firmware. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581013: [debmirror] debmirror ignore the section 'debian-installer' for the distribution '.*-proposed-updates'
On Monday 10 May 2010, Philippe wrote: debmirror ignore the section 'debian-installer' for the distributions '.*-proposed-updates'. It is hardcoded in the debmirror script itself. Yes. You should be able to remove the test if you want to. Is there any raisons to do that ? In the past there have been times when proposed-updates suites did not contain debian-installer sections and thus would cause mirroring to fail. I think the solution is to remove the test and simply not fail if the section is missing (which could still happen after a release), but just print a warning. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576576: option to skip installer for specific releases
On Monday 05 April 2010, Kees Cook wrote: In addition to the patches waiting in bug 455082, here is a patch to add a --skip-installer option to skip d-i files for specific dists (this is very handy for Ubuntu). I don't like this. It's way too complicated for the problem. To be honest, I think the whole test is redundant and should just be removed (see also #581013). Instead of failing when a d-i section is missing we should just print a warning and skip it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579995: Partitioning failure in Squeeze install
On Monday 03 May 2010, Frans Pop wrote: On Monday 03 May 2010, Terry Stroup wrote: On completing the partitioning, I get the following error: File system has an incompatible feature enabled. Compatible features are has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or debugfs to remove features. This is an error from libparted. I'm not sure what the cause of the problem is and your setup is simply too complex with too many variables to deduce it from your description. If you can reproduce the problem, then please send the syslog and partman.log files for the installation (compressed!) after the first error occurs. Without the requested additional info we'll have no option but to close your report. Please check if you can reproduce this issue and provide the requested log files. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580799: linux-image-2.6.32-5-sparc64: Should include pata_cmd64x driver instead of cmd64x
Package: linux-2.6 Version: 2.6.32-12 Severity: serious Because of the IDE - ATA transition for Squeeze the pata_cmd64x driver should be enabled instead of the (old) cmd64x driver. AFAIK the pata_cmd64x has been tested and is known to work correctly. My system failed to boot after updrading to 2.6.32-12 because I had updated my bootloader config and fstab as per the debconf dialogs, but was still getting the /dev/hdX devices from the old driver. -- Package-specific info: ** Version: Linux version 2.6.32-5-sparc64 (Debian 2.6.32-12) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 Mon May 3 12:15:34 UTC 2010 ** Command line: root=/dev/hda2 ro ** Not tainted ** Kernel log: [ 34.412487] Unpacking initramfs... [ 36.425976] Freeing initrd memory: 8542k freed [ 36.428004] power: Control reg at 1fff1724000 [ 36.429219] audit: initializing netlink socket (disabled) [ 36.429481] type=2000 audit(2.160:1): initialized [ 36.430530] HugeTLB registered 4 MB page size, pre-allocated 0 pages [ 36.446641] VFS: Disk quotas dquot_6.5.2 [ 36.447294] Dquot-cache hash table entries: 1024 (order 0, 8192 bytes) [ 36.448042] msgmni has been set to 2016 [ 36.450085] alg: No test for stdrng (krng) [ 36.450673] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 36.450782] io scheduler noop registered [ 36.450847] io scheduler anticipatory registered [ 36.450913] io scheduler deadline registered [ 36.451104] io scheduler cfq registered (default) [ 36.451824] atyfb: 3D RAGE II+ (Mach64 GT) [0x4754 rev 0x9a] [ 36.453534] atyfb: 2M SGRAM (1:1), 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK, 67 MHz XCLK [ 36.516048] Console: switching to colour frame buffer device 144x56 [ 36.541375] atyfb: fb0: ATY Mach64 frame buffer device on PCI [ 36.542671] /SUNW,f...@1e,0: FFB at 01fc, type 51, DAC pnum[236e] rev[10] manuf_rev[1] [ 36.556761] [drm] Initialized drm 1.1.0 20060810 [ 36.557763] /p...@1f,0/p...@1,1/e...@1/s...@14,3083f8: Keyboard port at 1fff13083f8, irq 6 [ 36.558491] /p...@1f,0/p...@1,1/e...@1/s...@14,3062f8: Mouse port at 1fff13062f8, irq 7 [ 36.559586] f0061c64: ttyS0 at MMIO 0x1fff140 (irq = 5) is a SAB82532 V3.2 [ 36.560168] f0061c64: ttyS1 at MMIO 0x1fff1400040 (irq = 5) is a SAB82532 V3.2 [ 36.893614] Floppy drive(s): fd0 is 1.44M [ 36.910680] FDC 0 is a National Semiconductor PC87306 [ 36.912772] Uniform Multi-Platform E-IDE driver [ 36.913344] ide-gd driver 1.18 [ 36.914572] mice: PS/2 mouse device common for all mice [ 36.916206] rtc-m48t59 rtc-m48t59.0: rtc core: registered m48t59 as rtc0 [ 36.920416] TCP cubic registered [ 36.922175] NET: Registered protocol family 10 [ 36.927110] lo: Disabled Privacy Extensions [ 36.930640] Mobile IPv6 [ 36.930789] NET: Registered protocol family 17 [ 36.931687] registered taskstats version 1 [ 36.932518] rtc-m48t59 rtc-m48t59.0: setting system clock to 2010-05-08 17:43:06 UTC (1273340586) [ 36.932895] Initalizing network drop monitor service [ 37.102842] udev: starting version 153 [ 37.560607] PCI: Enabling device: (:01:01.1), cmd 2 [ 37.560667] sunhme.c:v3.10 August 26, 2008 David S. Miller (da...@davemloft.net) [ 37.567765] input: Sun Type 5 keyboard as /devices/root/f005f9c0/f00601b4/f0061504/f0063594/serio0/input/input0 [ 37.570655] input: Sun Mouse as /devices/root/f005f9c0/f00601b4/f0061504/f0064df4/serio1/input/input1 [ 37.580218] eth0: HAPPY MEAL (PCI/CheerIO) 10/100BaseT Ethernet 08:00:20:9c:14:f5 [ 37.613386] cmd64x :01:03.0: IDE controller (0x1095:0x0646 rev 0x03) [ 37.627752] cmd64x :01:03.0: 100% native mode on irq 14 [ 37.634742] ide0: BM-DMA at 0x1fe02c00020-0x1fe02c00027 [ 37.641890] ide1: BM-DMA at 0x1fe02c00028-0x1fe02c0002f [ 37.649158] Probing IDE interface ide0... [ 37.937464] hda: ST34342A, ATA DISK drive [ 38.613346] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [ 38.613792] hda: MWDMA2 mode selected [ 38.621602] Probing IDE interface ide1... [ 38.909368] hdc: Maxtor 6E040L0, ATA DISK drive [ 39.417005] hdd: CD-ROM 56X/AKH, ATAPI CD/DVD-ROM drive [ 39.425289] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [ 39.425427] hdc: MWDMA2 mode selected [ 39.433355] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [ 39.433451] hdd: MWDMA2 mode selected [ 39.441443] ide0 at 0x1fe02c0-0x1fe02c7,0x1fe02ca on irq 14 (serialized) [ 39.450618] ide1 at 0x1fe02c00010-0x1fe02c00017,0x1fe02c0001a on irq 14 (serialized) [ 39.459783] hda: max request size: 128KiB [ 39.468269] hda: 8404830 sectors (4303 MB), CHS=8894/15/63 [ 39.477020] hda: cache flushes not supported [ 39.486101] hda: hda1 hda2 hda3 hda4 [ 39.521765] hdc: max request size: 128KiB [ 39.541162] hdc: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63 [ 39.550586] hdc: cache flushes supported [ 39.561151] hdc: hdc1 hdc2 hdc3 hdc4 [
Bug#571939: [sparc] segfault when quitting aptitude
found 571939 0.6.2.1-2 thanks I can still reproduce this with the current version. Any updates on the issue? The offer to give access to my sparc box is still open. Thanks, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580265: Failed netinst
reassign 580265 linux-2.6 2.6.32-9 thanks On Tuesday 04 May 2010, Gmail Notifier wrote: 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit Network Connection [8086:10f0] (rev 06) Subsystem: Intel Corporation Device [8086:0037] Kernel driver in use: e1000e Comments/Problems: Did not find my e1000e network interface, even after selecting it explicitly from the list. After installing without using a net connection, a simple modprobe e1000e and dhclient made the net connection work. The following were added automaticly to /etc/modules by the installation: e100 e1000 e1000e But booting with these in /etc/modules did not make the network interface work. Had to do modprobe e1000e manually after each boot. This sounds like a kernel issue. Reassigning to the kernel team. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579995: Partitioning failure in Squeeze install
tag 579995 moreinfo thanks On Monday 03 May 2010, Terry Stroup wrote: On completing the partitioning, I get the following error: File system has an incompatible feature enabled. Compatible features are has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or debugfs to remove features. This is an error from libparted. I'm not sure what the cause of the problem is and your setup is simply too complex with too many variables to deduce it from your description. If you can reproduce the problem, then please send the syslog and partman.log files for the installation (compressed!) after the first error occurs. except that Squeeze's DI wouldn't mount the ReiserFS partitions. ReiserFS is no longer supported by default for Squeeze. See http://d-i.alioth.debian.org/manual/en.i386/ch06s03.html#di-partition -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579948: SunBlade 1000 installation report - fails to mount root partition on /target
reassign 579948 partman-base severity 579948 serious thanks On Sunday 02 May 2010, Jurij Smakov wrote: Comments/Problems: The display of partition sizes appears to be all screwed up (see the first attached screenshot). Possibly a regression in libparted for sparc disklabel. Please send the partman.log and also the output of 'fdisk -l' for that disk. Attempt to mount /dev/sdb2 as / on /target fails with invalid argument (see second attached screenshot). My guess is that it happens because mount gets an argument -t ext3, while the partition is ext4, and mounts fine from the shell if I do not specify a type argument. Perhaps, mke2fs default has changed without installer being aware of it? Not sure about this. Could also be related to the first issue. How exactly did you partition the disk? The first screenshot shows sdb2 as ext3, not as ext4. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579948: SunBlade 1000 installation report - fails to mount root partition on /target
reassign 579948 libparted0debian1 2.2-5 tags 579948 d-i affects 579948 partman-base thanks On Sunday 02 May 2010, Jurij Smakov wrote: On Sun, May 02, 2010 at 03:57:48PM +0100, Jurij Smakov wrote: ~ # fdisk -l /dev/sdb Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8864 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1 013 972801 Boot /dev/sdb2 2048 2049 1024 83 Linux native /dev/sdb3 0 8864 712000805 Whole disk /dev/sdb4 4096 4097 1024 82 Linux swap /dev/sdb5 6144 8864 21848064 83 Linux native Right. So the free space shown in partman *is* really there (although it shouldn't be). And sdb2 is completely wrong as it's way too small for a root fs. I think this may be the result of new partition alignment code in parted. The error is certainly in libparted as the log shows the following. Creation of first partition (100MB for /boot; looks OK): /bin/perform_recipe: IN: NEW_PARTITION =dev=sdb primary ext2 0-72908881919 beginning 10001 parted_server: OUT: 1 0-99614719 99614720primary ext2 /dev/sdb1 Creation of second partition (7GB for /): /bin/perform_recipe: IN: NEW_PARTITION =dev=sdb primary ext3 99614720-72908881919 beginning 71 parted_server: OUT: 2 16845373440-16846422015 1048576 primary ext3 /dev/sdb2 So partman requests a partition of 7GB, but libparted creates one of 1MB. Looks broken to me. The swap partition has the same problem: partman requests ~2GB, but we get only 1MB. Here's the fdisk output and illustration of the mounting error: ~ # mount -t ext3 /dev/sdb2 /target/ mount: mounting /dev/sdb2 on /target/ failed: Invalid argument This is a consequence of the error above. The syslog shows: May 2 17:12:42 partman: mke2fs 1.41.11 (14-Mar-2010) May 2 17:12:42 partman: Filesystem too small for a journal So, the FS is too small for a journal and therefore not a valid ext3 filesystem. But apparently ext4 is able to mount it (and you should also be able to mount it as ext2). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579625: partman-base: partman/alignment should also be a regular question
Package: partman-base A new template partman/alignment has been added which is currently only preseedable. During a discussion [1] it was suggested that the question should also be asked during interactive installs (at medium and/or low priority and only for relevant disk labels). The template is also not yet documented in the installation guide. [1] http://lists.debian.org/debian-boot/2010/04/msg00184.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566635: sysconfig-hardware: Inconsistent use of variables in hwup-ccw-group?
Attached the patch included in 0.0.9+nmu2. diff --git a/debian/changelog b/debian/changelog index d2d2da0..8fb6ea6 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,6 +3,7 @@ sysconfig (0.0.9+nmu2) unstable; urgency=low * Non-maintainer upload. * Allow for driver name change in sysfs for CTC network devices in Linux kernel 2.6.33. Closes: #566632. + * Correct variable use in hwup-ccw-group script. Closes: #566635. -- Frans Pop f...@debian.org Thu, 29 Apr 2010 10:50:24 +0200 diff --git a/etc/sysconfig/scripts/hardware/hwup-ccw-group b/etc/sysconfig/scripts/hardware/hwup-ccw-group index 2aecf13..491e7d6 100755 --- a/etc/sysconfig/scripts/hardware/hwup-ccw-group +++ b/etc/sysconfig/scripts/hardware/hwup-ccw-group @@ -15,7 +15,7 @@ read_config ccw $ID CCWGROUP_ID=$CCWGROUP_CHANS -if [ $name == cu3088 ]; then +if [ $NAME == cu3088 ]; then modprobe ctcm 2 /dev/null || : modprobe ctc 2 /dev/null || : @@ -26,7 +26,7 @@ if [ $name == cu3088 ]; then else error no kernel module for ctc devices available! fi -elif [ $name == qeth ]; then +elif [ $NAME == qeth ]; then modprobe qeth 2 /dev/null || : if [ -d $SYSFS/module/qeth ]; then
Bug#566632: sysconfig-hardware: Fails to bring up ctc network interface with kernel 2.6.33-rc5
Attached the patch included in 0.0.9+nmu2. diff --git a/debian/changelog b/debian/changelog index dc72b7d..d2d2da0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +sysconfig (0.0.9+nmu2) unstable; urgency=low + + * Non-maintainer upload. + * Allow for driver name change in sysfs for CTC network devices in Linux +kernel 2.6.33. Closes: #566632. + + -- Frans Pop f...@debian.org Thu, 29 Apr 2010 10:50:24 +0200 + sysconfig (0.0.9+nmu1) unstable; urgency=medium * Non-maintainer upload. diff --git a/etc/sysconfig/scripts/hardware/hwup-ccw-group b/etc/sysconfig/scripts/hardware/hwup-ccw-group index f3ed7b6..2aecf13 100755 --- a/etc/sysconfig/scripts/hardware/hwup-ccw-group +++ b/etc/sysconfig/scripts/hardware/hwup-ccw-group @@ -36,7 +36,7 @@ elif [ $name == qeth ]; then fi fi -ccw=/bus/ccw/drivers/$NAME +ccw=/bus/ccw/devices/$ID/driver ccwgroup=/bus/ccwgroup/drivers/$DRIVER message_n Configuring device $ID:
Bug#566629: sysconfig-hardware: Inconsistency for module ctc versus ctcm
Attached the patch included in 0.0.9+nmu2.
diff --git a/debian/changelog b/debian/changelog
index 8fb6ea6..f8fd3dc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,8 @@ sysconfig (0.0.9+nmu2) unstable; urgency=low
* Allow for driver name change in sysfs for CTC network devices in Linux
kernel 2.6.33. Closes: #566632.
* Correct variable use in hwup-ccw-group script. Closes: #566635.
+ * Also set buffer and protocol options both for the (old) ctc module and
+the (current) ctcm modules. Closes: #566629.
-- Frans Pop f...@debian.org Thu, 29 Apr 2010 10:50:24 +0200
diff --git a/etc/sysconfig/scripts/hardware/hwup-ccw-group b/etc/sysconfig/scripts/hardware/hwup-ccw-group
index 491e7d6..59b3ec1 100755
--- a/etc/sysconfig/scripts/hardware/hwup-ccw-group
+++ b/etc/sysconfig/scripts/hardware/hwup-ccw-group
@@ -95,16 +95,19 @@ write_setting () {
fi
}
-if [ $DRIVER = ctc ]; then
- write_setting buffer $CTC_BUFFER
- write_setting protocol $CTC_PROTOCOL
-elif [ $DRIVER = qeth ]; then
- write_setting portname $QETH_PORTNAME
- write_setting portno $QETH_PORTNO
- write_option fake_broadcast ${qeth_optio...@]}
- write_option fake_ll ${qeth_optio...@]}
- write_option layer2 ${qeth_optio...@]}
-fi
+case $DRIVER in
+ ctc|ctcm)
+write_setting buffer $CTC_BUFFER
+write_setting protocol $CTC_PROTOCOL
+;;
+ qeth)
+write_setting portname $QETH_PORTNAME
+write_setting portno $QETH_PORTNO
+write_option fake_broadcast ${qeth_optio...@]}
+write_option fake_ll ${qeth_optio...@]}
+write_option layer2 ${qeth_optio...@]}
+;;
+esac
echo 1 $SYSFS$ccwgroup/$CCWGROUP_ID/online
message ok.
Bug#571045: syslinux: Incorrect display of boot screen image in D-I
On Wednesday 14 April 2010, Daniel Baumann wrote: On 04/14/2010 02:56 AM, Cyril Brulebois wrote: Can we please get a fix? It's been a while since the very first image seen by people giving a shot to d-i is broken. since the change was done upstream wise on purpose, i think i'm sticking with fixing the image instead. debian-cd does not actually have the image. It is provided by D-I [1]. So IIUC someone will need to change the boot splash image from 640x320 to 640x480. [1] installer/build/boot/x86/pics/klowner.* -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577451: hw-detect: Should automatically install hardware related packages (RAID tools, printer drivers, fingerprint scanner tools, etc)
reassign 577451 pkgsel severity 577451 wishlist thanks On Sunday 11 April 2010, Petter Reinholdtsen wrote: For some kind of hardware, it would be very nice if the Debian installer automatically installed the packages to support the hardware in question. IMO this belongs in pkgsel, not in hw-detect. It has nothing to do with hardware detection as used in D-I itself. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577461: installation-guide: Updates to textmode activation
tag 577461 pending thanks On Sunday 11 April 2010, Samuel Thibault wrote: Samuel Thibault, le Sun 11 Apr 2010 22:58:39 +0200, a écrit : Squeeze apparently needs vga=0 in addition to fb=false, else the kernel switches to graphical mode very early. That being said, it could actually been considered as a regression, since fb=false used to be enough. It's not a regression but a necessary change since we now use VESA framebuffer by default for all x86 installs in order to have a better display resolution. The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. I've applied a modified version of both your patches. I've left out the virtualization bits as I don't think they belong in a section about accessibility and disabling framebuffer in general is already also documented in the general boot parameters section. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577461: installation-guide: Updates to textmode activation
On Monday 12 April 2010, Frans Pop wrote: The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. Actually, *maybe* we could remove the need for fb=false for x86 if we dropped support for the vga16 framebuffer driver. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576885: debhelper: Change to act only on relevant packages breaks builds
On Thursday 08 April 2010, Joey Hess wrote: That's few enough to manually review. I found these problems: - partconf (contains workaround for #572077 that can be removed) Updated in SVN. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576885: debhelper: Change to act only on relevant packages breaks builds
On Thursday 08 April 2010, Joey Hess wrote: Frans Pop wrote: This could of course be fixed with an arch test, but that would mean an extra cost of maintaining that arch test with changes in supported arches in debian/control. Or with a dh_listpackages test. (or a test -d) Right. Have fixed it that way for netcfg. On Thursday 08 April 2010, Joey Hess wrote: So, in balance, this change seems very likely to me to not cause anything except netcfg to FTBFS. It also clears up a source of build failures that can easily lurk in packages without anyone likely to notice until a user, on a little-used arch, tries to build the package from source. Thanks for doing the analysis. Feel free to close the BR if you're happy that the issue is dealt with sufficiently. Thanks, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576885: debhelper: Change to act only on relevant packages breaks builds
On Thursday 08 April 2010, I wrote: On Thursday 08 April 2010, Joey Hess wrote: Frans Pop wrote: This could of course be fixed with an arch test, but that would mean an extra cost of maintaining that arch test with changes in supported arches in debian/control. Or with a dh_listpackages test. (or a test -d) Right. Have fixed it that way for netcfg. Hmmm. dh_gencontrol still fails with the override netcfg has for it. Is that expected? debian/rules override_dh_gencontrol make[1]: Entering directory `/srv/project/d-i/trunk/packages/netcfg' dh_gencontrol -- -Vnetcfg:Depends= dpkg-gencontrol: error: current host architecture 's390' does not appear in package's architecture list (i386 amd64 alpha arm armel armeb hppa ia64 m68k mips mipsel powerpc sparc kfreebsd-i386 kfreebsd-amd64 hurd-i386 sh4) dh_gencontrol: dpkg-gencontrol -pnetcfg -ldebian/changelog -Tdebian/netcfg.substvars -Pdebian/netcfg -Vnetcfg:Depends= returned exit code 255 I can fix it of course by adding back the '-s' option there, but as essentially dh_gencontrol is still being called without options (the only option is end-of-options), I wonder if this isn't a bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576885: debhelper: Change to act only on relevant packages breaks builds
Package: debhelper Version: 7.4.16 Severity: important Tags: d-i I was happy to see the change to make debhelper only act on packages relevant to the current architecture as it allows to remove a workaround that was needed in netcfg after the switch to dh 7 [1]. However, it turns out that this change causes a new build failure in netcfg, again for s390. The binary package 'netcfg' is not built for s390, only netcfg-static. But debian/rules has the following: override_dh_installdebconf: dh_installdebconf (echo ; po2debconf debian/netcfg-common.templates ) \ debian/netcfg-static/DEBIAN/templates (echo ; po2debconf debian/netcfg-common.templates )\ debian/netcfg/DEBIAN/templates (echo ; po2debconf debian/netcfg-dhcp.templates )\ debian/netcfg/DEBIAN/templates (echo ; po2debconf debian/netcfg-static.templates )\ debian/netcfg/DEBIAN/templates This now fails with: debian/rules override_dh_installdebconf make[1]: Entering directory `/srv/project/d-i/trunk/packages/netcfg' dh_installdebconf (echo ; po2debconf debian/netcfg-common.templates ) \ debian/netcfg-static/DEBIAN/templates (echo ; po2debconf debian/netcfg-common.templates )\ debian/netcfg/DEBIAN/templates /bin/sh: cannot create debian/netcfg/DEBIAN/templates: Directory nonexistent make[1]: *** [override_dh_installdebconf] Error 2 make[1]: Leaving directory `/srv/project/d-i/trunk/packages/netcfg' make: *** [binary] Error 2 This could of course be fixed with an arch test, but that would mean an extra cost of maintaining that arch test with changes in supported arches in debian/control. The previous behavior made that unnecessary. I suspect there are many more packages that rely on the fact that general preparation of a binary has always been done even if the binary is not valid for the current arch and that this change may cause e.g. binNMUs to suddenly fail. Maybe not a good idea at this stage of the Squeeze release process. [1] http://svn.debian.org/wsvn/d-i/trunk/packages/netcfg/debian/?rev=61127sc=1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-rc3 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debhelper depends on: ii binutils 2.20.1-5 The GNU assembler, linker and bina ii dpkg-dev 1.15.5.6 Debian package development tools ii file 5.04-2 Determines file type using magic ii html2text 1.3.2a-14 advanced HTML to text converter ii man-db2.5.7-2on-line manual pager ii perl 5.10.1-11 Larry Wall's Practical Extraction ii perl-base 5.10.1-11 minimal Perl system ii po-debconf1.0.16 tool for managing templates file t debhelper recommends no packages. Versions of packages debhelper suggests: pn dh-make none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576206: debian-installer: [ppc] does not work with serial console
tag 576206 moreinfo thanks On Thursday 01 April 2010, Michal Suchanek hramr...@centrum.cz wrote: qemu-system-ppc -m 1024 -net nic -net tap,ifname=tap0,script=no,downscript=nomg -cdrom debian-504-powerpc-netinst.iso -boot d -nographic does not seem to do anything. Without -nographic a prompt on yellow screen appears where you can type something to boot an installer. I think this is an error in how you're trying to boot the installer or your qemu invocation rather than a bug. I don't really know anything about powerpc myself, nor how to use qemu for powerpc, so I suggest you ask on the debian-powerpc list for help. The installer does have serial console support and I'm not aware of any issues with that on real powerpc hardware. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576206: debian-installer: [ppc] does not work with serial console
On Thursday 01 April 2010, Michal Suchanek wrote: Changing the -boot d to -boot c gives access to the installed system with full serial support from the quik bootloader so I don't think this is the case. Can you provide the boot log for the installer somehow? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576206: debian-installer: [ppc] does not work with serial console
On Thursday 01 April 2010, Michal Suchanek wrote: I cannot run the installer without graphics. It could be that the installer is actually running but does not print anything on the serial port but I doubt that is the case because with graphics I have to type the name of the image to boot. Right, and that suggests to me that it's not an *installer* issue, but at most a bootloader configuration problem for the CDs. As I've said before, I (and most others on the Installer team) have zero knowledge of powerpc. Please try to find out what's wrong or needed on the d-powerpc list where all the port experts hang out. If a needed change is identified we'll be happy to help get it implemented. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558686: This bug now happens always
On Tuesday 30 March 2010, José L. Redrejo Rodríguez wrote: Since about ten days, I can reproduce always this bug using daily builds of squeeze images. I've also been using simple-cdd to do squeeze images, and the bug begun to appear since last tuesday. So there must be some package migrated to testing about those days that make it. I think the migrated to testing comment is incorrect. Daily built images use udebs from *unstable*, so it is quite likely to be related to the upload of the new parted to unstable, which happened about the time you indicate. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575947: 60-persistent-input.rules is missing in the udeb
On Tuesday 30 March 2010, Martin Michlmayr wrote: I just noticed that qcontrol in squeeze d-i doesn't work because /dev/input/by-path/platform-gpio-keys-event doesn't exist. Please include 60-persistent-input.rules in the udev so it's created. I suppose this may be because some of the persistent-input rules require libusb? For the graphical installer we created a (fairly large) extra udeb that contains persistent-input because X.Org needs it. The size of that udeb is I think related to the calls to 'input_id' and 'usb_id', which require libudev. However, this is a regression as the Squeeze udeb did support the simple by-path symlinks for platform devices, and AFAICT no external programs are needed for that. I'm not sure what the correct solution is here. Split up 60-persistent-input.rules in udev-udeb? Include the rule needed for the platform devices in qcontrol-udeb instead of relying on udev-udeb? Marco, what do you think? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575751: [rootskel-gtk PATCH] Only start X if we're using the GTK frontend.
tag 575751 pending thanks On Sunday 28 March 2010, Julien Cristau wrote: Subject: Only start X if we're using the GTK frontend. Also try to not start X clients before the server is ready to accept connections. Thanks. Committed. Will upload once ftp-master is alive again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575352: debmirror: spelling mistake in mirror_size
tag 575352 pending thanks On Thursday 25 March 2010, Prema wrote: -All numbers reflect the state of te archive per 19 Dec 2009. +All numbers reflect the state of the archive per 19 Dec 2009. Thanks. Will be fixed with the next release. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569348: example debmirror.conf contains useless $dry_run
On Thursday 11 February 2010, Piotr Lewandowski wrote: In contrast to $dry_run_var, this variable has no effect on debmirror. Please update example accordingly. Thanks for reporting this. I have fixed the problem differently from your suggestion. I think it makes more sense to keep the name in the config file similar to the option, so I have changed the internal use of the variable in the script. With the next version of debmirror setting $dry_run *will* work correctly. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574647: Likely solution - quotemeta
On Thursday 25 March 2010, David Venz wrote:
Tried this out and it appears to fix the problem:
sub first_set_with_package {
my ($package, $set) = @_;
+ # Escape any characters that will upset the regex below
+ $package = quotemeta($package);
foreach my $s (sort keys %$set) {
if ($$set{$s}{plist} =~ /(^|,)$package(,|$)/) {
return $s;
Thanks, but I've already committed a different solution, which effectively
does the same:
if ($$set{$s}{plist} =~ /(^|,)\Q$package\E(,|$)/) {
A similar change was also needed in a few other places.
Cheers,
FJP
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572605: still present -- installation-reports: Sid d-i on PowerPC can not find driver for network interface
On Wednesday 24 March 2010, Benjamin Cama wrote: I don't know the exact cause of this bug, but there is not enough informations (for me) to try to understand this bug. Could you give at least a dmesg result when in the installer ? And what exact message does it outputs when looking for the adapter ? There is no real bug. The only problem is that the images that are currently available are outdated. If you should build an image yourself, I expect it will work fine. This has already been explained in an earlier reply to this BR: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572605#17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505111: will suggest removal from testing
On Wednesday 24 March 2010, Robert Lemmen wrote: unless you object soon, i will suggest the removal of these packages from testing. the rationale is (a mixture of these will apply to the package in question) This package should not be removed. The bug is partly theoretical and only affects a minority of use cases. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505111: will suggest removal from testing
On Wednesday 24 March 2010, Robert Lemmen wrote: On Wed, Mar 24, 2010 at 02:51:41PM +0100, Frans Pop wrote: This package should not be removed. The bug is partly theoretical and only affects a minority of use cases. ok, so you think it should be squeeze-ignore? do you think it should be ignored for any release in the future? or downgraded? having bugs which are marked as grave, but at the same time are ignored forever seems like a slightly suboptimal usage of the BTS... I think it should be fixed, but that the bug is not sufficient reason for removal of the package. Unfortunately the D-I team is understaffed. Leaving the bug at it's current (technically correct) severity will maybe help get other people to take in interest in it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572605: still present -- installation-reports: Sid d-i on PowerPC can not find driver for network interface
On Wednesday 24 March 2010, Benjamin Cama wrote: OK. So, if it has not already been told (I didn't see much details about that in this BR) what steps should be taken for powerpc volunteers ? If you are not a Debian Developer I'm afraid you cannot help with this issue. However, there is plenty of other work that could be done to improve powerpc support in Debian Installer. Feel free to check the BTS for any open issues and work on them and submit patches. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#373253: #373253 libgcc_s.so.1 on AMD64 and PowerPC should be provided
tags 373253 wontfix thanks Because of the switch from DirectFB to X.Org as backend for the graphical installer I don't think this issue is relevant anymore. But I'm keeping the BR open for now for reference. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572605: still present -- installation-reports: Sid d-i on PowerPC can not find driver for network interface
On Wednesday 24 March 2010, Rick Thomas wrote: So how do we get this fixed? If it really is a problem on the buildd, who *can* fix it? Is there a list somewhere of who is responsible for which buildd? I've already provided that info a few times. For the centralized D-I buildds (which includes powerpc) Luk Claes and Otavio Salvador are the persons who set up the buildds and who are AFAIK the only people who currently have the access required to maintain the buildds. I have seen no mails from them on the d-boot list requesting help with that, so I can only assume they're still willing to maintain them (although the evidence seems to indicate otherwise). If it doesn't get fixed, there's not much point in claiming that Debian supports PowerPC architecture... Bullshit. I agree that it's a huge nuisance for testing and that the daily builds really should be available, but the alpha1 release works just fine (except for the known issues) and a next release will also not have this issue. For testing the current development status of the installer you could always build your own images. It's not that hard. Your point about not supporting powerpc is a gross exaggeration and to be honest I'm getting pretty tired of your repeating that any time *volunteers* don't jump quickly enough to your liking. So far I've also not seen that much actual help with arch-specific D-I development from the Debian powerpc community, despite repeated calls for help from our side. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575309: user-setup: Should stop adding first user to device access groups
On Wednesday 24 March 2010, Petter Reinholdtsen wrote: The code in user-setup-apply to add the first user to all the groups in passwd/user-default-groups should no longer be needed. I believe it should be dropped for Squeeze, or at least the default groups used should be trimmed down to nothing. What about (server) systems that don't have consolekit installed? What harm do the current group assignments do? After all, we're only talking about the first user here! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572605: still present -- installation-reports: Sid d-i on PowerPC can not find driver for network interface
(Dropping some CCs.) On Wednesday 24 March 2010, Norberto Feliberty wrote: However maybe that has changed and will test a sid build and see if it can find the network drivers to install. That will only work if you build your own images. If you can do that, great! The fact that the official daily built images (which use the current udebs from Sid) are outdated and therefore not usable is exactly the point of this discussion. The daily built images are normally linked from [1], but I have removed the links for the problematic architectures a few weeks ago for this very reason. Cheers, FJP [1] http://www.debian.org/devel/debian-installer/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575309: user-setup: Should stop adding first user to device access groups
On Wednesday 24 March 2010, Petter Reinholdtsen wrote: What about (server) systems that don't have consolekit installed? Yes, what about them? On such systems the first user would be left without expected default access to devices. If the local user to have special privileges, one should install the packages providing such privileges to the local user. There's more way than one to Rome. Group membership is a traditional and still valid way to provide rights. Having packages like consolekit installed is not a requirement. What harm do the current group assignments do? After all, we're only talking about the first user here! It grant local device access to a user that should not have it. The first user should not have local device access, unless that user is logged in locally on the machine console. Why should that user not have it? For the purpose of D-I installations the first user is defined as being the admin and/or console user of the system. If you install systems where the first user does not hold that role, you should disable creation of the first user account during installation, or tune the default groups he's made a member of. I disagree with this proposed change. IMO the default group assignments are in line with the purpose of the first user account. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575059: Should Package-Type be included in udebs or not?
On Tuesday 23 March 2010, Raphael Hertzog wrote: I'm a bit annoyed with lintian officializing usage of the non-official field name. It's counterproductive IMO. The issue should be resolved at the dpkg level. Unfortunately the underlying issue has never been resolved between Guillem and the d-i team, you can find the discussion here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452273 Please note that I have not promoted the lintian warning as I'm well aware of the background of this. From Cyril's PoV the lintian warning may have seemed logical, but I agree that the real issue is in dpkg which in the view of the D-I team should not include the field in the control file in packages, at least not for udebs. See my mail in reply to Cyril's proposal of the patch: http://lists.debian.org/debian-boot/2010/03/msg00190.html Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549681: needs MODULES=dep on some PowerPC systems
reassign 549681 base-installer severity 549681 normal tag 549681 help user debian-b...@lists.debian.org usertag 549681 powerpc thanks On Wednesday 24 March 2010, maximilian attems wrote: some OpenFirmware implementations, such as the one in the PegasosII, have a 12 MB size limit on kernel images, and no initrd loading capability. The latter is worked around by merging the initrd into the image with the mkvmlinuz tool, however the generated images are unbootable if they exceed 12 MB. It would be good if mkinitramfs would fail on systems that have the string platform: CHRP in /proc/cpuinfo if compressed kernel and initramfs together are larger than 12 MB, to stop unpleasant surprises when booting. partman has some checks for partitions, aboves specialised wish sound nice for debian installer although there are not many powerpc guys. Deciding on the MODULES= setting is done by base-installer. If somebody from the Debian PowerPC community can provide a tested patch for this we'll be happy to apply it. If help is needed developing the patch, feel free to ask on the debian-boot list. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574985: using the network even when I said no network mirror...
On Monday 22 March 2010, Holger Levsen wrote: If I dont configure a mirror for the regular system, I will mostly likely edit the sources.list myself anyway. And then I could also enable commented out entries for volatile and security... It could also be you're installing from DVD and not interested in a regular mirror, but that you do want essential updates... We consider security and volatile essential services. Users should not be left without them unless they really know what they're doing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575012: x86 architecture names are confusing
tags 575012 wontfix severity 575012 wishlist thanks On Monday 22 March 2010, Ben Hutchings wrote: The current installation and download links referring to 'AMD64' sometimes confuse users with Intel x86-64 chips, who instead select 'IA64'. This is a waste of time and bandwidth for all concerned. The name 'Intel x86' is also inaccurate in that the i386 architecture runs on 32-bit x86 processors from many vendors. I recommend the names '32-bit PC' and '64-bit PC'. It's a known issue and I appreciate your concern, but I'm not going to change this exclusively in the installation guide. The installation guide currently simply follows the terminology used for in general for the project. If it needs to be changed, then it needs to be done (in a coordinated fashion) for the whole distribution and not just for a single document. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574854: libklibc-dev: D-I rootskel FTBFS because of missing header files
Package: libklibc-dev Version: 1.5.16-1 Severity: serious The D-I package rootskel failed to build with this version and also after upgrading to 1.5.17-2 because header files could not be found. The cause was traced to the fact that instead of symlinks there are empty directories: $ ls -dl /usr/lib/klibc/include/linux drwxr-xr-x 2 root root 28672 Mar 18 16:21 /usr/lib/klibc/include/linux $ ls -dl /usr/lib/klibc/include/asm* drwxr-xr-x 2 root root 4096 Mar 18 16:21 /usr/lib/klibc/include/asm drwxr-xr-x 2 root root 4096 Mar 18 16:21 /usr/lib/klibc/include/asm-generic $ ls -l /usr/lib/klibc/include/linux total 0 $ ls -l /usr/lib/klibc/include/asm* /usr/lib/klibc/include/asm: total 0 /usr/lib/klibc/include/asm-generic: total 0 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31.1 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libklibc-dev depends on: ii libklibc 1.5.17-2 minimal libc subset for use with i ii linux-libc-dev2.6.32-10 Linux support headers for userspac libklibc-dev recommends no packages. libklibc-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574647: debtree: 'nested quantifiers in regex' when a package name contains +
Package: debtree
Version: 1.0.5
If a package name contains regexp characters, mainly +, the following can
occur:
Nested quantifiers in regex; marked by -- HERE in m/(^|,)g++ -- HERE (,|
$)/ at /usr/local/bin/debtree line 377.
sub first_set_with_package {
my ($package, $set) = @_;
foreach my $s (sort keys %$set) {
-- if ($$set{$s}{plist} =~ /(^|,)$package(,|$)/) {
return $s;
}
}
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#394719: About bug # 394719 in Debian BTS
On Thursday 18 March 2010, Olivier Vitrat wrote: Are you able to reproduce it with a recent version of the package ? If yes, which version ? It can still be reproduced with the Lenny version of kmail. No idea about Squeeze. If you want to know that, you'll have to try it yourself. If not, can we close this old bug report ? As it is an upstream issue anyway I have no huge problems with that. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574288: Please switch from DirectFB to X11
On Wednesday 17 March 2010, Cyril Brulebois wrote: please find attached the patch to switch from DirectFB to X11. See http://lists.debian.org/debian-boot/2010/03/msg00313.html for the details. --- src/lib/debian-installer.d/Makefile (révision 62665) +++ src/lib/debian-installer.d/Makefile (copie de travail) @@ -15,12 +15,8 @@ endif files = \ - S62directfb-hw-accel \ - S62directfb-cairo-workaround + S62Xorg This new file seems to be missing in the patch. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574336: pkgsel: Only run update-initramfs once during installation?
On Wednesday 17 March 2010, Petter Reinholdtsen wrote: This seem like a good optimization for the installation time to bring over to Debian, making sure update-initramfs is only executed twice during the installation instead of several times more In exactly which scenario would it be executed more than twice? I don't much like the patch either. Why doesn't it just use in-target to run update-initramfs? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574336: pkgsel: Only run update-initramfs once during installation?
On Wednesday 17 March 2010, Petter Reinholdtsen wrote: It is possible some of these are from setting up the LTSP chroot environment. Something looks very broken in this example. Why is initramfs-tools getting set up twice for the same version? Why is dmsetup getting installed if it is not being used during partitioning (in which case it should already have been installed _before_ initramfs-tools gets installed the first time)? After that the only remaining cause for an extra run is usplash. If debian-edu wants that installed by default, then the correct solution IMO is to include it on the first CD and ensure it gets installed during post-base-installer.d and not during pkgsel. The problem here IMO is a badly structured installation, not a missing feature in pkgsel. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574336: pkgsel: Only run update-initramfs once during installation?
On Wednesday 17 March 2010, Petter Reinholdtsen wrote: No idea. This what made me suspect the cause might be the LTSP chroot. Ah. I failed to really comprehend that earlier. Yes, I guess that could be and that would of course make it separate from base system installation Why is dmsetup getting installed if it is not being used during partitioning (in which case it should already have been installed _before_ initramfs-tools gets installed the first time)? It is a dependency of lvm2. I asked 'aptitude why dmsetup' on the machine in question. :) The same goes for LVM2 though. That should really be installed as a result of partitioning, not as an extra package. Or is that installed in the LTSP chroot as well? If it is the LTSP chroot that is the cause, then I think pkgsel really is the wrong place to address this. Oh, well. My goal for this request was a faster installation. I assume we share that goal, and do not see the point of arguing further for making sure update-initramfs is called as few times as possible. Sure. But that does not mean we should blindly complicate D-I code without checking the validity of the use case. P.S. I've been wondering if we shouldn't consider postponing kernel installation until after APT is configured. In some ways it is more logical to group it with bootloader installation than with base system installation. It could also make sense for firmware installation (see my comments in #574158). Not something to change lightly though. Added complication is consistent handling of Recommends. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574288: Please switch from DirectFB to X11
On Wednesday 17 March 2010, Julien Cristau wrote: On Wed, Mar 17, 2010 at 12:50:04 +0100, Cyril Brulebois wrote: --- /dev/null +++ b/src/lib/debian-installer.d/S62Xorg @@ -0,0 +1,2 @@ +Xorg -retro -noreset -nolisten tcp +export DISPLAY=:0 This is racy, we probably should do something better here. Hmmm. And it's also important to distinguish between debian-installer.d and debian-installer-startup.d correctly. debian-installer-startup.d: executed once when D-I boots debian-installer.d: executed after d-i-startup.d and respawned if the debconf frontend should crash So IIUC having it here means we run the risk of starting multiple servers. It seems to me that this should maybe go in debian-installer-startup.d, but that may require more changes in order to determine the frontend to be used early enough. Another solution could be to check if the server is already running and only start it if not. That could provide a restart of the X server if *that* crashes. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574407: os-prober does not detect 64bit systems like Fedora 64
tag 574407 pending thanks On Wednesday 17 March 2010, max wrote: os-prober does not detect 64bit systems like Fedora 64. The /usr/lib/os-probes/mounted/90linux-distro script only checks $dir/lib/ld*.so* but to detect Fedora 64 correctly it must check $dir/lib64/ld*.so* too. I've simplified that to just looking for $dir/lib*/ld*.so*. Thanks a lot for the report and proposing a patch. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574096: installation problem report
On Tuesday 16 March 2010, Paul Jurczak wrote: Comments/Problems: I'm experimenting with various distributions and I successfully installed Ubuntu, Puppy, Fedora from USB Flash to USB Flash. Debian is the first distro, where I had to go USB CD to USB Flash route. Debian supports all kinds of installation methods. Looks to me like you simply did not try the correct one. For installations from USB stick you should use the hd-media installation method. Please see our installation guide. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574096: installation problem report
Please always reply to the BTS, not to the person responding. On Tuesday 16 March 2010, you wrote: Thank you for quick response. Do you mean that copying hd-media/boot.img.gz and .iso image to USB Flash will result in different installation behavior than preparing USB Flash with LiveUSB Creator and plain .iso image? I have no idea what LiveUSB Creator does. But if it only uses what's on the image it cannot work since, as you noticed, the installation image included on that will look for a CD *drive* instead of for a CD *image*. The main feature of the hd-media installation image is that it looks for CD images. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573791: Installer fails due to invalid signatures
reassign 573791 installation-reports tag 573791 unreproducible needinfo thanks On Tuesday 16 March 2010, steve clark wrote: I sent a report to the debian bug reporting system (bug number 573791) but it seems to not have been taken serious, being shuffled between responsible owners. I see it differently: you have an installation problem that nobody else is having and have not quite found the correct way to report it. The reason your bug report was reassigned is that the original report had an incorrect syntax. So it is *not* being shuffled around; someone was merely trying to correct your incorrect initial reporting. And please understand that reporting an issue incorrectly drastically increases the chance that it will be missed! Happens with other lives debian based systems (e.g. ubuntu 9.10 server) too. Please report issues with Ubuntu installs to Ubuntu. I'm a novice Debian user (4 months), but have over 25 years across multiple systems and am a professional developer, so think I can recognise a must look at problem when I see one :) In that case I would also expect you to recognize when a problem is so completely unlikely to escape the attention of the project publishing the software that it may well by an issue that's solely due to the inexperience of the user? I can assure you that, if Lenny really was not installable, we would be flooded with reports. Fortunately that has not happened. The fact that you consistently see the issue could also be explained by the fact that you're doing something consistently wrong maybe. !! I have just tried an install using the 5.04 netinst and using the !! ftp.uk.debian.org mirror without any problems. There may have been a temporary problem with that particular mirror. If there was it appears to be solved now. Did you try different mirrors? I would further suggest that as it prevents any new installations of Debian since at least 11th March 2010, its serverity is a little higher than normal. *If* the issue is confirmed to be a real issue *and* really affects all installations and not simply one isolated mirror, then yes. Until then a much more appropriate categorization is unreproducible, needs additional info. Now, to try to solve your problem, assuming that you can still reproduce it, we will need additional information. Please send us the syslog of a failed installation. You should be able to save it using the Save debug logs option in the main menu of the installer. Please gzip the syslog before sending it and send your reply _only_ to 573...@bugs.debian.org. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573791: apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11
Please note this log is taken just now using: debian 5.04 netinst business card image I have just tried with the same image (for i386), using ftp.nl.d.o as mirror without any problems. My log looks similar to you, except that I get good signatures... From my log: Mar 16 17:41:08 choose-mirror[6970]: INFO: suite/codename set to: stable/lenny [...] Mar 16 16:42:18 main-menu[1044]: INFO: Menu item 'bootstrap-base' selected Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Signature made Fri Jan 29 23:18:35 2010 UTC using RSA key ID 55BE302B Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Good signature from Debian Archive Automatic Signing Key (5.0/lenny) ftpmas...@debian.org Mar 16 16:42:21 debootstrap: Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Signature made Fri Jan 29 23:25:01 2010 UTC using DSA key ID F42584E6 Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Good signature from Lenny Stable Release Key debian-rele...@lists.debian.org I wonder if somehow the files are getting corrupted during download. Can you copy the following two files from the installer after a debootstrap failure and send them: /target/var/lib/apt/lists/debootstrap.invalid_dists_lenny_Release /target/var/lib/apt/lists/debootstrap.invalid_dists_lenny_Release.gpg The first one should be zipped again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574158: firmware licenses never displayed
On Tuesday 16 March 2010, Joey Hess wrote: 3. Provide some way for firmware debs to communicate to d-i that they have a license the user needs to see, and have check-missing-firmware display these licenses before the firmware is ever used. This is the option that I have had in the back of my mind for some time. I think for really structural support of firmware, we could repackage it like we do for kernel modules and include meta data (partially? automatically generated) about the deb something was taken from + licence requirements. That would also allow to e.g. skip old versions of firmware. My personal opinion is that it should actually be quite OK to include non-free firmware *udebs* on (CD) images as long as - the licence in no way limits distribution; - we never allow use of any non-free firmware without explicit ack by the user. The *debs* should IMO always be either downloaded from a mirror (using standard apt-install) with fallback support for installing them from an external medium. Under those conditions I think the project might be persuaded to accept inclusion of firmware in D-I images and on CDs. We should of course keep support for loading firmware that does not match these criteria from external media. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#243857: Patch has been available in Ubuntu
tags 243857 + pending thanks On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. This code is in their current version of cdrom-detect and seems to work well in the exact same situation that d-i fails. Can we get this patch backported? Part of the patch is already in our code. I've ported the rest and done some additional refactoring. Will commit after testing in the next few days. I can do a NMU if there is no real maintainer willing to step up. An NMU (upload not from the D-I SVN repo) is never really a solution in the case of D-I as it tends to increase rather than reduce the work for maintainers. In general NMUs should not be needed where packages are maintained by a generally active team. It also seems not indicated in this case as this is the first time a patch has been suggested for the issue. Providing (preferably tested) patches against current SVN helps maintainers a lot more and is very much appreciated. Pinging maintainers on bug reports is also always appreciated. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#243857: Patch has been available in Ubuntu
Hi Joshua, On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. I can do a NMU if there is no real maintainer willing to step up. An NMU is not required (and does not really reduce the work of maintainers anyway). But a proper patch, preferably tested, that applies to the current version of the source package and that does not log messages saying Ubuntu would be most welcome. I would suggest changing the message to ... is not a valid installation CD (especially as it does not actually test if it is a Debian or Ubuntu CD; if you'd happen to have a Debian CD in one drive and an Ubuntu CD in the other, it would accept either...). Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#243857: Patch has been available in Ubuntu
On Tuesday 16 March 2010, Frans Pop wrote: On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. I can do a NMU if there is no real maintainer willing to step up. An NMU is not required (and does not really reduce the work of maintainers anyway). But a proper patch, preferably tested, that applies to the current version of the source package and that does not log messages saying Ubuntu would be most welcome. I would suggest changing the message to ... is not a valid installation CD (especially as it does not actually test if it is a Debian or Ubuntu CD; if you'd happen to have a Debian CD in one drive and an Ubuntu CD in the other, it would accept either...). Please ignore this mail. Apparently I had two versions open and by mistake also sent this early draft. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
