Bug#636977: Boot-Repair sponsoring news ?
hi Axel, yes, still interest. You are correct: latest version is in the PPA. I can update the git if needed. Let me know if you need action or information from me. regards Yann 2015-04-10 16:20 GMT+02:00 Alessio Treglia : > Bella, > > On Fri, Apr 10, 2015 at 1:16 PM, Axel Beckert wrote: > > Is there still interest to bring boot-repair to Debian? > > I started to review the packaging quite a long ago, and afterwards I > have lost interest. > So Axel, please do take it under your wing if you like, I'd be more > than happy to see it entering main. > > Cheers! > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A >
Bug#554167: Upgrading mawk to 1.3.4
Best wishes for 2013 ! any progress concerning the update to mawk 1.3.4 ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683638: add-apt-repository adds invalid deb line if the rep contains a -
AFAIK, all repositories, even those not affected by this bug, have a slash (/). So this bug affects only reps with a dash (-) in its name. Anybody working on this?
Bug#685159: os-prober does not detect Fedora17
NEW ELEMENTS: - Debian testing and Ubuntu12.04 (os-prober 1.51) are affected by the bug: their os-prober detect Fedora16 but not Fedora17. - Ubuntu11.04 (os-prober 1.44) detects Fedora17 So the bug seems to be a regression of os-prober. And it seems to be restricted to the detection of Fedora17.
Bug#685159: os-prober does not detect Fedora
Package: os-prober Version: 1.51 Initially reported on https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1038093 The os-prober of Ubuntu does not detect Fedora when Fedora's partition is unmounted (which is frequent). Consequence: Fedora does not appear in Ubuntu's GRUB menu. WORKAROUND: mount the Fedora partition before doing update-grub in Ubuntu. Bug confirmed by several French users with Fedora17 and Ubuntu12.04 ( http://forum.ubuntu-fr.org/viewtopic.php?pid=9695571#p9695571 and http://forums.fedora-fr.org/viewtopic.php?id=57393 ).
Bug#685128: grub-install (1.99) fails with a 126 error code
Package: grub2 Version: 1.99-21 OS: Ubuntu 12.04 Originaly posted at https://bugs.launchpad.net/grub/+bug/1037922 The user (Rik = rufn) reported this problem: - Just before the problem appeared: Rik is not certain what he was doing but he may have disconnected a second hdd, he now only has one drive connected and had 2 earlier. He also installed the latest updates. - Then: the system failed to boot and gave message "unknown filesystem grub ???" - Attempt of GRUB repair: Rik ran Boot-Repair (from a Boot-Repair-Disk), and selected the recommended repair, which tried to reinstall GRUB via chroot into the installed Ubuntu (log: http://paste.ubuntu.com/1149152 ). As we can see in the log: - grub-install failed (MBR still points to sda6 when it should point to sda1) - grub-install returned a 126 error code
Bug#683638: add-apt-repository adds invalid deb line if the rep contains a / and a -
Package: python-software-properties Version: 0.82.7.2 STEPS TO REPRODUCE: 1. Add the PPA that contains a slash and minus with add-apt-repository: $ sudo add-apt-repository ppa:deluge-team/ppa 2. Removing the PPA with ppa-purge: $ sudo ppa-purge ppa:deluge-team/ppa 3. Again, add the PPA with add-apt-repository: $ sudo add-apt-repository ppa:deluge-team/ppa RESULT: The file '/etc/apt/sources.list.d/deluge-team-ppa-natty.list' now contains an invalid third line that says 'ain': $ cat /etc/apt/sources.list.d/deluge-team-ppa-natty.list deb http://ppa.launchpad.net/deluge-team/ppa/ubuntu natty main deb-src http://ppa.launchpad.net/deluge-team/ppa/ubuntu natty main ain Bug confirmed by 17 users: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/789859
Bug#554167: Updating Mawk in Debian
Dear all, any news about updating Mawk with the last upstream version? Regards Yann 2012/5/28 Gert Hulselmans > The Debian version of mawk has a lot of bugs (v1.3.3) > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=mawk;dist=unstable > > Thomas Dickey (other dev than the original mawk dev) has an improved > version of mawk (without those bugs): > ftp://invisible-island.net/mawk/ > > but for some reason the debian maintainer doesn't want to update. > > > Thomas Dickey: > > > If the Debian packager were responding, it would be about a week. > However, he's ignored most of my bug reports (aside from the one > about incorrect license). > > Look here - I've marked fixed-upstream on the ones that I believe are > done... > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk > > > https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/400409 > > > I use the fixed version of mawk a lot for my work. > > If you can force the debian maintainer to update mawk, I would be happy. > > I tried it a while back, but failed. > > One of my bug reports at Ubuntu (still not any comment on it): > https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/716920 > > It would be nice to get it bumped by somebody else. > > - Gert > > 2012/5/27 yannubu...@gmail.com : > > Hello Gert, > > > > Mawk package description says, that "Mawk is smaller and much faster than > > gawk". > > What about using Mawk instead of Gawk in BIS ? > > > > Regards > > Yann >
Bug#636977: Boot-Repair sponsoring news ?
Hi Alessio, Fabrice (another MOTU) is ok to upload Boot-Repair if you agree: https://bugs.launchpad.net/ubuntu/+bug/806291/comments/30 Please could you add a comment? Regards Yann
Bug#636977: Boot-Repair sponsoring news ?
>2012/2/14 Alessio Treglia >On Fri, Feb 10, 2012 at 8:09 PM, yannubu...@gmail.com > wrote: >> I updated the GIT with : >> - embarked g2s-gtk2, so that you can see the difference of packaging. (the >> pyGTK2 dependency is moved to the "boot-sav" package). >> - minor upstream fixes in gui-g2slaunch.sh and gui-update.sh > >Looks good, I'll have a further look later today. > >-- >Alessio Treglia | www.alessiotreglia.com >Debian Developer | ales...@debian.org >Ubuntu Core Developer| quadris...@ubuntu.com >0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A > 2012/2/22 yannubu...@gmail.com > > > 2012/2/22 Alessio Treglia > >> Yann, >> >> sorry for the unbelievable delay, I am in trouble with my examinations. >> >> On Tue, Feb 21, 2012 at 10:36 PM, yannubu...@gmail.com >> wrote: >> > is there any chance to see Boot-Repair integrated in the Precise ISO ? >> >> Sincerely I don't know, I'll have a look at it tomorrow. >> >> Regards, and please again apologize for the delay. >> > > > No problem. if you could just upload, i will try to ask the > FeatureFreezeException by myself. > > Good luck for your exams ! > Yann > Hello Alessio, any news? There is now Precise beta freeze, should i directly ask Feature Freeze Exception ? Regards Yann
Bug#658283: ITP: glade2script
Package: wnpp Version: 2.3.1 Upstream Author : Ansuz Peorth URL : https://launchpad.net/glade2script License : GPL Description : Glade interface engine for scripts Glade2script allows a script (bash, python or other) to display and interact with a GUI (created with Glade). Most of the opportunities offered by GTK are available. A terminal (vte) and/or webkit are integrable. One can also embed an external application that supports it natively, like mplayer or gvim. A plugin system was added to extend G2S capability. Documentation, many examples, and an interface giving access to the archive supports (simply launch presentation.sh). 2 versions are available: - GTK2 version is mature. It is already used by several softwares, such as Boot-Repair, OS-Uninstaller, Debeditor, DeskWall, GUnity, LaunchBash, Malokal, mkv_extractor_gui_v4, Screencastor, Sylaba2, Xee, Zenitor. -GTK3 version is in development.
Bug#636977: Boot-Repair sponsoring news ?
Hello Alessio, The GIT seems to be down, so i just continue updating the http://mentors.debian.net/package/boot-repair Yesterday i set the packaging to "non-native", as i am now working on Fedora and OpenSuse packaging too. Of course, i made the according changes, so that it is still lintian -E --pedantic clean. My priority is integration in Debian and Precise, so please give me news ! Regards Yann
Bug#636977: RFS: boot-repair ( 2nd try )
2012/1/12 > Dear mentors, > > I am looking for a sponsor for my package "boot-repair". > > * Package name: boot-repair >Version : 3.04 > Upstream Author : Yann Mrn (yannubu...@gmail.com) > * URL : https://sourceforge.net/p/boot-repair/home/Home/ > * License : GPLv3 >Section : admin > > It builds those binary packages: > > boot-repair - Graphical tool to repair boot problems > boot-sav - Librairies for Clean-Ubiquity, OS-uninstaller & Boot-repair > boot-sav-gui - Librairies for OS-uninstaller and Boot-repair > clean-ubiquity - Make the Ubiquity installer safer > os-uninstaller - Operating System Uninstaller > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/boot-repair > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/b/boot-repair/boot-repair_3.04.dsc > > > I took into account all remarks from last reviews: > - fixed /usr/share/clean (became /usr/share/boot-sav) > - fixed (removed) self-update > - fixed "X: boot-repair source: python-depends-but-no-python-helper > boot-repair"... > - fixed "temporary files created in an insecure way." (now uses mktemp) > - fixed the packaging in order to group the 5 binary packages (via > .install files) > > Package is lintian (--pedantic -E -i -I) clean. > > I would be glad if someone uploaded this package for me. > > Kind regards, > > Yann MRN >
Bug#636977: RFS: boot-repair (v3.04)
Dear mentors, I am looking for a sponsor for my package "boot-repair". * Package name: boot-repair Version : 3.04 Upstream Author : Yann Mrn (yannubu...@gmail.com) * URL : https://sourceforge.net/p/boot-repair/home/Home/ * License : GPLv3 Section : admin It builds those binary packages: boot-repair - Graphical tool to repair boot problems boot-sav - Librairies for Clean-Ubiquity, OS-uninstaller & Boot-repair boot-sav-gui - Librairies for OS-uninstaller and Boot-repair clean-ubiquity - Make the Ubiquity installer safer os-uninstaller - Operating System Uninstaller To access further information about this package, please visit the following URL: http://mentors.debian.net/package/boot-repair Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/boot-repair/boot-repair_3.04.dsc I took into account all remarks from last reviews: - fixed /usr/share/clean (became /usr/share/boot-sav) - fixed (removed) self-update - fixed "X: boot-repair source: python-depends-but-no-python-helper boot-repair"... - fixed "temporary files created in an insecure way." (now uses mktemp) - fixed the packaging in order to group the 5 binary packages (via .install files) Package is lintian (--pedantic -E -i -I) clean. I would be glad if someone uploaded this package for me. Kind regards, Yann MRN
Bug#636977: Packaging Boot-Repair with dh_install
Hello I updated sources, taking into account all comments from reviews. Now my problem is how to use dh_install . I would be happy if someone knowing dh_install packaging could help on this. As long as there is no solution with dh_install, i will use the only packaging solution i know (setup.py) to update http://mentors.debian.net/ , and propose for upload. Regards Yann
Bug#636977: Packaging Boot-Repair with dh_install
Dear all, does somebody know an example of package using dh_install ? (the one in manpage is not explicit enough for me). Thanks Thomas for your help. By the way, what alessio has to do with all this? > He helped for the packaging preparation ( created the GIT, and improved several files in the debian folder). > > # Initialize a new Git repo with upstream sources > mkdir boot-repair > cd boot-repair > tar -xvzf ../boot-repair_.orig.tar.gz > mv boot-repair-/* . > rmdir boot-repair- > git init > git add * > git commit -a -m "Added initial upstream sources v" > DONE, and pushed. ( http://anonscm.debian.org/gitweb/?p=collab-maint/boot-repair.git ) > > # Add the debian dir in a new branch > git checkout -b debian > echo "[DEFAULT] > upstream-branch = master > debian-branch = debian > [git-buildpackage] > export-dir = ../build-area/" >debian/gbp.conf > > [ ... add all your files in the debian folder ...] > > git add debian > git commit -a -m "Added initial debian folder" > DONE but when i push, i don't see where this branch is in the GIT !? > # Now you can build > git-buildpackage > this gives me errors: $ git-buildpackage dh_install gbp:error: You have uncommitted changes in your source tree: gbp:error: # On branch debian # Untracked files: # (use "git add ..." to include in what will be committed) # #debian/boot-repair.debhelper.log #debian/boot-repair/ #debian/clean-gui.debhelper.log #debian/clean-gui/ #debian/clean-ubiquity.debhelper.log #debian/clean-ubiquity/ #debian/clean.debhelper.log #debian/clean/ #debian/os-uninstaller.debhelper.log #debian/os-uninstaller/ nothing added to commit but untracked files present (use "git add" to track) gbp:error: Use --git-ignore-new to ignore. Regards Yann
Bug#636977: RFS: boot-repair
> Just FYI, you should use 2 branches, one for your upstream > code, and one containing that + the debian folder, so that > one can use "git-buildpackage". > > Cheers, > Thomas > i read the git-buildpackage man, but i'm sorry i don't understand what to change in the GIT, nor how to create a 2nd branch in it. Maybe this is something that only the GIT owner (Alessio) can change ? Regards Yann
Bug#636977: RFS: boot-repair
Happy new year ! I disabled the update from PPA, removed the setup.py, created the packages.install files, moved data to debian/tmp and changed the rule to %:dh_install --sourcedir=debian/tmp See http://anonscm.debian.org/gitweb/?p=collab-maint/boot-repair.git But now I get this error when i try to package: dpkg-genchanges: error: cannot read files list file: No such file or directory dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2 debuild: fatal error at line 1348: dpkg-buildpackage -rfakeroot -D -us -uc failed any idea? Regards
Bug#636977: Status of boot-repair, clean-gui , clean, os-uninstaller and clean-ubiquity packages
Hello Alessio, 2011/12/28 Alessio Treglia > Yann, > > don't worry, please merge the setup* scripts into a single one, let > the final setup.py install files in one-shot, I'll arrange things in > debian/* to create three different binaries (*.deb) by tuning > dh_install control files (debian/package1.install, > debian/package2.install and debian/package3.install). > > And no worries about python-support, we will use dh_python2 instead > since it is deprecated. > ok thanks ! > > So, please, let's merge all setup*.py scripts into a single one and > give me the lists of which files should be installed in which package. > DONE. The merged setup.py , and the 5 LISTS are at the root of the GIT ( http://anonscm.debian.org/gitweb/?p=collab-maint/boot-repair.git;a=tree ) Please note that there are now 5 binaries, not 3. *** In the meantime, I had a try for separate packaging, which gave me the following: http://mentors.debian.net/package/boot-repair http://mentors.debian.net/package/clean http://mentors.debian.net/package/clean-gui http://mentors.debian.net/package/clean-ubiquity http://mentors.debian.net/package/os-uninstaller I don't know what the errors (in the "QA information" zone) mean. I also don't know how to solve the "A watch file is not present" warning. *** For information: when I packaged via debuild -us -uc, Lintian was clean, but i saw the following warning: dpkg-deb: warning: 'debian/clean/DEBIAN/control' contains user-defined field 'Python-Version' any idea? *** Regards Yann
Bug#636977: Boot-Repair's GIT update - still need help for packaging
dear all, updated GIT tree: http://anonscm.debian.org/gitweb/?p=collab-maint/boot-repair.git I still need help to create Debian&Ubuntu packagings. Regards, and best wishes for this end of year :) Yann
Bug#636977: Status of boot-repair, boot-repair-common and clean-ubiquity-common
2011/11/5, yannubu...@gmail.com : > 2011/11/2, Alessio Treglia : >> Hi! >> >> I'd be interested in having this in Debian unstable soon, so how's the >> current status of these ITPs? >> Do you still have interest in doing the job? If you need help to >> handling the packaging or a mere sponsor, please don't hesitate to >> ask. >> >> I hope to hear from you soon, cheers! >> >> -- >> Alessio Treglia | www.alessiotreglia.com >> Debian Developer | ales...@debian.org >> Ubuntu Core Developer| quadris...@ubuntu.com >> 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 >> > > Hi Alessio, thanks for your interest in this tool. > Yes I still have interest in packaging it for Debian but I need help. > I use a software (LaunchBash) to do packaging for Ubuntu and upload to > PPA, but I don't know how to package for Debian, your help would be > much appreciated. > Boot-Repair needs 3 packages : boot-repair , boot-repair-common and > clean-ubiquity-common . Their sources can be found here: > https://launchpad.net/~yannubuntu/+archive/boot-repair/+packages . > They are made of Bash scripts, so i guess packaging should be quite > simple? > > Best regards > Yann , Boot-Repair & OS-Uninstaller developer Hello Alessio, Quick update: I am still failing to package for Debian (but succeed to create Precise packages in the PPA). For information, the ITP for clean-ubiquity-common is 637075, so the 3 packages needed for the software are: 636977, 637074, and 637075 Regards Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636977: Status of boot-repair and boot-repair-common
2011/11/2, Alessio Treglia : > Hi! > > I'd be interested in having this in Debian unstable soon, so how's the > current status of these ITPs? > Do you still have interest in doing the job? If you need help to > handling the packaging or a mere sponsor, please don't hesitate to > ask. > > I hope to hear from you soon, cheers! > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer| quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 > Hi Alessio, thanks for your interest in this tool. Yes I still have interest in packaging it for Debian but I need help. I use a software (LaunchBash) to do packaging for Ubuntu and upload to PPA, but I don't know how to package for Debian, your help would be much appreciated. Boot-Repair needs 3 packages : boot-repair , boot-repair-common and clean-ubiquity-common . Their sources can be found here: https://launchpad.net/~yannubuntu/+archive/boot-repair/+packages . They are made of Bash scripts, so i guess packaging should be quite simple? Best regards Yann , Boot-Repair & OS-Uninstaller developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#492493: When will su-to-root be available by default in Debian ?
Dear all, su-to-root is recommended by Lintian, but still not usable by default in Debian, causing confusion for users, and strange situations such as bug [1] and [2]. For memory, 2 alternative solutions were proposed in 2008's discussion [3] : - move su-to-root into debianutils where it would always be available, - or introducing an xdg-* utility into xdg-utils that does the same thing any update ? (I am developping graphical apps that need to be launched with admin privileges in live-session (whatever the DE), and because of this situation I think I will have to stick with gksu as dependency...) Best regards Yann [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492493 [2] https://bugs.launchpad.net/debian/+source/lintian/+bug/330533 [3] http://thread.gmane.org/gmane.linux.debian.devel.release/19273
Bug#637075: ITP: clean-ubiquity-common -- Common librairies for Boot-repair, OS-Uninstaller and Clean-Ubiquity
Package: clean-ubiquity-common Version: 3 Severity: wishlist Tags: needs-packaging clean-ubiquity-common contains common librairies for 3 tools : OS-Uninstaller, Boot-Repair and Clean-Ubiquity. Homepage: https://launchpad.net/os-uninstaller and https://launchpad.net/boot-repair
Bug#637074: ITP: boot-repair-common -- Librairies for OS-uninstaller and Boot-repair
Package: boot-repair-common Version: 3 Severity: wishlist Tags: needs-packaging boot-repair-common contains librairies for the 2 following tools: os-uninstaller and boot-repair Homepages: https://launchpad.net/os-uninstaller and https://launchpad.net/boot-repair
Bug#637073: ITP: os-uninstaller -- Small tool to uninstall any OS in 1 click
Package: os-uninstaller Version: 3 Severity: wishlist Tags: needs-packaging OS-Uninstaller is a graphical tool to uninstall any Operating System (Windows, MacOS, GNU/Linux...) Homepage: https://launchpad.net/os-uninstaller
Bug#636977: ITP: boot-repair -- Simple tool to repair boot problems
Package: boot-repair Version: 3 Severity: wishlist Tags: needs-packaging Boot-Repair is a little GUI to easily restore access to operating systems (reinstall GRUB bootloader, restore MBR, repare filesystems...) Homepage: https://launchpad.net/boot-repair
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
2011/7/24 Otavio Salvador > On Sat, Jul 23, 2011 at 16:45, yannubu...@gmail.com > wrote: > > Does NOT work ANY MORE: > > Now I have got it working again I think; it was a quoting issue. > Perfect, now it works !
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
> Hello, > > Talking with Colin at #debian-boot we found some possible corner cases > and then we end up doing some more changes. Please give this one a > final test so I can upload it. > Does NOT work ANY MORE: With /boot: $ LANG=C sudo os-prober ls: cannot access /media/Vista/Boot boot: No such file or directory /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux Without /boot: $ LANG=C sudo os-prober /dev/sda1:Windows Vista (loader):Windows:chain /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux Yann
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
2011/7/23 Otavio Salvador > On Sat, Jul 23, 2011 at 15:09, yannubu...@gmail.com > wrote: > >> I maked a fake environment and tested this patch locally and it seems > >> to work. Please give it a try and tell me. > > > > > > Sorry, in both cases (with or without /boot folder), I get this output: > > > > $ LANG=C sudo os-prober > > /dev/sda1:::chain > > /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux > > So now it has detected it but failed to handle description; the > attached patch ought to fix it. > Fixed in my config. Obrigado Otavio ! Yann
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
> > I maked a fake environment and tested this patch locally and it seems > to work. Please give it a try and tell me. > Sorry, in both cases (with or without /boot folder), I get this output: $ LANG=C sudo os-prober /dev/sda1:::chain /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
Opa! Output with /boot and patch: $ LANG=C sudo os-prober + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda1 + mpoint=/media/Vista + type=fuseblk + debug /dev/sda1 is a FUSE partition + log debug: /dev/sda1 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda1 is a FUSE partition + item_in_dir -q bootmgr /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 /media/Vista + item_in_dir boot/ /media/Vista + [ boot/ = -q ] + q= + grep -i ^boot/$ + ls -1 /media/Vista + boot=/media/Vista + item_in_dir bcd /media/Vista//media/Vista + [ bcd = -q ] + q= + grep -i ^bcd$ + ls -1 /media/Vista//media/Vista ls: cannot access /media/Vista//media/Vista: No such file or directory + bcd= + boot= + item_in_dir bcd /media/Vista/ + [ bcd = -q ] + q= + grep -i ^bcd$ + ls -1 /media/Vista/ + bcd= + count_next_label + require_tmpdir + [ -z /tmp/os-prober.u3aFGD ] + _labelprefix= + count_for + _labelprefix= + grep ^ /var/lib/os-prober/labels + true + _result= + [ -z ] + return + _cfor= + [ -z ] + echo 1 + echo + label= + result /dev/sda1:::chain + log result: /dev/sda1:::chain + cache_progname + logger -t 20microsoft result: /dev/sda1:::chain + echo /dev/sda1:::chain /dev/sda1:::chain + exit 0 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda2 + mpoint=/media/Perso + type=ext3 + debug /dev/sda2 is not a MS partition: exiting + log debug: /dev/sda2 is not a MS partition: exiting + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda2 is not a MS partition: exiting + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda5 + mpoint=/var/lib/os-prober/mount + type=fuseblk + debug /dev/sda5 is a FUSE partition + log debug: /dev/sda5 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda5 is a FUSE partition + item_in_dir -q bootmgr /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 /var/lib/os-prober/mount + item_in_dir -q ntldr /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^ntldr$ + ls -1 /var/lib/os-prober/mount + item_in_dir dos /var/lib/os-prober/mount + [ dos = -q ] + q= + grep -i ^dos$ + ls -1 /var/lib/os-prober/mount + [ -d ] + item_in_dir -q windows /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^windows$ + ls -1 /var/lib/os-prober/mount + exit 1 /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux Output with patch and without /boot: $ LANG=C sudo os-prober [sudo] password for yyy: + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda1 + mpoint=/media/Vista + type=fuseblk + debug /dev/sda1 is a FUSE partition + log debug: /dev/sda1 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda1 is a FUSE partition + item_in_dir -q bootmgr /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 /media/Vista + item_in_dir boot/ /media/Vista + [ boot/ = -q ] + q= + grep -i ^boot/$ + ls -1 /media/Vista + boot=/media/Vista + item_in_dir bcd /media/Vista//media/Vista + [ bcd = -q ] + q= + grep -i ^bcd$ + ls -1 /media/Vista//media/Vista ls: cannot access /media/Vista//media/Vista: No such file or directory + bcd= + boot= + item_in_dir bcd /media/Vista/ + [ bcd = -q ] + q= + grep -i ^bcd$ + ls -1 /media/Vista/ + bcd= + count_next_label + require_tmpdir + [ -z /tmp/os-prober.hRfoyP ] + _labelprefix= + count_for + _labelprefix= + grep ^ /var/lib/os-prober/labels + true + _result= + [ -z ] + return + _cfor= + [ -z ] + echo 1 + echo + label= + result /dev/sda1:::chain + log result: /dev/sda1:::chain + cache_progname + logger -t 20microsoft result: /dev/sda1:::chain + echo /dev/sda1:::chain /dev/sda1:::chain + exit 0 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda2 + mpoint=/media/Perso + type=ext3 + debug /dev/sda2 is not a MS partition: exiting + log debug: /dev/sda2 is not a MS partition: exiting + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda2 is not a MS partition: exiting + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda5 + mpoint=/var/lib/os-prober/mount + type=fuseblk + debug /dev/sda5 is a FUSE partition + log debug: /dev/sda5 is a FUSE partition + cache_progname + basename /usr/lib/os-probe
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
> > > I attached a new one and this is more verbose. Please test it. > Bom dia Otavio -> Output with the patch and the (empty) /boot folder : ~$ LANG=C sudo os-prober + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda1 + mpoint=/media/Vista + type=fuseblk + debug /dev/sda1 is a FUSE partition + log debug: /dev/sda1 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda1 is a FUSE partition + item_in_dir -q bootmgr + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 ls: cannot access : No such file or directory + item_in_dir -q ntldr /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^ntldr$ + ls -1 /media/Vista + item_in_dir dos /media/Vista + [ dos = -q ] + q= + grep -i ^dos$ + ls -1 /media/Vista + [ -d ] + item_in_dir -q windows /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^windows$ + ls -1 /media/Vista + item_in_dir windows /media/Vista + [ windows = -q ] + q= + grep -i ^windows$ + ls -1 /media/Vista + item_in_dir -q win.com /media/Vista/Windows + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^win.com$ + ls -1 /media/Vista/Windows + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda2 + mpoint=/media/Perso + type=ext3 + debug /dev/sda2 is not a MS partition: exiting + log debug: /dev/sda2 is not a MS partition: exiting + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda2 is not a MS partition: exiting + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda5 + mpoint=/var/lib/os-prober/mount + type=fuseblk + debug /dev/sda5 is a FUSE partition + log debug: /dev/sda5 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda5 is a FUSE partition + item_in_dir -q bootmgr + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 ls: cannot access : No such file or directory + item_in_dir -q ntldr /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^ntldr$ + ls -1 /var/lib/os-prober/mount + item_in_dir dos /var/lib/os-prober/mount + [ dos = -q ] + q= + ls -1 /var/lib/os-prober/mount + grep -i ^dos$ + [ -d ] + item_in_dir -q windows /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^windows$ + ls -1 /var/lib/os-prober/mount + exit 1 /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux ** -> Output with the patch and no /boot partition: ~$ LANG=C sudo os-prober [sudo] password for yyy: + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda1 + mpoint=/media/Vista + type=fuseblk + debug /dev/sda1 is a FUSE partition + log debug: /dev/sda1 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda1 is a FUSE partition + item_in_dir -q bootmgr + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 ls: cannot access : No such file or directory + item_in_dir -q ntldr /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^ntldr$ + ls -1 /media/Vista + item_in_dir dos /media/Vista + [ dos = -q ] + q= + grep -i ^dos$ + ls -1 /media/Vista + [ -d ] + item_in_dir -q windows /media/Vista + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^windows$ + ls -1 /media/Vista + item_in_dir windows /media/Vista + [ windows = -q ] + q= + grep -i ^windows$ + ls -1 /media/Vista + item_in_dir -q win.com /media/Vista/Windows + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^win.com$ + ls -1 /media/Vista/Windows + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda2 + mpoint=/media/Perso + type=ext3 + debug /dev/sda2 is not a MS partition: exiting + log debug: /dev/sda2 is not a MS partition: exiting + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda2 is not a MS partition: exiting + exit 1 + . /usr/share/os-prober/common.sh + cleanup_tmpdir=false + cleanup_ro_partitions= + progname= + type mapdevfs + partition=/dev/sda5 + mpoint=/var/lib/os-prober/mount + type=fuseblk + debug /dev/sda5 is a FUSE partition + log debug: /dev/sda5 is a FUSE partition + cache_progname + basename /usr/lib/os-probes/mounted/20microsoft + progname=20microsoft + logger -t 20microsoft debug: /dev/sda5 is a FUSE partition + item_in_dir -q bootmgr + [ -q = -q ] + q=-q + shift 1 + grep -q -i ^bootmgr$ + ls -1 ls: cannot access : No such file or directory + item_in_dir -q ntldr /var/lib/os-prober/mount + [ -q = -q ] + q=-q + shift 1 + grep -q -
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
2nd patch does not work either: patch and boot folder: ubuntu@ubuntu:~$ LANG=C sudo os-prober ls: cannot access : No such file or directory ls: cannot access : No such file or directory ls: cannot access : No such file or directory /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux /dev/sda6:Ubuntu 11.04 (11.04):Ubuntu1:linux ls: cannot access : No such file or directory no patch and boot folder: ubuntu@ubuntu:~$ LANG=C sudo os-prober ls: cannot access /media/Vista/Boot boot: No such file or directory /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux /dev/sda6:Ubuntu 11.04 (11.04):Ubuntu1:linux no patch and no boot folder: ubuntu@ubuntu:~$ LANG=C sudo os-prober /dev/sda1:Windows Vista (loader):Windows:chain /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux /dev/sda6:Ubuntu 11.04 (11.04):Ubuntu1:linux patch and no boot folder: ubuntu@ubuntu:~$ LANG=C sudo os-prober ls: cannot access : No such file or directory ls: cannot access : No such file or directory ls: cannot access : No such file or directory /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux /dev/sda6:Ubuntu 11.04 (11.04):Ubuntu1:linux ls: cannot access : No such file or directory all tests from live-usb
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
Thanks Otavio. Unfortunately, your patch does not solve the bug. Please see below the os-prober output I get in 3 configurations: 1) Normal output (no /boot folder in the Windows partition) : /dev/sda1:Windows Vista (loader):Windows:chain /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux 2) Output when there is a /boot folder in the Windows partition (without patch): ls: cannot access /media/Vista/Boot boot: No such file or directory /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux 3) Output when there is a /boot folder in the Windows partition (with your patch): /dev/sda5:Ubuntu 10.10 (10.10):Ubuntu:linux Remark : indeed even an empty /boot folder is enough to disturb os-prober. What this /boot folder contains does not change the result. I think the bug comes from the fact that os-prober looks inside the /boot folder but not inside the /Boot (or /BOOT) folder. Regards
Bug#634649: os-prober does not detect Windows if there is a /boot folder in the Windows partition
Package: os-prober
Version: 1.44ubuntu1
If the Windows partition contains a /boot/grub/core.img folder (this occurs
when beginners install GRUB by mistake in the Windows partition), os-prober
won't detect Windows any more.
I believe this is due to the fact that there are 2 folders with similar
names ("/Boot" and "/boot"), so os-prober just sees the /boot folder instead
of the /Boot or /BOOT folder coming with Windows)
I am using Ubuntu 11.04 32bits, but this bug has been also confirmed
with previous os-prober versions.
