Re: help regarding whom excatly i should contact.
Hi! On Sun, Dec 04, 2011 at 12:14:47AM +0530, joy chalissery wrote: here is the link where is gave something in writing http://brainstorm.ubuntu.com/idea/28923/ please do read the comments following the idea admin talked about getting involved with development team. Thanks for your interesst in improving the software-center! I am not a programmer of expert level but would like to give some suggestions . Saw about the teams and categories. But no where there was a team which took in suggestions may be about a single software in bulk. i can do art,bit of programming, but more importantly give suggestion on improving which can be easily acted upon by developers. So the question is which team to join/ location of a suggestion box ? where i could contribute to ubuntu. There are various way to approach the software-center team, check http://launchpad.net/software-center, it links to the spec that has a subsection about how to contribute. We are keen to hear your ideas and we always welcome help! In addition to suggestions, the best is probably to start hacking at the source code, even if you are not a expert programmer. We are happy to help you getting started, there is the software-store-developers mailing list and the #software-center irc channel where we hang out and can help. The scarce resource for us is people working on the implementation of all the great ideas that are floating around. So every bit helps! Thanks, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu System Restore
On Sat, Oct 29, 2011 at 09:19:28PM +0530, Gaurav Saxena wrote: Hello Michael Hi Gaurav, sorry for my slow reply. On Fri, Oct 7, 2011 at 2:05 PM, Michael Vogt m...@ubuntu.com wrote: On Thu, Oct 06, 2011 at 05:15:14PM -0600, Bear Giles wrote: I've written a few prototypes and this comes down to four issues. Some of the details below are debian/ubuntu-specific but the same concepts will apply to redhat. [..] 2. Packages should NOT be backed up. All you need is the package name and version. Reinstall from .deb and .rpm if necessary since this way you're sure that you never restore compromised files. You may want to look at the apt-clone package for this part of the work, it supports creating/restoring this meta-data. Could you suggest something to me that how can I use apt-clone in my system restore program to backup the states of system packages. I read articles regarding that like http://swik.net/apt-clone which say that I need to have a ZFS file system for managing snapshots and also its just a front-end to apt-get. There is a unfortuate name clash here, the apt-clone that uses zfs on solaris is different from the one we have in the archive. Our apt-clone create a system-state file by capturing installed packages, auto-install states, sources.list etc. apt-clone --help should give a overview. Its possible to test using e.g. apt-clone restore --destination=/tmp/foo clonefile this will restore into a chroot dir. Careful otherwise, the default restore location is /. Cheers, Michael Cheers, Michael On Fri, Sep 30, 2011 at 12:01 AM, Gaurav Saxena grvsaxena...@gmail.com wrote: Hello Aaron Thanks a lot for your quick reply. On Fri, Sep 30, 2011 at 10:03 AM, Aaron C. de Bruyn aa...@heyaaron.comwrote: In Windows, the ability to snapshot is built into the filesystem. In Linux, you must be running a filesystem that supports snapshots. I know LVM supports snapshotting and I believe BRTFS has support, but other than that I'm not sure. Yes I read the logic behind windows system restore. But I think we can take some other approach for this, that will be better as all users won't be able to spare an extra partition formatted brtfs. Basically, your program would have to check the file system that is used on the computer (remember Linux can have many types of file systems mounted at the same time), then (in the case of LVM) make sure there's enough free space to snapshot, and finally take the snapshot. Ok. Do I have to snapshot the whole system partition / important system files to the brtfs partition ? When the snapshots start filling up, you would either need to delete them or detect the low space and resize them. In my personal opinion, snapshotting in Linux is currently a pain in the rear. It sounds like BTRFS could change that, but it's still a ways off. Ok. I will try another approach that will be better as suggested by people here. -A On Thu, Sep 29, 2011 at 21:00, Gaurav Saxena grvsaxena...@gmail.com wrote: Hello all, I want to write a windows system restore like program for ubuntu , which will have options for creating restore points for the system and then restoring it back to that point. Also I will as an extension provide support for older version of a file as is in windows currently. I need your help to find how to start with this in ubuntu. I know that I have to snapshot the system when creating a restore point and then restore it. I need some starting pointers so that I can start doing this work. Also if this has already been done please inform me. I got this idea from https://wiki.ubuntu.com/SystemRestore. -- Thanks and Regards , Gaurav -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Thanks and Regards , Gaurav -- Thanks and Regards , Gaurav -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Thanks and Regards , Gaurav -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu System Restore
On Thu, Oct 06, 2011 at 05:15:14PM -0600, Bear Giles wrote: I've written a few prototypes and this comes down to four issues. Some of the details below are debian/ubuntu-specific but the same concepts will apply to redhat. [..] 2. Packages should NOT be backed up. All you need is the package name and version. Reinstall from .deb and .rpm if necessary since this way you're sure that you never restore compromised files. You may want to look at the apt-clone package for this part of the work, it supports creating/restoring this meta-data. Cheers, Michael On Fri, Sep 30, 2011 at 12:01 AM, Gaurav Saxena grvsaxena...@gmail.comwrote: Hello Aaron Thanks a lot for your quick reply. On Fri, Sep 30, 2011 at 10:03 AM, Aaron C. de Bruyn aa...@heyaaron.comwrote: In Windows, the ability to snapshot is built into the filesystem. In Linux, you must be running a filesystem that supports snapshots. I know LVM supports snapshotting and I believe BRTFS has support, but other than that I'm not sure. Yes I read the logic behind windows system restore. But I think we can take some other approach for this, that will be better as all users won't be able to spare an extra partition formatted brtfs. Basically, your program would have to check the file system that is used on the computer (remember Linux can have many types of file systems mounted at the same time), then (in the case of LVM) make sure there's enough free space to snapshot, and finally take the snapshot. Ok. Do I have to snapshot the whole system partition / important system files to the brtfs partition ? When the snapshots start filling up, you would either need to delete them or detect the low space and resize them. In my personal opinion, snapshotting in Linux is currently a pain in the rear. It sounds like BTRFS could change that, but it's still a ways off. Ok. I will try another approach that will be better as suggested by people here. -A On Thu, Sep 29, 2011 at 21:00, Gaurav Saxena grvsaxena...@gmail.com wrote: Hello all, I want to write a windows system restore like program for ubuntu , which will have options for creating restore points for the system and then restoring it back to that point. Also I will as an extension provide support for older version of a file as is in windows currently. I need your help to find how to start with this in ubuntu. I know that I have to snapshot the system when creating a restore point and then restore it. I need some starting pointers so that I can start doing this work. Also if this has already been done please inform me. I got this idea from https://wiki.ubuntu.com/SystemRestore. -- Thanks and Regards , Gaurav -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Thanks and Regards , Gaurav -- Thanks and Regards , Gaurav -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu-devel-discuss Digest, Vol 36, Issue 10
On Wed, Nov 04, 2009 at 10:38:35AM +0200, Davyd McColl wrote: On Tue, 03 Nov 2009 20:07:58 +0100, Mario Vukelic wrote: I don't think that the OP provided enough information to understand what went wrong during his upgrade; it does seem that he may have tried update-manager first and resorted to the manual process only once it failed. First and foremost I'm sorry that you had such a bad upgrade experience. We work hard to make it smooth and painless and take the bugs/issues very seriously. Apologies if I wasn't quite clear -- I have been known to ramble a little. At the risk of once again flooding the mailing list with useless information (sorry!), here is the sequence of events leading up to the issues at hand: 1) Notice update-manager icon in the tray; clicky! 2) Get update-manager screen telling me that I have about 4 packages that may be updated. 3) Update-manager refreshes to show the New release available frame. Like an OCD spider-monkey on crack, I click on that thing! 4) Another dialog pops up, starting the upgrade process that I've been accustomed to (downloading scripts, etc) 5) This dies ): No idea why, really. Just death, cold, alone, and without so much as a crash report. If you still have access to the logs, could you please report a bug or mail me the content of /var/log/dist-upgrade/* ? I would really like to know what happend there. Given that your sources.list got udated (see below) I'm pretty sure there is useful log information available. 6) I re-launch update-manager from the tray icon, to find that I now have in the order of 1000 packages that can be upgraded. The update to new release frame doesn't re-appear. For all intents and purposes, it appears as if my machine has been morphed into a Koala with some negative karma points and a lot of upgrading ahead. I'm not daunted -- this looks like what I would expect if I were to manually edit my sources and do a dist-upgrade. So I click on update 7) After some time, the libc6 issue appears, asking me, via standard gtk-style deb messages, to restart, amongst other things, gdm. At this point, I drop out to a VT, stop gdm myself, and progress with apt-get dist-upgrade, thinking that the package manager for libc6 is probably a lot smarter than me and has his/her reasons for requesting a restart of gdm, as well as realising that if I don't do this in a VT, I have an endless loop ahead of me. So you stopped it and killed the session (that update-manager was running in) yourself? It was not the upgrade process that kicked you out? I assume you answered no, please stop the upgrade at the debconf prompt? I see that you reported bug #471436, I assume the pre-isnt exit there (comment #2) is the result of clicking cancel). 8) rounds of apt-get dist-upgrade interspersed with apt-get install -f until things seem calm. The occasional dpkg --purge of conflicting packages that I don't essentially need (indi and d4x come to mind) and some manual fixing for packages with bad post-install scripts (wicd comes to mind) [..] Thanks, indi and wicd have no open bugs about this it seems, could you please report them and include the failure? Please also file a bug about the grub problem, with the apt terminal log included. I suspect that grub somehow got removed during the upgrade but the logs should give us more details. Thanks, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: aufs based upgrade tests
On Tue, Mar 17, 2009 at 03:53:23PM +0200, Marius Gedminas wrote: On Mon, Mar 16, 2009 at 07:00:12PM +0100, Michael Vogt wrote: Yes, after the upgrade the system will be jaunty until the next reboot, then the writable overlay is removed and the system is exactly in the same state as before the upgrade. Does this overlay cover the whole filesystem? If people start creating files in /home that are going to be lost on reboot, it would be nice to warn them about that. [..] The /home dir is excluded from the overlay. There is still a certain risk with this however, assume hypothetical e.g. the new rhythmbox is run after the test upgrade and it converts its database files to a new format that the old (intrepid) version can no longer read. This is pretty rare, but it does sometimes happens. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: aufs based upgrade tests
On Sat, Mar 14, 2009 at 02:13:24PM +, (``-_-´´) -- BUGabundo wrote: Olá Michael e a todos. On Friday 13 March 2009 18:19:28 Michael Vogt wrote: during the last UDS we talked informally about using the aufs overlay filesystem layer for release upgrade testing. I build a prototype implementation of this now that should be ok for public testing. The idea discussed with Evan Dandrea (and others) was to create a writable overlay into /tmp on top the systemdirs in / and then run the release upgrade. This way we can test easily if the system would upgrade cleanly (if no dpkg errors/maintainer script failures happen). All writes go into /tmp so after the upgrade and on the next reboot the system is back to its pre-upgraded state again (modulo /home, that is not overlayed). It also means the next boot takes a *long* time to clean /tmp - when I did test it on one of my production machines that wait made me *really* nervous :) But its ok, it just takes long (up to ~20 minutes or so). Feedback is welcome This idea seems like a really nice idea, and one that in some other form is requested by users/testers. I would like to add to points: * if all tests go OK, and we end up with this on koala (to late for FFe on jaunty, right?), a checkbox when using update-manager -d / cli question on do-release-upgrade to use Sandbox would be much nicer then running all that code. * to save the system state prior to upgrade, so that a user can restore the system if even after successful package upgrade, some application/kernel/driver upgrade doesnt go as good. Thanks for this feedback. The longer term goal is provide the two improvements you suggested :) The current version is a first step to build up experience with the system. This is why its limited to testing currently, but in the longer run we hope to make it more capable. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: aufs based upgrade tests
On Sun, Mar 15, 2009 at 02:27:16AM -0400, John Vivirito wrote: On 03/14/2009 10:13 AM, (``-_-´´) -- BUGabundo wrote: Olá Michael e a todos. [..] This idea seems like a really nice idea, and one that in some other form is requested by users/testers. I would like to add to points: * if all tests go OK, and we end up with this on koala (to late for FFe on jaunty, right?), a checkbox when using update-manager -d / cli question on do-release-upgrade to use Sandbox would be much nicer then running all that code. * to save the system state prior to upgrade, so that a user can restore the system if even after successful package upgrade, some application/kernel/driver upgrade doesnt go as good. I am a bit on the short end of this topic due to trouble with having this set to digest mode. What exactly is this going to do. It sounds very interesting. is this similar to system restore in windows? The following quote makes it sound like after reboot it is going to restore itself to before the latest upgrade: All writes go into /tmp so after the upgrade and on the next reboot the system is back to its pre-upgraded state again Right now its a tool to help test if your version of ubuntu can upgrade to the next version of ubuntu without errors. It does a full regular upgrade from 8.10 to 9.04 but instead of writing it to the system disk it writes all changes to a directory in /tmp Doe the above always write to /tmp? If so does it clear upon restart automatically? Yes, after the upgrade the system will be jaunty until the next reboot, then the writable overlay is removed and the system is exactly in the same state as before the upgrade. Is there somewhere where i can get more information on it, a wiki or, blueprint or something? Unfortunately not right now. I created as a stub wiki page: https://wiki.ubuntu.com/AufsBasedUpgrades and we will probably talk about it at the next UDS and create a more formal plan. The currently version is build to get experience with the system and fint bugs and limitations with the aufs based approach, this is why its relatively complicated to enable it. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: aufs based upgrade tests
On Sun, Mar 15, 2009 at 11:51:52AM +0100, Vincenzo Ciancia wrote: When doing something like this one should be careful because here you have a copy of all files that are modified during the upgrade. Applications keeping these files open will write to the old copies, and applications which reopen the file after the upgrade will not see this data. This may be dangerous and lead to unexpected behaviour. Thanks for the feedback. This is a problem we are aware of. The best ways to fix it will probably we discussed at UDS. One approach (that is available in the code as well) is to just create the overlay for the dpkg child, this means that the regular desktop stuff (including firefox) keeps working during the upgrade. But in my tests it has been less of a practical problem than I anticiapted, i.e. I have not had any issues because of that in my tests (but of course this is all young and has not been tested that much yet). Apart from that, as I ranted in the past, let me say that this is a very important change and I am really happy that ubuntu developers are making it happen. Thanks, if it works out in the way we hope it will mean more robustness to upgrades and that is certainly a good thing. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: kvm sandbox upgrade tester
On Tue, Aug 26, 2008 at 02:54:21PM +0100, (``-_-´´) -- Fernando wrote: Olá Michael e a todos. Hi, sorry for my late reply, I was on vacation. On Friday 08 August 2008 13:05:36 Michael Vogt wrote: Hi, I would like to ask for feedback/testing of the kvm sandbox-upgrader package that is currently in my ppa at: deb http://ppa.launchpad.net/mvo/ubuntu hardy main It contains two scripts that need to be run with sudo: - sandbox-clone-to-vm - sandbox-test-upgrade Thanks, Michael I'm going to use this to test the 2.6.27 next kernel. any advice before I move? By the way is it : deb http://ppa.launchpad.net/mvo/ubuntu hardy main or deb http://ppa.launchpad.net/mvo/ubuntu intrepid main ? If you run hardy, then please use: deb http://ppa.launchpad.net/mvo/ubuntu hardy main If you run intrepid you can just install the version in the archive. I think it will not auto upgrade you when you run intrepid because it will tell you that you already run intrepid. But you can still use the clone feature and then manually log into the cloned system. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Thank you for the new Quick Search on Synaptic
On Wed, Jun 18, 2008 at 01:24:47PM +0100, Russell Green wrote: 2008/6/17 (``-_-´´) -- Fernando [EMAIL PROTECTED]: Thank you for the new Quick Search on Synaptic. It looks great and makes searches much, much, much faster and easier. That's (one of the things) why I love Ubuntu and FOSS so much. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss Nice feature but atm its not working for me, last time I checked it was greyed out. It is usually grayed out when the helper application apt-xapian-index is not installed. It is only a recommends of synaptic. It may also be still indexing, but it should write that into the UI. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Making apt-get powercut-proof
Hi, On Tue, May 06, 2008 at 07:06:35PM +0100, Andrew Sayers wrote: That's a pretty handy tool - would you be interested in an option to start the remote recovery that's being discussed in a nearby thread? The design of friendly-recovery makes it easy to drop-in scripts, I wasn't following this thread, but it would certainly be possible to drop in something into /usr/share/recovery-mode/options that is then available in the recovery menu. Also, how would you feel if I suggested the options/dpkg script to the APT development team as the basis for an init script? I don't expect it would add more than a few seconds to boot time (or less if there's a lockfile that they can check for the existence of), and it would tackle the specific issue I had, where the problem presented as a missing home directory, and only turned out to be a package installation issue after much investigation. I would prefer to make the package repair a explicit choice by the user. It may require manual input (conffile questions, debconf prompts, maintainer script prompts) so it is safer to handle when we know that a human is available. update-manager has support to deal with most brokeness in the packages system nowdays (interrupted dpkg, broken dependencies, packages in req-reinstall state, ...) and update-notifier will display a error symbol that will call update-manager. That should cover most of the desktop use-cases. The friendly-reocvery package with dpkg repair mode is now also available in hardy-proposed and should become available to hardy-updates soonish. Thanks, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Making apt-get powercut-proof
Hi,
On Mon, May 05, 2008 at 08:57:36PM +0100, Andrew Sayers wrote:
A friend of mine was upgrading to Hardy, and (so far as we can tell)
there was a power cut while it was halfway through, which left his
system in a not-especially-useful state. I think the best solution is
to have a /etc/init.d/{apt-get|dpkg} script that checks for
half-finished installs, and restarts them if necessary. If so, which
(or both) would be better, and is there anyone here that knows enough
about the two to suggest a complete set of commands that need to be run?
Also, is this something we should be doing in an Ubuntu-specific way
(e.g. from X), or should I take this idea to Debian?
I added a dpkg/apt recovery to the friendly-recovery package in
intrepid. When booting into recovery mode it will have a dpkg -
Repair packages menu item that will do the required steps. I plan to
also extend update-manager so that it is available there.
The new friendly recovery is also in my PPA at
https://edge.launchpad.net/~mvo/+archive
(for those curious to test).
Cheers,
Michael
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Use of the XS-Vcs-bzr (or -git, ...) debian/control field
Hi, I would like to start a discussion about adopting the XS-Vcs-* debian/control field in our packages. The value of the field should be the location of the version control system used to maintain this packages, e.g. XS-Vcs-Bzr: http://launchpad.net/~ubuntu-core-dev/python-apt/ubuntu Debian is using this in its PTS system and it will go into the developers reference. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391023 and http://www.bononia.it/~zack/blog/posts/xs-vcs-XXX_almost_there.html There are several benefits for this field. One is that launchpad could parse it and automatically link in the packages page to the right branch from which that package was build. But the main advantage to me is that this way each developer can see if and what VCS is used. Then he can either notify the maintainer of the package that a new version needs to be integrated into the VCS or just submit the patch into the VCS himself (for e.g. ~ubuntu-core-dev). I think this is important for ubuntu because: a) a lot of packages are maintained in bzr nowdays and the number is increasing (NoMoreSourcePackages!) b) packages are frequently uploaded by people who touch the package for the first time (e.g. for transitions) without notification or VCS commit Having a VCS out of sync with the reality in the archive leads to dropped patches, merge conflicts and general grief. I think that usage of the X-VCS-* tag can help to reduce this problem a lot. Cheers, Michael -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
