Feature changed by: visnov
Feature #303738, revision 5
Title: yast repository manager should be able to import .repo files
- openSUSE-11.1: Evaluation
+ openSUSE-11.1: Rejected by visnov(a)novell.com
+ reject date: 2008-06-26 15:20:02
+ reject reason: Importing a .repo file is an expert feature, having
+ zypper support is enough.
Priority
Requester: Desirable
Requested by: lslezak(a)novell.com
Partner organization: openSUSE.org
Description:
It should be possible to add a repository defined in a .repo file. This
functionlity is already implemented in zypper.
References:
https://bugzilla.novell.com/show_bug.cgi?id=384195
Discussion:
#1: dmacvicar(a)novell.com (2008-04-28 17:48:42)
Actually the functionallity is implemented in libzypp.
RepoManager::addRepositories( const Url &url, const ProgressData::
ReceiverFnc & progressrcv = ProgressData::ReceiverFnc() );
there you pass the url of the repo file (which can contain multipla
repositories).
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=303738
Feature changed by: visnov
Feature #302354, revision 11
Title: Split metadata by architecture / modules
openSUSE-11.0: Rejected by visnov(a)novell.com
reject date: 2008-03-28 16:28:18
reject reason: Out of resources. The speed of parsing is greatly
improved, downloading is still an issue in 11.0.
Priority
Requester: Important
openSUSE-11.1: Evaluation
Priority
Requester: Important
Requested by: visnov(a)novell.com
Partner organization: openSUSE.org
Description:
All packages are in a single file no matter if they are from different
architectures, therefore ZYpp has to download everything
Any kind of metadata should be separated by architecture. ZYpp does it
for patterns in 10.3, but it is still missing for packages
The metadata should be ideally separated by subdirectories and modules.
See references on how debian does it
References:
https://bugzilla.novell.com/show_bug.cgi?id=208452
Discussion:
#1: dmacvicar(a)novell.com (2007-11-09 16:52:55)
This is not true, YaST filter patterns in 10.3. Will edit the feature
to represent the real problems
#2: flucifredi(a)novell.com (2008-06-13 20:22:10)
Duncan, do we still need this / have an advantage from it ? if so, lets
make it Mandatory.
#3: dmacvicar(a)novell.com (2008-06-26 13:17:09)
This feature requires:
- separate primary.xml files per architecture. 90% effort -> rudi ,
adrian
- tell libzypp to ignore certain pattern or convention ( primary-x86_64.
xml ??? ) when downloading -> one liner.
It is not much benefit anymore as we are much faster now, but I would
recommend pset it to desirable and pass to Rudi and Adrian.
+ #4: visnov(a)novell.com (2008-06-26 13:20:11) (reply to #3)
+ Adrian, this is something for you.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=302354
Feature changed by: dmacvicar
Feature #302354, revision 10
Title: Split metadata by architecture / modules
openSUSE-11.0: Rejected by visnov(a)novell.com
reject date: 2008-03-28 16:28:18
reject reason: Out of resources. The speed of parsing is greatly
improved, downloading is still an issue in 11.0.
Priority
Requester: Important
openSUSE-11.1: Evaluation
Priority
Requester: Important
Requested by: visnov(a)novell.com
Partner organization: openSUSE.org
Description:
All packages are in a single file no matter if they are from different
architectures, therefore ZYpp has to download everything
Any kind of metadata should be separated by architecture. ZYpp does it
for patterns in 10.3, but it is still missing for packages
The metadata should be ideally separated by subdirectories and modules.
See references on how debian does it
References:
https://bugzilla.novell.com/show_bug.cgi?id=208452
Discussion:
#1: dmacvicar(a)novell.com (2007-11-09 16:52:55)
This is not true, YaST filter patterns in 10.3. Will edit the feature
to represent the real problems
#2: flucifredi(a)novell.com (2008-06-13 20:22:10)
Duncan, do we still need this / have an advantage from it ? if so, lets
make it Mandatory.
+ #3: dmacvicar(a)novell.com (2008-06-26 13:17:09)
+ This feature requires:
+ - separate primary.xml files per architecture. 90% effort -> rudi ,
+ adrian
+ - tell libzypp to ignore certain pattern or convention ( primary-x86_64.
+ xml ??? ) when downloading -> one liner.
+ It is not much benefit anymore as we are much faster now, but I would
+ recommend pset it to desirable and pass to Rudi and Adrian.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=302354
Feature changed by: visnov
Feature #303517, revision 4
Title: Configure a cronjob for refreshing repositories
openSUSE-11.1: Evaluation
Priority
Requester: Desirable
+ Projectmanager: Mandatory
Requested by: lslezak(a)novell.com
Partner organization: openSUSE.org
Description:
Autorefresh configured repositories at certain times, this could be on
certain days, or time of day, etc.
A mockup and more details are in
https://bugzilla.novell.com/show_bug.cgi?id=346966
Discussion:
#1: flucifredi(a)novell.com (2008-06-13 15:12:52)
there are some caveats I can think of requiring silent fail (for
instance, a laptop), or requiring randomization (not hitting NCC with a
volley all at the same time), but I think the idea is good.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=303517
Feature changed by: visnov
Feature #303527, revision 9
Title: Resolve dependencies after ignoring package download failure
openSUSE-11.1: Evaluation
Priority
Requester: Desirable
Requested by: jkupec(a)novell.com
Partner organization: openSUSE.org
Description:
YaST and Zypper should run the solver before resuming installation if
download of a package fails and the user chooses to ignore that
package. Currently YaST continues withough solving which makes the
ignore button useful only if the user knows how the missing package
will affect the system.
References:
https://bugzilla.novell.com/show_bug.cgi?id=340345#c4http://lists.opensuse.org/zypp-devel/2008-03/msg00025.html
Discussion:
#1: flucifredi(a)novell.com (2008-06-13 15:13:41)
bit of a corner case.
#2: jkupec(a)novell.com (2008-06-16 11:44:24)
Well, yes. An idea to cover it easily to some extent: let's advice
users to run 'zypper verify' (or the YaST equivalent) in such case,
after the installation is finished. This will fix hard dependencies.
+ #3: visnov(a)novell.com (2008-06-24 15:32:30) (reply to #2)
+ Yes, I would just suggest to add a message with instructions for the
+ user.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=303527
Feature changed by: visnov
Feature #303678, revision 6
Title: New yast module - LIRC configuration
- openSUSE-11.1: Evaluation
+ openSUSE-11.1: Rejected by visnov(a)novell.com
+ reject date: 2008-06-24 15:31:30
+ reject reason: More urgent stuff to cover.
Priority
Requester: Desirable
+ openSUSE-11.2: New
+ Priority
+ Requester: Desirable
Requested by: lslezak(a)novell.com
Partner organization: openSUSE.org
Description:
Create a new Yast module for configuring IR receivers and remote
controls.
* irrecord support
* ir-kbd-i2c, ir-kbd-gpio support as in tv module already
* reading users' config to find out what buttons were defined (only if
/home partition left from last installation)
* support for lirc's options in /etc/sysconfig
See bug https://bugzilla.novell.com/show_bug.cgi?id=381641
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=303678
Feature changed by: adrian
Feature #302047, revision 24
Title: Integrated package searching for YaST and build service
openSUSE-10.3: Rejected by aj(a)novell.com
reject date: 2007-10-05 14:30:28
reject reason: still open partly - postpone the rest.
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.0: Rejected by michl(a)novell.com
reject date: 2008-06-10 14:01:45
reject reason: not done for 11.0
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.1: Evaluation
Priority
Requester: Important
Requested by: dmacvicar(a)novell.com
Partner organization: openSUSE.org
Description:
You perhaps remember the hacks Benjamin did to support  "click and
install" packages (similar to Click'n run) [1]
Benjamin has another article in his blog that is worth to read.
He has been providing a wepage to search packages from repositories
like packman and build service. Now he presents an architecture to
desentralize the system, using web services an indexers, and he shows
working prototypes of YaST modules for searching, and others like web
and irc-bot clients
http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/
I hope we can provide a strategy and roadmap to integrate these cool
ideas and _code_.
 [1]:
