Re: UI for backports usage
On Tuesday 23 October 2007 11:10:06 Daniel Holbach wrote: Hello everybody, snip Have a nice day, Daniel What ever gets done for Backports should also be done for Proposed. Users should be able to easily test updates available on Proposed, knowing right then that does are Testing packages. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net signature.asc Description: This is a digitally signed message part. -- 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: UI for backports usage
John Dong [EMAIL PROTECTED] writes: No, IMO the UI, underneath, should be adding the entire backports repository, just all packages pinned back. This does not necessarily need pinning via /etc/apt/preferences. Apt has a feature which does something similar. Please compare http://archive.ubuntu.com/ubuntu/dists/gutsy-backports/Release with http://backports.org/backports.org/dists/etch-backports/Release wrt to the NotAutomatic: Yes field in bpo. I always wondered by ubuntu backports don't have that field. See http://backports.org/dokuwiki/doku.php?id=instructions for instructions how to use them. If backports were NotAutomatic: yes, then the instructions would reduce to step 3, i.e.: apt-get -t gutsy-backports install package Synaptic and aptitude already offer a nice interface for selecting specific version (i.e. backports for instance). John, does this satisfy your concerns? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- 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: UI for backports usage
Wow, never knew about NotAutomatic -- that sounds great! On Wed, Oct 24, 2007 at 08:39:12AM +0200, Reinhard Tartler wrote: John Dong [EMAIL PROTECTED] writes: No, IMO the UI, underneath, should be adding the entire backports repository, just all packages pinned back. This does not necessarily need pinning via /etc/apt/preferences. Apt has a feature which does something similar. Please compare http://archive.ubuntu.com/ubuntu/dists/gutsy-backports/Release with http://backports.org/backports.org/dists/etch-backports/Release wrt to the NotAutomatic: Yes field in bpo. I always wondered by ubuntu backports don't have that field. See http://backports.org/dokuwiki/doku.php?id=instructions for instructions how to use them. If backports were NotAutomatic: yes, then the instructions would reduce to step 3, i.e.: apt-get -t gutsy-backports install package Synaptic and aptitude already offer a nice interface for selecting specific version (i.e. backports for instance). John, does this satisfy your concerns? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- 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: UI for backports usage
Hello, I have a few questions. 2007/10/24, John Dong [EMAIL PROTECTED]: Wow, never knew about NotAutomatic -- that sounds great! Where is the documentation for this feature ? I do not remember finding on the APT manual.. Will it cause the packages already installed from the backports repositories to be upgraded when a newer version becomes available ? It would be great to integrate with a web interface if apt url allowed to specify the release name. Thanks -- João Pinto IRC: Lamego @ irc.freenode.net Jabber ID: [EMAIL PROTECTED] GetDeb Project Manager - http://www.getdeb.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
UI for backports usage
Hello everybody, I had some discussions with John Dong and João Pinto and both acknowledged the fact that there's a need for installing just a select few backport packages and not all of them. Let's imagine that somebody has an interest in just the latest version of blender on his stable system. That user does not want to upgrade to all packages available in the backports repository, but just the backported version of blender. How could something like this be realised in a user-friendly way? Have a nice day, Daniel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- 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: UI for backports usage
No, IMO the UI, underneath, should be adding the entire backports repository, just all packages pinned back. A UI should be able to unpin specific versions of each backport to let it through, but not let through other backports unless needed to satisfy dependences... An apturl approach would require the archive to create a separate section for each package and a meta all section like Debian Backports, which I guess can be done but is more complex. John On Tue, Oct 23, 2007 at 04:06:32PM +0300, Teemu Heinämäki wrote: What about getdeb with apturl? It can remove the external repositorys from sources.list after you install from there if you wish. Maybe it can be modified to do so automatically? https://wiki.ubuntu.com/AptFirefoxFileHandler ti, 2007-10-23 kello 07:22 -0400, Scott Kitterman kirjoitti: On Tue, 23 Oct 2007 12:10:06 +0200 Daniel Holbach [EMAIL PROTECTED] wrote: Hello everybody, I had some discussions with John Dong and João Pinto and both acknowledged the fact that there's a need for installing just a select few backport packages and not all of them. Let's imagine that somebody has an interest in just the latest version of blender on his stable system. That user does not want to upgrade to all packages available in the backports repository, but just the backported version of blender. How could something like this be realised in a user-friendly way? I think that between the getdeb web U/I and gdebi there is a very reasonably user friendly approach. I think from a U/I perspective it's only major lack is around automated dependency management. Scott K -- 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: UI for backports usage
Hello, about the UI, there is already a specification which cover most of the requirements: https://wiki.ubuntu.com/ThirdPartyApt The pinning support is described but not implemented, I did exchange several mails with the GApti author in order to motivate him to implement the pinning, I have failed, despite of the specification I was unable to convince that there maybe a good reason to pin a main/universe package . GApti is available on Gutsy universe, it would need be extended with the pinning support and an unpinning interface. Please note that I did already some research on this subject: http://wiki.getdeb.net/Software_Distribution The https://wiki.ubuntu.com/DynamicMirrorDecisions is also a very important detail, you must guarantee that the UI will pick the correct version (the latest), with dynamic mirror the server side component will know/check for synchronized mirrors and return it. Thanks -- João Pinto IRC: Lamego @ irc.freenode.net Jabber ID: [EMAIL PROTECTED] GetDeb Project Manager - http://www.getdeb.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
Re: UI for backports usage
On Tue, Oct 23, 2007 at 09:23:33AM -0400, John Dong wrote: An apturl approach would require the archive to create a separate section for each package and a meta all section like Debian Backports, which I guess can be done but is more complex. http://www.backports.org/debian/dists/etch-backports/Release NotAutomatic: yes -- 5o Peter.Mann at tuke.sk -- 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: UI for backports usage
There's obviously a need for a new infrastructure/UI. Since GDebi and apt-url are to be disabled in future versions (which I approve of), we should find a way to allow the user to select trusted repositories and easily install software from there, either on a replace-alla-installed-packages basis or on a ponctual one. Maybe apt-url could be modified only to accept trusted repos. Else, we would need a new graphical tool, or new features in Add/Remove applications. -- 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: UI for backports usage
On Oct 23, 2007, at 11:10 PM, Daniel Holbach wrote: ... Let's imagine that somebody has an interest in just the latest version of blender on his stable system. That user does not want to upgrade to all packages available in the backports repository, but just the backported version of blender. How could something like this be realised in a user-friendly way? ... Perhaps a New Versions item in the navigation list for the package manager, next to the items for minor updates, but different from those items in that all its packages would be unselected by default. Cheers -- Matthew Paul Thomas http://mpt.net.nz/ PGP.sig Description: This is a digitally signed message part -- 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: UI for backports usage
On Tuesday 23 October 2007 19:22, Matthew Paul Thomas wrote: On Oct 23, 2007, at 11:10 PM, Daniel Holbach wrote: ... Let's imagine that somebody has an interest in just the latest version of blender on his stable system. That user does not want to upgrade to all packages available in the backports repository, but just the backported version of blender. How could something like this be realised in a user-friendly way? ... Perhaps a New Versions item in the navigation list for the package manager, next to the items for minor updates, but different from those items in that all its packages would be unselected by default. Cheers How about apt/adept/nautilus changes so that only packages installed from backports can be upgraded by backports. Then it would be safe to just enable the repository and install things you wanted from there. There would also need to be U/I to install from the regular distro repo if the backport was not wanted. I think that, more cleanly, gets at the heart of the matter. Packages not selected by the user to be installed from backports should not be upgraded from backports. Scott K -- 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: UI for backports usage
On Tue, 2007-10-23 at 20:13 -0400, Scott Kitterman wrote: How about apt/adept/nautilus changes so that only packages installed from backports can be upgraded by backports. Then it would be safe to just enable the repository and install things you wanted from there. There would also need to be U/I to install from the regular distro repo if the backport was not wanted. Isn't this what the NotAutomatic field in the Release file meant to do? I think that, more cleanly, gets at the heart of the matter. Packages not selected by the user to be installed from backports should not be upgraded from backports. Scott K -- Michael R. Head [EMAIL PROTECTED] http://picasaweb.google.com/demiri.head.wedding smime.p7s Description: S/MIME cryptographic signature -- 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