http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/
Discussion:
#1: jw(a)suse.de (2007-05-03 15:29:13)
see also 300898
For 10.3 the installer should be able to make use of an external list
of repositories. I suggest to host such a list at
http://packages.opensuse-community.org/ together with the search
engine, which is already there.
#3: freitag(a)novell.com (2007-07-12 10:46:54)
Implementation on openSUSE BS already started, Adrian knows the
details.
#4: adrian(a)novell.com (2007-07-12 11:30:04)
We work on two approaches atm:
* YaST will support (thanks to mvidner) additional repository offers
during installation. The list gets hosted on our servers, the open
question is how to maintain this list.
* The build service End-User interface will offer .ymp files based on
pattern submissions for easy installation.
#5: visnov(a)novell.com (2007-07-30 20:13:09) (reply to #4)
Adrian, please, drive this. The feature for YaST should be done now
(let me know if anything is missing).
#6: michl(a)novell.com (2007-11-22 11:26:30)
This sounds like very useful. And it might be possible the community
(in this case Benji) helps implementing this.
#7: aj(a)novell.com (2008-06-06 10:56:28)
Apparently not done - please reject and postpone for 11.1.
#8: michl(a)novell.com (2008-06-10 14:02:08)
PM-Priority for product openSUSE-11.0 downgraded from mandatory to
important:
not done for 11.0 - PM accepts reality ;-)
+ #9: adrian(a)novell.com (2008-06-18 17:08:16)
+ This is something what we should bind to the new upcomming software
+ portal. The software portal will be the End-User interface for searcing
+ and installing software and replace http://software.opensuse.org/search
+ . However it is still in development and not yet set up. Therefore I am
+ unsure if this can happen in time for 11.1.
+ On the other side, the 1-click-installation and integration into the
+ web interface is done since quite some time. The user can use the cool
+ technologies from Benjamin since 10.3.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=302047
Feature changed by: jsrain
Feature #303493, revision 6
Title: zypper: add separate messages for Required and Recomended
packages
openSUSE-11.0: Rejected by visnov(a)novell.com
reject date: 2008-03-27 13:50:16
reject reason: Not enough time to look into this.
Priority
Requester: Important
- openSUSE-11.1: Evaluation
+ openSUSE-11.1: Candidate
Priority
Requester: Important
Projectmanager: Important
- SLES-11: Evaluation
+ SLES-11: Candidate
Priority
Requester: Important
Projectmanager: Important
Requested by: crrodriguez(a)novell.com
Partner organization: openSUSE.org
Description:
currenly when you install a package with zypper, you just get the
packages that are going to be installed, regardless if the are required
or Reccommended,.. will be nice if the messages can be arranged to be
more explict about what the package manager is doing.
"The following NEW [required|reccomended] package is going to be
installed: foo"
also an informative message about Suggested packages should be shown
"The following package(s) is(are) suggested but are not going to be
installed foo bar "
unless user pass --install-suggested or use a boolean configuration
directive on zypp.conf or something, suggested packages should not be
installed by default ..currently it seems to be completely ignored and
does nothing.
--
SUSE Feature Tool:
http://partnerfate.suse.de/?rm=feature_show&id=303493