The goodness of Smart (was: Upgrade from 10.0 to 10.1 using apt?)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Breaking into a new thread. Ken Schneider wrote:
On Fri, 2006-01-06 at 15:24 +0100, Clayton wrote:
1. It doesn't show me what version I already have installed (as Synaptic and Aptitude do). To me this is somewhat of a "deal breaker"... this really needs to be included in Smart-gui to make it useful/usable. I don't understand. Could you please provide a screenshot or a more detailed "how to reproduce"? Which "view" are you using in smart-gui? I'm thinking in terms of how Synaptic (or Aptitude) presents the information about installed applications.
If I filter the view so I just see upgradable packages, I'm shown two columns... Package and Version. What does this tell me? The version available or the version installed? It doesn't say (although from my own experience it looks like it's showing the available version). Also... assuming it's showing the available version, I can't easily see what version I already have installed (in fact, I can't see any obvious way at all to find out what version is already installed for those packages that are flagged as upgradable).
Look at how Synaptic presents the same info... Package, Installed Version, Available version. It's this installed vs repository version comparison I'm missing. I would hazard a guess that a lot of other people will be missing that same info....
This is my only complaint using smart. How hard can it be to add another column showing the installed version so a comparison can be made?
It's not, definately not with smart. File an enhancement request ;-)
So about the question what can smart do that yast2's package manager doesn't.
First off, it's all written in Python. It's really nice and clean code, very modular, which is a
good sign for long-term maintainance and quality of it as a whole.
As an example, Mauricio added YaST2 repository support (still experimental, included in my
"smart-0.41-10" package): he didn't have to patch anything, just 3 new files that get dropped and
"plug" into Smart's architecture.
There is still much room for improvements, no question about that, but what Christoph meant and what
I'd also like to ask: please test it and file bug reports. And if you'd like to contribute in other
ways: coding on the project, translating locale messages, writing documentation.
So, what's so nice about Smart.
* mirrors
- - mirrors are managed globally, for every single operation, because you just define URL mappings
(e.g. "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS" ->
"http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS"), that's it, it will apply for
every file retrieval because it's managed by a central component
- - you can define several of such "mirror mappings" and Smart collects information about hits and
misses as well as average speed, selecting the best mirror based on that information (IIRC it even
parallelizes downloads and distributes them on several mirrors, when available)
* supports many repository formats
It's a single tool that supports
- - several repository formats: rpm-md (yum), apt-rpm, apt-deb, urpmi, redcarpet, rpmhd, up2date,
yast2 (experimental atm)
- - installing from just a directory of files, without any metadata
- - several backends: rpm, dpkg, slack (obviously a bad idea to install dpkg packages on an RPM
system; in fact it means that smart runs on a lot of distributions, not just RPM-based ones)
- - several frontends, currently: command-line, shell, gtk2 GUI; this is very pluggable in its
architecture as well, someone could develop another gtk2 UI or a PyQt one or.. whatever has bindings
in Python, and it's directly into the runtime, no need for libraries or "shelling out"
The maintainer of the project, Gustavo Niemeyer (the former maintainer of apt-rpm, and he also
contributed a lot to synaptic) is very active on the project, as well as a really nice chap to
discuss with. He's also very open to improvements, ideas and constructive criticism.
These are just a few of the very nice things with smart.
It's not perfect yet, still has many points where it can be improved.
That's why Christoph, Mauricio and I are calling for testing ;)
But it has already proven to be very solid and consistent in terms of package management and
dependency handling (especially 0.41 that sorts out a lot of bugs that happened on SUSE Linux < 10.1
because of an older RPM version). The UIs still need improvements, especially the GUI (personally, I
mostly use the shell interface), but the deal is: let's work on it and contribute feedback, ideas,
and maybe even your experience in Python coding.
Given it's a very modular architecture and clean design, imagine all the possibilites once the core
is really solid (I think it already is as of now, the issues are rather with the UIs): a very smart
and portable (in every sense: package repository formats, backends) package management engine that
can be extended in nearly every possible way (and work on many different distributions).
Personally, at least, and as a software developer, I find the concept very attractive and I can
definitely see the potential of the project.
Well, that's the reason why I want to get involved in it.
http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Sat, 7 Jan 2006, Pascal Bleser wrote:
Breaking into a new thread.
We should have done that early, I guess ;)
Ken Schneider wrote:
On Fri, 2006-01-06 at 15:24 +0100, Clayton wrote:
1. It doesn't show me what version I already have installed (as Synaptic and Aptitude do). To me this is somewhat of a "deal breaker"... this really needs to be included in Smart-gui to make it useful/usable. I don't understand. Could you please provide a screenshot or a more detailed "how to reproduce"? Which "view" are you using in smart-gui? I'm thinking in terms of how Synaptic (or Aptitude) presents the information about installed applications.
If I filter the view so I just see upgradable packages, I'm shown two columns... Package and Version. What does this tell me? The version available or the version installed? It doesn't say (although from my own experience it looks like it's showing the available version). Also... assuming it's showing the available version, I can't easily see what version I already have installed (in fact, I can't see any obvious way at all to find out what version is already installed for those packages that are flagged as upgradable).
Look at how Synaptic presents the same info... Package, Installed Version, Available version. It's this installed vs repository version comparison I'm missing. I would hazard a guess that a lot of other people will be missing that same info....
This is my only complaint using smart. How hard can it be to add another column showing the installed version so a comparison can be made?
It's not, definately not with smart. File an enhancement request ;-)
So about the question what can smart do that yast2's package manager doesn't.
First off, it's all written in Python. It's really nice and clean code, very modular, which is a good sign for long-term maintainance and quality of it as a whole. As an example, Mauricio added YaST2 repository support (still experimental, included in my "smart-0.41-10" package): he didn't have to patch anything, just 3 new files that get dropped and "plug" into Smart's architecture.
There is still much room for improvements, no question about that, but what Christoph meant and what I'd also like to ask: please test it and file bug reports. And if you'd like to contribute in other ways: coding on the project, translating locale messages, writing documentation.
So, what's so nice about Smart. * mirrors - - mirrors are managed globally, for every single operation, because you just define URL mappings (e.g. "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS" -> "http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS"), that's it, it will apply for every file retrieval because it's managed by a central component - - you can define several of such "mirror mappings" and Smart collects information about hits and misses as well as average speed, selecting the best mirror based on that information (IIRC it even parallelizes downloads and distributes them on several mirrors, when available)
* supports many repository formats It's a single tool that supports - - several repository formats: rpm-md (yum), apt-rpm, apt-deb, urpmi, redcarpet, rpmhd, up2date, yast2 (experimental atm) - - installing from just a directory of files, without any metadata - - several backends: rpm, dpkg, slack (obviously a bad idea to install dpkg packages on an RPM system; in fact it means that smart runs on a lot of distributions, not just RPM-based ones) - - several frontends, currently: command-line, shell, gtk2 GUI; this is very pluggable in its architecture as well, someone could develop another gtk2 UI or a PyQt one or.. whatever has bindings in Python, and it's directly into the runtime, no need for libraries or "shelling out"
The maintainer of the project, Gustavo Niemeyer (the former maintainer of apt-rpm, and he also contributed a lot to synaptic) is very active on the project, as well as a really nice chap to discuss with. He's also very open to improvements, ideas and constructive criticism.
These are just a few of the very nice things with smart. It's not perfect yet, still has many points where it can be improved. That's why Christoph, Mauricio and I are calling for testing ;)
But it has already proven to be very solid and consistent in terms of package management and dependency handling (especially 0.41 that sorts out a lot of bugs that happened on SUSE Linux < 10.1 because of an older RPM version). The UIs still need improvements, especially the GUI (personally, I mostly use the shell interface), but the deal is: let's work on it and contribute feedback, ideas, and maybe even your experience in Python coding.
Given it's a very modular architecture and clean design, imagine all the possibilites once the core is really solid (I think it already is as of now, the issues are rather with the UIs): a very smart and portable (in every sense: package repository formats, backends) package management engine that can be extended in nearly every possible way (and work on many different distributions). Personally, at least, and as a software developer, I find the concept very attractive and I can definitely see the potential of the project. Well, that's the reason why I want to get involved in it.
Well said -- but to make this long story short: SMART is smart. So don't be stupid ;) The upcoming Beta1 of SUSE Linux 10.1 will ship with the latest and greatest SMART, by the way. Have a nice weekend Christoph
I'll follow. Let me start with saying that I want to see smart and yum succeed. I look forward to the day that there is one format package repo format for suse operational. Op zaterdag 7 januari 2006 01:54, schreef Pascal Bleser:
So about the question what can smart do that yast2's package manager doesn't.
There is still much room for improvements, no question about that, but what Christoph meant and what I'd also like to ask: please test it and file bug reports. And if you'd like to contribute in other ways: coding on the project, translating locale messages, writing documentation.
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir This works with yum Why does smart not read the /etc/yum.repos.d directory? I now have to define the repositories twice :( Smart is not integrated with suse... I mean the "OK" button is at the right side while suse (kde) has it left... (nothing will be done about it, I know). There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would happen the alias field could be labelled "name"...
So, what's so nice about Smart. * mirrors - mirrors are managed globally, for every single operation, because you just define URL mappings (e.g. "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS" -> "http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS"), that's it, it will apply for every file retrieval because it's managed by a central component
Is there a central directory that shows which repositories are available? Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server?
But it has already proven to be very solid and consistent in terms of package management and dependency handling (especially 0.41 that sorts out a lot of bugs that happened on SUSE Linux < 10.1 because of an older RPM version).
command line tool yummie :) Heh, why is the /etc/yum.repos.d so empty when it is installed?? Why does it not come preconfigured with information for base, security, and all the other goodies (of course they could all be disabled).
http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart
It was very easy to install with apt :) Do you have a yum repodata directory? Why is yum not able to find yast2-tv? hp100:/etc/yum.repos.d # time apt search yast2-tv yast2-tv - YaST2 - TV Configuration real 0m5.794s user 0m2.864s sys 0m0.940s hp100:/etc/yum.repos.d # time yum search yast2-tv Searching Packages: Setting up repositories suser-rbos 100% |=========================| 951 B 00:00 base 100% |=========================| 951 B 00:00 packman 100% |=========================| 951 B 00:00 kolab 100% |=========================| 951 B 00:00 Reading repository metadata in from local files No Matches found real 0m19.979s user 0m12.705s sys 0m1.284s What about the rpmkey rpms? Will they be supported? I saw that each rpmkey file has to be configured in the /etc/yum.repos.d/* files? Why is it that way, why should they be configured in those repository files? Sofar my ramblings. it nice to see that smart works now (this was not the case when a I tested version 0.2 (or something like that) some years ago) -- Richard Bos Without a home the journey is endless
Op zaterdag 7 januari 2006 13:25, schreef Richard Bos:
Why is yum not able to find yast2-tv?
Is there a quiet option with yum (in case I want to run it from cron)? Is it possible to specify on the command line, 1 repository. I'm thinking of speficying only the security update channel/component. Is this possible? -- Richard Bos Without a home the journey is endless
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
I'll follow. Let me start with saying that I want to see smart and yum succeed. I look forward to the day that there is one format package repo format for suse operational.
Op zaterdag 7 januari 2006 01:54, schreef Pascal Bleser:
So about the question what can smart do that yast2's package manager doesn't.
There is still much room for improvements, no question about that, but what Christoph meant and what I'd also like to ask: please test it and file bug reports. And if you'd like to contribute in other ways: coding on the project, translating locale messages, writing documentation.
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir This works with yum
Ok, good point to check. If it doesn't work, it should be added (not very difficult though, it's a central component that handles all file retrieval in smart).
Why does smart not read the /etc/yum.repos.d directory? I now have to define the repositories twice :(
Because smart doesn't use yum. That's one of the nice things about smart: repository metadata support for apt-rpm, rpm-md/yum, yast2, urpmi, ... ... has been implemented in pure Python code, independently of whether you have yum, apt-rpm, yast2, urpmi, etc.. installed or not. Also, it has a very minimal set of dependencies (python >= 2.3, python-rpm). Note that the code to import yum.repos.d/* could be added. The question is whether one really wants that :) I use rpm-md repositories without having configured any repository in yum. How do you want to sync between the smart channels and yum yum.repos.d/* ? - - at installation of smart, once - - every time smart starts up, but only add channels for yum repos that are missing (as channels) don't remove anything - - same as above but with prompting the user for every channel - - explicitely, with a "reposync" (just an example ;)) command in smart ... ? What could be done very easily is a set of scripts that import - - yum (/etc/yum.repos.d/*) - - apt-rpm (/etc/apt/sources.list + /etc/apt/sources.list.d/*) - - yast2 (installation_sources -s) repositories into smart. I already hacked one (not much tested though) for apt-rpm: http://linux01.gwdg.de/~pbleser/files/smart/apt-sources-to-smart.sh And there's another one written by oc2pus: http://www30.websamba.com/texpert/ Same could be done for yum and yast2. Quickly hacked a prototype for importing yast2 sources: http://linux01.gwdg.de/~pbleser/files/smart/yast2-sources-to-smart.sh It even imports the "autorefresh" and "enabled" information. Run with -n for a dry run. Disclaimer: early alpha version, untested, use at your own risk ;)
Smart is not integrated with suse... I mean the "OK" button is at the right side while suse (kde) has it left... (nothing will be done about it, I know).
Hm. File a bug ? ;) Maybe a SUSE-specific patch into the smart.rpm, but I'm not sure it's a good idea to have a different UI on SUSE than on other distros ;)
There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would happen the alias field could be labelled "name"...
Yes, might be easier to understand.
So, what's so nice about Smart. * mirrors - mirrors are managed globally, for every single operation, because you just define URL mappings (e.g. "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS" -> "http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS"), that's it, it will apply for every file retrieval because it's managed by a central component
Is there a central directory that shows which repositories are available?
No. Remember that smart is not SUSE-specific in any way and already used since some time by people on other distros.
Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server?
Similar to the list of repositories on http://opensuse.org Note that smart has the nice ability to retrieve a list of repositories from a text file, e.g.: smart channel --add http://linux01.gwdg.de/~pbleser/files/smart/my-smart-channels.txt
But it has already proven to be very solid and consistent in terms of package management and dependency handling (especially 0.41 that sorts out a lot of bugs that happened on SUSE Linux < 10.1 because of an older RPM version).
command line tool yummie :) Heh, why is the /etc/yum.repos.d so empty when it is installed?? Why does it not come preconfigured with information for base, security, and all the other goodies (of course they could all be disabled).
Smart does, because in my smart.rpm I add those channels (as well as my repo and packman).
http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart It was very easy to install with apt :) Do you have a yum repodata directory?
Yes, not much tested/used but should work: http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.0/RPMS (as well as for 9.3, 9.2, etc...) ...
What about the rpmkey rpms? Will they be supported? I saw that each rpmkey file has to be configured in the /etc/yum.repos.d/* files? Why is it that way, why should they be configured in those repository files?
That's a yum thing, not smart ;) Smart has no rpmkey support AFAIK. Again, could be done as well.
Sofar my ramblings. it nice to see that smart works now (this was not the case when a I tested version 0.2 (or something like that) some years ago)
;)
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Op zaterdag 7 januari 2006 15:47, schreef Pascal Bleser:
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir This works with yum
Ok, good point to check. If it doesn't work, it should be added (not very difficult though, it's a central component that handles all file retrieval in smart).
How does this not get forgotten, do you take care for it?
Why does smart not read the /etc/yum.repos.d directory? I now have to define the repositories twice :(
Because smart doesn't use yum.
That's true. I considered them both as the same which they aren't.
That's one of the nice things about smart: repository metadata support for apt-rpm, rpm-md/yum, yast2, urpmi, ... ... has been implemented in pure Python code, independently of whether you have yum, apt-rpm, yast2, urpmi, etc.. installed or not. Also, it has a very minimal set of dependencies (python >= 2.3, python-rpm).
Note that the code to import yum.repos.d/* could be added. The question is whether one really wants that :)
No need, if smart is just good. No need at all when smart is better than yum ;)
I use rpm-md repositories without having configured any repository in yum.
How do you want to sync between the smart channels and yum yum.repos.d/* ? - at installation of smart, once - every time smart starts up, but only add channels for yum repos that are missing (as channels) don't remove anything - same as above but with prompting the user for every channel - explicitely, with a "reposync" (just an example ;)) command in smart ... ?
What could be done very easily is a set of scripts that import - yum (/etc/yum.repos.d/*) - apt-rpm (/etc/apt/sources.list + /etc/apt/sources.list.d/*) - yast2 (installation_sources -s) repositories into smart.
I already hacked one (not much tested though) for apt-rpm: http://linux01.gwdg.de/~pbleser/files/smart/apt-sources-to-smart.sh And there's another one written by oc2pus: http://www30.websamba.com/texpert/
Same could be done for yum and yast2.
Quickly hacked a prototype for importing yast2 sources: http://linux01.gwdg.de/~pbleser/files/smart/yast2-sources-to-smart.sh It even imports the "autorefresh" and "enabled" information. Run with -n for a dry run. Disclaimer: early alpha version, untested, use at your own risk ;)
Good to know.
There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would happen the alias field could be labelled "name"...
Yes, might be easier to understand.
How does this not get forgotten, do you take care for it?
So, what's so nice about Smart. * mirrors - mirrors are managed globally, for every single operation, because you just define URL mappings (e.g. "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS" -> "http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS"), that's it, it will apply for every file retrieval because it's managed by a central component
Is there a central directory that shows which repositories are available?
No. Remember that smart is not SUSE-specific in any way and already used since some time by people on other distros.
The question remains. Is there a central directory that shows which repositories are available for suse. How come that smart only got better when susers started to use smart?
Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server?
Similar to the list of repositories on http://opensuse.org
Note that smart has the nice ability to retrieve a list of repositories from a text file, e.g.: smart channel --add http://linux01.gwdg.de/~pbleser/files/smart/my-smart-channels.txt
Something like this I was looking for indeed. Can it be stored on a wiki page, so we can all add our own channel information?
Smart has no rpmkey support AFAIK. Again, could be done as well.
How does this not get forgotten, do you take care for it? BTW, I think this is a must if smart is to replace apt. so 'smart install rpmkey-suser-guru' should insert your key into the gpg database. Please remove this line "Run "smart command --help" for more information" from 'smart --help". If run 'smart --help' I don't get more information. Where is smart manpage? Just create one with help2man. What is the smart similar command for: 'apt --sources security.list upgrade' This only upgrades the security packages. I assume it exists but 'man smart' does not tell ;) Is there yast support to configure automatic package upgrades? Have a look at: /var/adm/fillup-templates/sysconfig.autoupdate This can be reached via yast -> system -> sysconfig editor -> Autoupdate Running # smart upgrade Loading cache... Updating cache... ######################################## [100%] Computing transaction... Upgrading packages (19): alsa gcompris libvorbis perl-Cyrus-IMAP alsa-devel imlib2 libvorbis-devel rar alsa-firmware imlib2-loaders libxine1 sane alsa-tools k3b mad speex freeciv kipi-plugins mplayerplug-in Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name? What is meant in the output above with: Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid The package is not installed, see: linux:/etc/sysconfig # rpm -q faac package faac is not installed -- Richard -- Richard Bos Without a home the journey is endless
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
Op zaterdag 7 januari 2006 15:47, schreef Pascal Bleser:
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir This works with yum Ok, good point to check. If it doesn't work, it should be added (not very difficult though, it's a central component that handles all file retrieval in smart).
How does this not get forgotten, do you take care for it?
No, I'm not developing on smart (would like to, but no time as of now), neither is this mailing-list the right place to submit feature requests or bugfixes (unless they're intrinsincly related to SUSE Linux) ;) Please use the Smart bugtracker: http://tracker.labix.org/ ...
No. Remember that smart is not SUSE-specific in any way and already used since some time by people on other distros.
The question remains. Is there a central directory that shows which repositories are available for suse. How come that smart only got better when susers started to use smart?
The rpm-md parsing performance enhancement was a tip from Christoph Thiel. Sorting out bugs with an older version of RPM only happened since people use it on SUSE, because SUSE Linux is the last distro that uses a completly outdated (but heavily patched) RPM version. Note that this does not apply to 10.1 as it uses a current RPM version. Central directory of repositories for SUSE: http://www.opensuse.org/Additional_YaST_Package_Repositories
Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server? Similar to the list of repositories on http://opensuse.org
Note that smart has the nice ability to retrieve a list of repositories from a text file, e.g.: smart channel --add http://linux01.gwdg.de/~pbleser/files/smart/my-smart-channels.txt
Something like this I was looking for indeed. Can it be stored on a wiki page, so we can all add our own channel information?
I would suggest that too. See the URL above. Maybe we could also embed smart channel files for those ? e.g. a link to a file "guru-10.0.channel" that includes the following: [guru-10.0] type = yast2 name = Guru baseurl = http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.0 One would just need to right-click the link on the wiki page, "copy link location" and then paste it in a shell, like this: smart channel --add http://www.opensuse.org/smart/guru-10.0.channel Maybe one could even make a MIME handler for *.channel files (one-click channel adding) ;) *.channel => kdesu - -c "konsole -e 'smart channel --add'" or something like that, with a .desktop file...
Smart has no rpmkey support AFAIK. Again, could be done as well.
How does this not get forgotten, do you take care for it? BTW, I think this is a must if smart is to replace apt. so 'smart install rpmkey-suser-guru' should insert your key into the gpg database.
Hmm... IIRC that works on RPM level. What I meant with "no rpmkey support" is that Smart won't automatically install the rpmkey-* RPM that matches a repository (as yum does IIRC). Nor will it say "this package is signed with key ... but you don't have that key, do you want me to install rpmkey-suser-guru ?"
Please remove this line "Run "smart command --help" for more information" from 'smart --help". If run 'smart --help' I don't get more information. Where is smart manpage? Just create one with help2man.
Hmm.. yes, a manpage would be great :)
What is the smart similar command for: 'apt --sources security.list upgrade' This only upgrades the security packages. I assume it exists but 'man smart' does not tell ;)
Documentation is still lacking. Smart has a great number of commands and flags but most are still undocumented (that's where being a 0.41 shows most).
Is there yast support to configure automatic package upgrades? Have a look at: /var/adm/fillup-templates/sysconfig.autoupdate This can be reached via yast -> system -> sysconfig editor -> Autoupdate
That's a YaST2-only feature, or YOU rather. Would require YOU repository support in Smart. That might be on Mauricio's TODO list, once yast2 repository support is sufficently tested ;)
Running # smart upgrade Loading cache... Updating cache... ######################################## [100%]
Computing transaction...
Upgrading packages (19): alsa gcompris libvorbis perl-Cyrus-IMAP alsa-devel imlib2 libvorbis-devel rar alsa-firmware imlib2-loaders libxine1 sane alsa-tools k3b mad speex freeciv kipi-plugins mplayerplug-in
Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid
Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name?
Sure. Not implemented as of now, but from having looked at the smart source code [1] a few times, I'd say this would be very easy to implement, but has to be done for the shell, CLI and GUI interface. Please open a feature request on the tracker [2]. [1] svn co http://svn.smartpm.python-hosting.com/trunk [2] http://tracker.labix.org/
What is meant in the output above with:
Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid
The package is not installed, see: linux:/etc/sysconfig # rpm -q faac package faac is not installed
Actually it means that to perform the upgrade you've asked for, smart will
- - upgrade the 19 packages mentioned in "Upgrading packages"
- - additionally install the 5 currently uninstalled packaged mentioned in "Installed packages" to
fulfill the dependencies created by the upgrade process
Indeed, "Installed packages" might be a bit misleading.
"Installing additional packages" would be more appropriate.
I've submitted a bug (+ patch) for this one: http://tracker.labix.org/issue72
(same for "Removed packages", should be "Removing packages")
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Op zondag 8 januari 2006 11:56, schreef Pascal Bleser:
Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server?
Similar to the list of repositories on http://opensuse.org
Note that smart has the nice ability to retrieve a list of repositories from a text file, e.g.: smart channel --add http://linux01.gwdg.de/~pbleser/files/smart/my-smart-channels.txt
Something like this I was looking for indeed. Can it be stored on a wiki page, so we can all add our own channel information?
I would suggest that too. See the URL above. Maybe we could also embed smart channel files for those ? e.g. a link to a file "guru-10.0.channel" that includes the following:
[guru-10.0] type = yast2 name = Guru baseurl = http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.0
One would just need to right-click the link on the wiki page, "copy link location" and then paste it in a shell, like this: smart channel --add http://www.opensuse.org/smart/guru-10.0.channel
Maybe one could even make a MIME handler for *.channel files (one-click channel adding) ;) *.channel => kdesu - -c "konsole -e 'smart channel --add'" or something like that, with a .desktop file...
Yes, that would be awesome!
Smart has no rpmkey support AFAIK. Again, could be done as well.
How does this not get forgotten, do you take care for it? BTW, I think this is a must if smart is to replace apt. so 'smart install rpmkey-suser-guru' should insert your key into the gpg database.
Hmm... IIRC that works on RPM level.
No it is not. It are plugins into apt. Gustavo knows this very well ;) Have a look at the scripts: /usr/lib/apt/scripts (from the pkg apt). Does smart support the functionality provided by: gpg-checker.lua, gpg-import.lua, pkglog.lua and post.lua inclusive configuration settings. Heh, we want smart to replace apt, so it should do it with the same functionality or more.
What I meant with "no rpmkey support" is that Smart won't automatically install the rpmkey-* RPM that matches a repository (as yum does IIRC).
How does yum do this, where does it fetch the signature from?
Is there yast support to configure automatic package upgrades? Have a look at: /var/adm/fillup-templates/sysconfig.autoupdate This can be reached via yast -> system -> sysconfig editor -> Autoupdate
That's a YaST2-only feature, or YOU rather.
No not all. It uses YAST to provide a GUI. The backend is stored in: /etc/cron.daily/suse-apt-upgrade
Would require YOU repository support in Smart. That might be on Mauricio's TODO list, once yast2 repository support is sufficently tested ;)
I thought that YOU is already able to repomd formatted pkg repositories? Could you explain what Mauricio is adding?
Running # smart upgrade Loading cache... Updating cache... ######################################## [100%]
Computing transaction...
Upgrading packages (19): alsa gcompris libvorbis perl-Cyrus-IMAP alsa-devel imlib2 libvorbis-devel rar alsa-firmware imlib2-loaders libxine1 sane alsa-tools k3b mad speex freeciv kipi-plugins mplayerplug-in
Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid
Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name?
Sure. Not implemented as of now, but from having looked at the smart source code [1] a few times, I'd say this would be very easy to implement, but has to be done for the shell, CLI and GUI interface.
Please open a feature request on the tracker [2].
[1] svn co http://svn.smartpm.python-hosting.com/trunk [2] http://tracker.labix.org/
What is meant in the output above with:
Installed packages (5): faac faad2 libffmpeg0 libmpcdec xvid
The package is not installed, see: linux:/etc/sysconfig # rpm -q faac package faac is not installed
Actually it means that to perform the upgrade you've asked for, smart will - upgrade the 19 packages mentioned in "Upgrading packages" - additionally install the 5 currently uninstalled packaged mentioned in "Installed packages" to fulfill the dependencies created by the upgrade process
Indeed, "Installed packages" might be a bit misleading. "Installing additional packages" would be more appropriate.
I've submitted a bug (+ patch) for this one: http://tracker.labix.org/issue72 (same for "Removed packages", should be "Removing packages")
cheers
What does smart mean with updating cache? Does it retrieve new information from an online server, see: linux:/usr/share/doc/packages/apt/lua-scripts/gpg-check> smart search yast2-tv Loading cache... Updating cache... ######################################## [100%] yast2-tv - YaST2 - TV Configuration linux:/usr/share/doc/packages/apt/lua-scripts/gpg-check> smart search yast2 Loading cache... Updating cache... ######################################## [100%] Why is the 2nd time the cache updated? Does smart use a local cache, if so where is it stored? This is as regular user so the local cached if owned by root can not be updated. Just testing smart with 1 of my packages. I choose gramps, which is already installed, it can be updated it works and as far as I know there are no problems with it. Still smart tells me the following packages are needed: richard@linux:~> smart install gramps Loading cache... Updating cache... ######################################## [100%] Computing transaction... Upgrading packages (1): gramps-2.0.9-0.suse1000.rb1@i586 Installed packages (8): gtksourceview-1.4.1-2@i586 libnvtv-0.4.7a-8@i586 gtkspell-2.0.11-5@i586 nautilus-cd-burner-2.12.0-4@i586 iso-codes-0.47-3@noarch python-gnome-extras-2.11.3-3@i586 libgtop-2.12.0-3@i586 totem-1.3.0-0.pm.0@i586 7.0MB of package files are needed. 12.9MB will be used. =========== Why are these packages needed/ Why do I needed a gnome CD burner for this application (it does not do anything with CDs at all).... The counts for totem, probably isocodes. Now if I answer "Y" to the question: Confirm changes? (Y/n): It crashes: Traceback (most recent call last): File "/usr/bin/smart", line 194, in ? main(sys.argv[1:]) This for now. With respect to have smart replace apt and as such leave apt out of the distribution; I think that smart is getting there, but that it is still lacking things and in some cases have bugs that are to be fixed. What I would like to see is, to have smart installed by default on suse (if suse want to push it) and provide apt online for 10.1 (not on CD as is the case with 10.0). With 10.2 apt can be moved from online to ..... I believe this scenario (descirbed) is needed to give smart some time to mature and to get susers used to smart. besides that the 10.1 alpha cycly is almost finished and as such no big new things can be added to 10.1... Provide more information online (wiki whatever) with tricks and such. I have not filed bugs, I leave that up to the people that want smart to succeed with suse. -- Regards, Richard Bos Without a home the journey is endless
Em Dom, 2006-01-08 às 16:55 +0100, Richard Bos escreveu:
Does smart support the functionality provided by: gpg-checker.lua, gpg-import.lua, pkglog.lua and post.lua inclusive configuration settings.
That should be done using plugins written in Python and dropped into Smart's "plugins" directory, althought it could be a little tricky to make some parts to merge well with smart without modifying some code elsewhere.
Heh, we want smart to replace apt, so it should do it with the same functionality or more.
It does more. Python scripts are more powerful than Lua scripts. And even if you want to maintain support for them, one could write a plugin for it.
No not all. It uses YAST to provide a GUI. The backend is stored in: /etc/cron.daily/suse-apt-upgrade
You could join the Smart mailing list and thake that discussion there. We could check if it's possible to implement.
I thought that YOU is already able to repomd formatted pkg repositories?
YOU is something completely different.
Could you explain what Mauricio is adding?
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
What does smart mean with updating cache? Does it retrieve new information from an online server, see:
Why smart loads/updates/saves the cache all the time? What is this cache anyway? http://labix.org/smart/faq#head-176755c0475d8090d9be199927d41febc9d7918e
Why are these packages needed/ Why do I needed a gnome CD burner for this
Check 'smart install --explain', that should tell you why those packages are needed.
Now if I answer "Y" to the question: It crashes:
The important part of the crash is the end, and you pasted just the initial part. :) -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
Hi, On Sun, 8 Jan 2006, Mauricio Teixeira wrote:
Em Dom, 2006-01-08 às 16:55 +0100, Richard Bos escreveu:
[...]
Could you explain what Mauricio is adding?
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
Now even the SUSE core team should see that it was/is wrong (false! bad! annoying!) to discard apt-rpm support this early before smart is ready to be a full-weight successor.
The important part of the crash is the end, and you pasted just the initial part. :)
What is that, "a crash"? Some new feature of smart, superceding apt-rpm? Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Em Seg, 2006-01-09 às 02:31 +0100, Eberhard Moenkeberg escreveu:
annoying!) to discard apt-rpm support this early before smart is ready to be a full-weight successor.
I prepared a very long answer for that, but then I remember "Don't Feed the Trolls". :) -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
On Sun, 8 Jan 2006, Mauricio Teixeira wrote:
I thought that YOU is already able to repomd formatted pkg repositories?
YOU is something completely different.
Could you explain what Mauricio is adding?
Correct. The metadata / patch description stuff is documented in the yast2-packagemanager-devel package (/usr/share/doc/packages/yast2-packagemanager/*).
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
... we have a feature request pending to enable repomd on YOU trees. Chances are good that we will get this to work for 10.1. (However there is one issue with this approach: The YOU trees contain scripts, which would only be accessible if SMART / $other_package_manager would implement the methods to access the metadata / patch description stuff of the YOU trees. I'm pretty sure APT isn't / wasn't able to access those parts of the updates either.) Regards Christoph
Em Seg, 2006-01-09 às 09:56 +0100, Christoph Thiel escreveu:
... we have a feature request pending to enable repomd on YOU trees.
That is very nice.
one issue with this approach: The YOU trees contain scripts, which would only be accessible if SMART / $other_package_manager would implement the
That is planned too. :) -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
Op maandag 9 januari 2006 09:56, schreef Christoph Thiel:
I thought that YOU is already able to repomd formatted pkg repositories?
YOU is something completely different.
Could you explain what Mauricio is adding?
Correct. The metadata / patch description stuff is documented in the yast2-packagemanager-devel package (/usr/share/doc/packages/yast2-packagemanager/*).
linux:~ # ls /usr/share/doc/packages/yast2-packagemanager/* /bin/ls: /usr/share/doc/packages/yast2-packagemanager/*: No such file or directory linux:~ # smart install /usr/share/doc/packages/yast2-packagemanager/pkg-sel-use-cases.txt Loading cache... Updating cache... ############################################### [100%] Computing transaction... Installed packages (4): curl-devel-7.14.0-2@i586 liby2util-devel-2.12.9-0.1@i586 rpm-devel-4.1.1-222@i586 yast2-packagemanager-devel-2.12.21-0.1@i586 3.3MB of package files are needed. 25.5MB will be used. Confirm changes? (Y/n): n Please copy and past the relevant text. So we do not all to install 25Megs and dig through it to read only 1k....
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
... we have a feature request pending to enable repomd on YOU trees. Chances are good that we will get this to work for 10.1.
What about repomd'ing everything that suse provides. Think about suse-people, suse-projects directories. But also provide similar repodata repositories for kotd, mozilla, wine and last but not least security updates!!!
(However there is one issue with this approach: The YOU trees contain scripts, which would only be accessible if SMART / $other_package_manager would implement the methods to access the metadata / patch description stuff of the YOU trees. I'm pretty sure APT isn't / wasn't able to access those parts of the updates either.)
See above this would be awesome to have, but if I was in charge of moving things from an apt repository to repodata I would put this somewhere on the bottom of my TODO list. Christoph any idea when we can have a repomd repository originated at suse similar to the apt repository? A new structure on the server can be created like apt: ..../suse/apt ..../suse/rmd/10.0-i586/ rmd = repomd or repo metadat (that is its official name) This directory can contain links to e.g. packman -> misc/packman/suse-10.0 suser-rbos -> ~misc/apt4rpm/10.0 base -> /ftp/pub/opensuse/distribution/SL-10.0-OSS/inst-source/suse update -> where are the updates located? It would be nice to see something happening in this direction... -- Richard Bos Without a home the journey is endless
On Mon, 9 Jan 2006, Richard Bos wrote:
Correct. The metadata / patch description stuff is documented in the yast2-packagemanager-devel package (/usr/share/doc/packages/yast2-packagemanager/*).
[...]
Please copy and past the relevant text. So we do not all to install 25Megs and dig through it to read only 1k....
It's too much stuff to copy and past via mail. I can provide you with a tar.bz2 copy of those files, if you like (via private mail).
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
... we have a feature request pending to enable repomd on YOU trees. Chances are good that we will get this to work for 10.1.
What about repomd'ing everything that suse provides. Think about suse-people, suse-projects directories. But also provide similar repodata repositories for kotd, mozilla, wine and last but not least security updates!!!
As those different repos are all managed by different people, it's not that easy to have all of them providing repomd stuff. At least the mozilla projects dirs have beend "repomded" already...
(However there is one issue with this approach: The YOU trees contain scripts, which would only be accessible if SMART / $other_package_manager would implement the methods to access the metadata / patch description stuff of the YOU trees. I'm pretty sure APT isn't / wasn't able to access those parts of the updates either.)
See above this would be awesome to have, but if I was in charge of moving things from an apt repository to repodata I would put this somewhere on the bottom of my TODO list. Christoph any idea when we can have a repomd repository originated at suse similar to the apt repository?
A new structure on the server can be created like apt: ..../suse/apt ..../suse/rmd/10.0-i586/ rmd = repomd or repo metadat (that is its official name) This directory can contain links to e.g. packman -> misc/packman/suse-10.0 suser-rbos -> ~misc/apt4rpm/10.0 base -> /ftp/pub/opensuse/distribution/SL-10.0-OSS/inst-source/suse update -> where are the updates located?
It would be nice to see something happening in this direction...
IMHO this is something that we will need (and have) as soon as the build services goes public with a lot of different repos. Regards Christoph
Op maandag 9 januari 2006 11:07, schreef Christoph Thiel:
What about repomd'ing everything that suse provides. Think about suse-people, suse-projects directories. But also provide similar repodata repositories for kotd, mozilla, wine and last but not least security updates!!!
As those different repos are all managed by different people, it's not that easy to have all of them providing repomd stuff. At least the mozilla projects dirs have beend "repomded" already...
And yours, kraxel's, mine, kolab, packman, suser-guru (I think). Now build a repodata community around them (see below)!
(However there is one issue with this approach: The YOU trees contain scripts, which would only be accessible if SMART / $other_package_manager would implement the methods to access the metadata / patch description stuff of the YOU trees. I'm pretty sure APT isn't / wasn't able to access those parts of the updates either.)
See above this would be awesome to have, but if I was in charge of moving things from an apt repository to repodata I would put this somewhere on the bottom of my TODO list. Christoph any idea when we can have a repomd repository originated at suse similar to the apt repository?
A new structure on the server can be created like apt: ..../suse/apt ..../suse/rmd/10.0-i586/ rmd = repomd or repo metadat (that is its official name) This directory can contain links to e.g. packman -> misc/packman/suse-10.0 suser-rbos -> ~misc/apt4rpm/10.0 base -> /ftp/pub/opensuse/distribution/SL-10.0-OSS/inst-source/suse update -> where are the updates located?
It would be nice to see something happening in this direction...
IMHO this is something that we will need (and have) as soon as the build services goes public with a lot of different repos.
Christoph use your account at gwdg and start buidling the structure above. It would be a good start and it would give insight what is needed. You can even link your own and kraxel's and mozilla repodata into that structure. -- Richard Bos Without a home the journey is endless
On Mon, 9 Jan 2006, Richard Bos wrote: [...]
As those different repos are all managed by different people, it's not that easy to have all of them providing repomd stuff. At least the mozilla projects dirs have beend "repomded" already...
And yours, kraxel's, mine, kolab, packman, suser-guru (I think). Now build a repodata community around them (see below)!
[...]
It would be nice to see something happening in this direction...
IMHO this is something that we will need (and have) as soon as the build services goes public with a lot of different repos.
Christoph use your account at gwdg and start buidling the structure above. It would be a good start and it would give insight what is needed. You can even link your own and kraxel's and mozilla repodata into that structure.
I'm not so sure if it makes sense to have all that stuff centered around ftp.gwdg.de -- with the build service and all the infrastructure that is accompanying it, we will have a much more openSUSE/SUSE centered approach (to be mirrored by all SUSE mirrors then). Regards Christoph
Op maandag 9 januari 2006 11:07, schreef Christoph Thiel:
Please copy and past the relevant text. So we do not all to install 25Megs and dig through it to read only 1k....
It's too much stuff to copy and past via mail. I can provide you with a tar.bz2 copy of those files, if you like (via private mail).
I did not ask for the development guide. I asked is YOU repodata aware? I think the answer is no, but it is being worked on. Than; is yast2 --software (or what is the option) repodata aware. I don't, guess you do. PS: this is actually a different topic than smart, but okay I think we can cope with this. -- Richard Bos Without a home the journey is endless
On Mon, 9 Jan 2006, Richard Bos wrote:
I did not ask for the development guide. I asked is YOU repodata aware? I think the answer is no, but it is being worked on.
Right, the answer is no: YOU uses it's own so called patch descriptions (neither YaST2 stuff nor rpmmd). [This is covered in #128607]
Than; is yast2 --software (or what is the option) repodata aware. I don't, guess you do.
Even if I don't really understand the second sentence, let me comment on this ;) YaST2 is able to access/use repomd repos since SUSE Linux 10.0, but the "old" YaST2 metadata is still used per default on CDs/DVDs and ftp trees (but those trees also contain repodata). Regards Christoph
Op maandag 9 januari 2006 01:17, schreef Mauricio Teixeira:
Em Dom, 2006-01-08 às 16:55 +0100, Richard Bos escreveu:
Does smart support the functionality provided by: gpg-checker.lua, gpg-import.lua, pkglog.lua and post.lua inclusive configuration settings.
That should be done using plugins written in Python and dropped into Smart's "plugins" directory, althought it could be a little tricky to make some parts to merge well with smart without modifying some code elsewhere.
Heh, we want smart to replace apt, so it should do it with the same functionality or more.
It does more. Python scripts are more powerful than Lua scripts. And even if you want to maintain support for them, one could write a plugin for it.
The only thing it does more is processing of repodata. That is very good, but if smart should replace apt it should provide the same or more functionality. So as long as smart does not provide similar functionality to check gpg keys, import gpg keys, launch post scripts, keep an install and remove log and other things I mentioned in other emails it does LESS! These are things I notice as SUSER, the repodata I do not notice as user, it's the server admin that will be happy with it.
No not all. It uses YAST to provide a GUI. The backend is stored in: /etc/cron.daily/suse-apt-upgrade
You could join the Smart mailing list and thake that discussion there. We could check if it's possible to implement.
Heh, but you (and others) want smart to supersede apt. I contribruted apt and all its goodies. It's up to you to make smart better.
I thought that YOU is already able to repomd formatted pkg repositories?
YOU is something completely different.
The question was: "is YOU already able to use repomd formatted repositories"
Could you explain what Mauricio is adding?
Just dealing with YaST2 sources for now, not YOU yet. For now you need to add the updates repository in APT format. But I plan to add YOU support in all of it's glory as soon as possible. :)
What is meant with YOU support?? Processing of the repomd files?
What does smart mean with updating cache? Does it retrieve new information from an online server, see:
Why smart loads/updates/saves the cache all the time? What is this cache anyway? http://labix.org/smart/faq#head-176755c0475d8090d9be199927d41febc9d7918e
Not clear. I understand the loading I think (reading data from disk), but what is it doing during update. Does it contact the server and retrieve data from there, or is doing something else.
Now if I answer "Y" to the question: It crashes:
The important part of the crash is the end, and you pasted just the initial part. :)
Well it is easy reproducable. Install a package as regular user, withour root permission. -- Richard Bos Without a home the journey is endless
Em Seg, 2006-01-09 às 10:42 +0100, Richard Bos escreveu:
YOU is something completely different. The question was: "is YOU already able to use repomd formatted repositories"
SUSE plans to. Meanwhile it's something completely different. But we do expect to have this working on Smart either.
What is meant with YOU support?? Processing of the repomd files?
Processing the "something else" repository format, patch scripts, etc.
what is it doing during update. Does it contact the server and retrieve data from there, or is doing something else.
It checks if something changed, like the rpm database or any other file from any other channel (stored on /var/lib/smart/channels). If it detects any changes, it reads everything (rpm database and channel files) to reconstruct the data. It only retrieves files from network when you do an 'update'.
Well it is easy reproducable. Install a package as regular user, withour root permission.
I don't get a crash, I get an obvious error: [Errno 13] Permission denied: '/var/lib/smart/packages/sazanami-fonts-20040629-7.noarch.rpm.part' Since I can't write to the cache, I can't install. Even if I do a direct rpm install, I get: error: db4 error(13) from dbcursor->c_put: Permission denied error: error(13) allocating new package instance Which means the crash you got isn't related to the regular user installing anything at all. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
Op maandag 9 januari 2006 10:01, schreef Mauricio Teixeira:
what is it doing during update. Does it contact the server and retrieve data from there, or is doing something else.
It checks if something changed, like the rpm database or any other file from any other channel (stored on /var/lib/smart/channels). If it detects any changes, it reads everything (rpm database and channel files) to reconstruct the data. It only retrieves files from network when you do an 'update'.
Could the text be changed from 'Updating cache' to 'Updating local cache' or do not show the '#########'. I (and others I think) associate those '#####' with downloading (retrieving) data from a remote server.
Well it is easy reproducable. Install a package as regular user, withour root permission.
I don't get a crash, I get an obvious error:
[Errno 13] Permission denied: '/var/lib/smart/packages/sazanami-fonts-20040629-7.noarch.rpm.part'
Me too now. I don't have the traceback, that's a pity. Why is there no check whether the directory is writable because if this done with many packages, it starts to download (it at least) tries and will than tell for each package that the directory is not writavle. Besides that is time consuming. Please check the download directory permission first.
Since I can't write to the cache, I can't install. Even if I do a direct rpm install, I get:
error: db4 error(13) from dbcursor->c_put: Permission denied error: error(13) allocating new package instance
Which means the crash you got isn't related to the regular user installing anything at all.
-- Richard Bos Without a home the journey is endless
On Sun, 8 Jan 2006, Richard Bos wrote: [...]
This for now. With respect to have smart replace apt and as such leave apt out of the distribution; I think that smart is getting there, but that it is still lacking things and in some cases have bugs that are to be fixed.
What I would like to see is, to have smart installed by default on suse (if suse want to push it) and provide apt online for 10.1 (not on CD as is the case with 10.0). With 10.2 apt can be moved from online to ..... I believe this scenario (descirbed) is needed to give smart some time to mature and to get susers used to smart. besides that the 10.1 alpha cycly is almost finished and as such no big new things can be added to 10.1...
We have just decided to give apt-rpm / apt4rpm a last grace period and readded it to the distro. It will _only_ hit Factory (and later on the ftp trees of SUSE Linux 10.1). Many thanks to Philipp Thomas for taking the maintainership of the apt packages! Having said that, I'd like call for testing SMART as much as possible. This is the project / package manager that will sooner or later supersede apt, so be sure to test it NOW and provide feedback ;) [The version of SMART (0.40) that's in 10.0 is quite suboptimal -- please try the one in Factory / 10.1, which is much better!] To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)? Regards Christoph
On 2006-01-12 16:36:07 +0100, Christoph Thiel wrote:
Having said that, I'd like call for testing SMART as much as possible. This is the project / package manager that will sooner or later supersede apt, so be sure to test it NOW and provide feedback ;) [The version of SMART (0.40) that's in 10.0 is quite suboptimal -- please try the one in Factory / 10.1, which is much better!]
for all people who want to test the newer smart releases on 10.0 pascal provides rpms on his website. darix
On Thu, 2006-01-12 at 16:47 +0100, Paul Borel wrote:
why the distribution is not in DVD ?
I always support the distro packer, the latest was SUSE 10.0 for €59. I use the x86_64 also. The DVD is DL, but I successfully copied it as backup, using the backup-copy to install. :-) Al
okay but i see that the 5cd of opensuse but why it don't also in DVD version ?
On Thu, 2006-01-12 at 16:47 +0100, Paul Borel wrote:
why the distribution is not in DVD ?
I always support the distro packer, the latest was SUSE 10.0 for €59. I use the x86_64 also. The DVD is DL, but I successfully copied it as backup, using the backup-copy to install.
:-) Al
-------------------------------------------------------------------- - To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
__________ Information NOD32 1.1363 (20060112) __________
Ce message a ete verifie par NOD32 Antivirus System. http://www.nod32.com
Op donderdag 12 januari 2006 16:36, schreef Christoph Thiel:
We have just decided to give apt-rpm / apt4rpm a last grace period and readded it to the distro. It will _only_ hit Factory (and later on the ftp trees of SUSE Linux 10.1). Many thanks to Philipp Thomas for taking the maintainership of the apt packages!
You guys are superb!
Having said that, I'd like call for testing SMART as much as possible. This is the project / package manager that will sooner or later supersede apt, so be sure to test it NOW and provide feedback ;) [The version of SMART (0.40) that's in 10.0 is quite suboptimal -- please try the one in Factory / 10.1, which is much better!]
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Can't (are we allowed) to put [suse]/[oss]/[opensuse] in the title or another field in the bugreport. What about adding a 'topic' = opensuse to the roundup bag tracker (at the moment it does not seem to be used). -- Richard Bos Without a home the journey is endless
On Thu, 12 Jan 2006, Richard Bos wrote: [...]
Having said that, I'd like call for testing SMART as much as possible. This is the project / package manager that will sooner or later supersede apt, so be sure to test it NOW and provide feedback ;) [The version of SMART (0.40) that's in 10.0 is quite suboptimal -- please try the one in Factory / 10.1, which is much better!]
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Can't (are we allowed) to put [suse]/[oss]/[opensuse] in the title or another field in the bugreport. What about adding a 'topic' = opensuse to the roundup bag tracker (at the moment it does not seem to be used).
I guess having SUSE in the title would be sufficient -- but a lot of bugs that are hidden in SMART might not be exclusive to SUSE. Regards Christoph
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels? -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
On Fri, 13 Jan 2006, James Ogley wrote:
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels?
No, this is rather problematic from a legal perspective. Regards Christoph
Am Freitag, 13. Januar 2006 11:08 schrieb Christoph Thiel:
On Fri, 13 Jan 2006, James Ogley wrote:
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels?
No, this is rather problematic from a legal perspective. Seems not to be a problem for Mark Shuttleworth ;-)
Just paste the lines and make a comment mark in front of it, please... -- Üdvözlettel -- Mit freundlichen Grüssen, Marcel Hilzinger
On Fri, 2006-01-13 at 11:08 +0100, Christoph Thiel wrote:
On Fri, 13 Jan 2006, James Ogley wrote:
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels?
No, this is rather problematic from a legal perspective.
Perhaps then the people that provide third party channels can publish their information somewhere like they currently do for apt/YaST. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Perhaps then the people that provide third party channels can publish their information somewhere like they currently do for apt/YaST.
Perhaps we can attach (or link to) channel info files from the repositories page on opensuse.org -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christoph Thiel wrote:
On Fri, 13 Jan 2006, James Ogley wrote:
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)? Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels?
No, this is rather problematic from a legal perspective.
i.e. we're still waiting for comments from Novell's legal dept. about this ;)
Adrian ? AJ ?
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Am Samstag, 14. Januar 2006 01:55 schrieb Pascal Bleser:
Christoph Thiel wrote:
On Fri, 13 Jan 2006, James Ogley wrote:
To assist SMART to actually get there, I'd also like to collect a list of "missing features" and "things that need to be fixed" until SMART can do the job apt does for you guys. Any volunteers to create a wiki page and file bugs (preferably at http://tracker.labix.org/)?
Is the plan to include third party channels, and if so would you like the maintainers to send you channel information files for /etc/smart/channels?
No, this is rather problematic from a legal perspective.
i.e. we're still waiting for comments from Novell's legal dept. about this ;)
Adrian ? AJ ?
I can't discuss legal issues in detail here, but we can't allow links to illegal content on our systems. This means we have to remove them, if anyone is adding such a link. A second issue is for me that we can't guarantee that the content of a binary rpm is really build from the source rpm beside. So any possible bad thing could happen when you use (or even only install) it. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
I can't discuss legal issues in detail here, but we can't allow links to illegal content on our systems. This means we have to remove them, if anyone is adding such a link.
libdvdcss2 bites us in the ass yet again ;)
A second issue is for me that we can't guarantee that the content of a binary rpm is really build from the source rpm beside. So any possible bad thing could happen when you use (or even only install) it.
I wonder whether a naming convention that made it clear which are third-party repos would cover this. -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
* James Ogley
I can't discuss legal issues in detail here, but we can't allow links to illegal content on our systems. This means we have to remove them, if anyone is adding such a link.
libdvdcss2 bites us in the ass yet again ;)
Looks like a prominent SUSE user, hint hint (James Ogley), might need to provide a list of links on his web site. Or maybe someone in a location that libdvdcss(2) is not considered to be unlawful. List discussion and word-of-mouth would have to suffice to keep that site widely known. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Looks like a prominent SUSE user, hint hint (James Ogley), might need to provide a list of links on his web site. Or maybe someone in a location that libdvdcss(2) is not considered to be unlawful. List discussion and word-of-mouth would have to suffice to keep that site widely known.
lol! :) I believe the link you want is http://packman.links2linux.org/?action=122 Go PackMan, Go, go, go PackMan! -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
Hi, On Sun, 15 Jan 2006, James Ogley wrote:
Looks like a prominent SUSE user, hint hint (James Ogley), might need to provide a list of links on his web site. Or maybe someone in a location that libdvdcss(2) is not considered to be unlawful. List discussion and word-of-mouth would have to suffice to keep that site widely known.
lol! :)
I believe the link you want is http://packman.links2linux.org/?action=122
Go PackMan, Go, go, go PackMan!
This way, no incriminated "tool" or "program" is offered - only some kind of help to reach the goal. But not a safe way I guess... Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Patrick Shanahan wrote:
* James Ogley
[01-14-06 12:34]:
libdvdcss2 bites us in the ass yet again ;)
Looks like a prominent SUSE user, hint hint (James Ogley), might need to provide a list of links on his web site. Or maybe someone in a location that libdvdcss(2) is not considered to be unlawful.
Norway comes to mind. IIRC, a court officially backed up everybody's right to see DVDs on alternative operating systems. I can't tell a number of this process, but the kid, who first made DeCSS available was Norwegian and drawn to court there. The sentence was one of acquittal. The judgment I just cited should have been in this or a related process. Ciao Siegbert
Em Dom, 2006-01-08 às 11:56 +0100, Pascal Bleser escreveu:
Maybe one could even make a MIME handler for *.channel files (one-click channel adding) ;) *.channel => kdesu - -c "konsole -e 'smart channel --add'"
There is already something similar for KDE. Check under "contrib/servicemenus" on Smart sources.
Please remove this line "Run "smart command --help" for more information" from 'smart --help". If run 'smart --help' I don't get more information.
"smart command --help" means "smart install --help", "smart upgrade --help", etc.
Where is smart manpage? Just create one with help2man. Hmm.. yes, a manpage would be great :)
That should be me to work on that too, and I even started it, but then directions changed and we decided to write a complete "User's Guide" instead of a minimalistic man page. So the doc development is quite slow right now since it's a very complex task to write something really useful/interesting.
What is the smart similar command for: 'apt --sources security.list upgrade' This only upgrades the security packages. I assume it exists but 'man smart'
I'm not familiar with that command on APT, but I'll assume you want one of those: a) 'smart update mychannel' will fetch package information for 'mychannel' only. b) If you want to upgrade packages that come from 'mychannel' only, and leave the others alone, you'd need to disable all other channels and then run an upgrade (sorry, there's no easy way I know).
Would require YOU repository support in Smart. That might be on Mauricio's TODO list, once yast2 repository support is sufficently tested ;)
Smart guy you are. ;)
Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name?
smart upgrade --urls (or) smart upgrade --explain
- - additionally install the 5 currently uninstalled packaged mentioned in "Installed packages" to fulfill the dependencies created by the upgrade process
That could be clarified by using "--stepped" switch. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
Op maandag 9 januari 2006 01:04, schreef Mauricio Teixeira:
Where is smart manpage? Just create one with help2man.
Hmm.. yes, a manpage would be great :)
That should be me to work on that too, and I even started it, but then directions changed and we decided to write a complete "User's Guide" instead of a minimalistic man page. So the doc development is quite slow right now since it's a very complex task to write something really useful/interesting.
Perhaps Pascal can add an 'help2man' line during his rpmbuild.... Or perhaps it can be added to the Makefile...
What is the smart similar command for: 'apt --sources security.list upgrade' This only upgrades the security packages. I assume it exists but 'man smart'
I'm not familiar with that command on APT, but I'll assume you want one of those:
a) 'smart update mychannel' will fetch package information for 'mychannel' only.
b) If you want to upgrade packages that come from 'mychannel' only, and leave the others alone,
I want this.
you'd need to disable all other channels and then run an upgrade (sorry, there's no easy way I know).
So please have this added to smart (it should supersede apt, that is why apt is left out of suse remember...) Disabling all other channels is not at all userfriendly. Hopefully you'll put this on the smart todo list.
Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name?
smart upgrade --urls
this does it: linux:~ # smart install --urls gramps Loading cache... Updating cache... ############################################### [100%] Computing transaction... ftp://ftp.gwdg.de/pub/linux/misc/apt4rpm/10.0/gramps-2.0.9-0.suse1000.rb1.i586.rpm http://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/RPMS.base/gtksourceview...
(or) smart upgrade --explain
--explain does not, it would if it would include the 'alias' . BTW: --explain is not correct. As I still don't know how it works, it's only more verbose. So please change it into --verbose.... ..... Installed packages (8): gtksourceview-1.4.1-2@i586 Required By: python-gnome-extras-2.11.3-3@i586 (installed) ..... Please change 'Installed' into 'New' those packages are not installed (yet) they are new (for my sysytem).
- - additionally install the 5 currently uninstalled packaged mentioned in "Installed packages" to fulfill the dependencies created by the upgrade process
That could be clarified by using "--stepped" switch.
No not at all. -- Richard Bos Without a home the journey is endless
Em Seg, 2006-01-09 às 11:16 +0100, Richard Bos escreveu:
Disabling all other channels is not at all userfriendly. Hopefully you'll put this on the smart todo list.
Please, ask for it on http://tracker.labix.org -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
Op maandag 9 januari 2006 01:04, schreef Mauricio Teixeira:
Where is smart manpage? Just create one with help2man. Hmm.. yes, a manpage would be great :) That should be me to work on that too, and I even started it, but then directions changed and we decided to write a complete "User's Guide" instead of a minimalistic man page. So the doc development is quite slow right now since it's a very complex task to write something really useful/interesting.
Perhaps Pascal can add an 'help2man' line during his rpmbuild.... Or perhaps it can be added to the Makefile...
Never used help2man but I'll have a look and see whether it works with smart. The problem is that with smart you don't see all the help with "--help", it's smart install --help smart channel --help smart search --help etc..... I doubt help2man will work.
What is the smart similar command for: 'apt --sources security.list upgrade' This only upgrades the security packages. I assume it exists but 'man smart' I'm not familiar with that command on APT, but I'll assume you want one of those:
a) 'smart update mychannel' will fetch package information for 'mychannel' only.
b) If you want to upgrade packages that come from 'mychannel' only, and leave the others alone,
I want this.
Yes, I want it too :) smart upgrade --channel=mychannel smart upgrade --channel=mychannel kde* That would be great. Just created a ticket for it: http://tracker.labix.org/issue76
you'd need to disable all other channels and then run an upgrade (sorry, there's no easy way I know).
So please have this added to smart (it should supersede apt, that is why apt is left out of suse remember...) Disabling all other channels is not at all userfriendly. Hopefully you'll put this on the smart todo list.
I agree. Having an option for upgrade and install would be needed. See above for TODO.
Now from which repositories are these packages installed. With apt does can be deducted from the version number. Would smart be able to put the component name behind the rpm name? smart upgrade --urls
this does it: linux:~ # smart install --urls gramps Loading cache... Updating cache... ############################################### [100%]
Computing transaction... ftp://ftp.gwdg.de/pub/linux/misc/apt4rpm/10.0/gramps-2.0.9-0.suse1000.rb1.i586.rpm http://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/RPMS.base/gtksourceview...
(or) smart upgrade --explain
--explain does not, it would if it would include the 'alias' . BTW: --explain is not correct. As I still don't know how it works, it's only more verbose. So please change it into --verbose....
..... Installed packages (8): gtksourceview-1.4.1-2@i586 Required By: python-gnome-extras-2.11.3-3@i586 (installed) .....
Please change 'Installed' into 'New' those packages are not installed (yet) they are new (for my sysytem).
I already submitted a patch to change "Installed" into "Installing" and "Removed" into "Removing", hence it is currently a mix of active/passive form (it writes "Upgrading" but "Installed"). http://tracker.labix.org/issue72
- - additionally install the 5 currently uninstalled packaged mentioned in "Installed packages" to fulfill the dependencies created by the upgrade process That could be clarified by using "--stepped" switch.
No not at all.
I agree, --stepped doesn't quite do the job. "Installed" must be renamed to "Installing".
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Em Sáb, 2006-01-07 às 13:25 +0100, Richard Bos escreveu:
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir
Hum... It always works for me, either with FTP or HTTP (basic auth).
Why does smart not read the /etc/yum.repos.d directory? I now have to define the repositories twice :(
Smart won't check what package manager you already have installed. Even if it would, how can it be sure which one you're using where you're running SUSE but using APT or YUM, and not YaST? :) You could check if someone already wrote some script to convert channel info. I know there is one for APT.
Smart is not integrated with suse... I mean the "OK" button is at the right
And it's not intended to be. Smart isn't designed to be attached to any distro at all. It's completely independent.
There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would
alias = netmask name = Mauricio Teixeira alias = yaloki name = Pascal Blesser alias = suse-base name = Suse Base Packages ...
Is there a central directory that shows which repositories are available?
That should be up to the distro (or contributers) to make it available. Check for example this site: http://easyurpmi.zarb.org (central mirror listing for Mandriva). -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
Op maandag 9 januari 2006 00:39, schreef Mauricio Teixeira:
Em Sáb, 2006-01-07 às 13:25 +0100, Richard Bos escreveu:
What does not work: are urls with login and passwords, like: ftp://login:password@host.domain.tld/dir
smart : Fetching information for 'Mijn pakketten op gwdg on linux01'... -> ftp://apt4rpm:*@linux01.gwdg.de/apt4rpm/10.0/repodata/repomd.xml repomd.xml [ 29%] error: Failed acquiring release file for 'Mijn pakketten op gwdg on linux01': error: ftp://apt4rpm:*@linux01.gwdg.de/apt4rpm/10.0/repodata/repomd.xml: 550 Failed to change directory. not so smart (ftp): linux:/var/lib/smart/channels # ftp ftp://apt4rpm:*@linux01.gwdg.de/apt4rpm/10.0/repodata/ Connected to linux01.gwdg.de. 220 "Welcome to linux01.gwdg.de FTP service." 331 Please specify the password. 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. 200 Switching to Binary mode. 250 Directory successfully changed. 250 Directory successfully changed. 250 Directory successfully changed.
Hum... It always works for me, either with FTP or HTTP (basic auth).
Tell me what is different than (my firewall maybe)?
There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would
alias = netmask name = Mauricio Teixeira
alias = yaloki name = Pascal Blesser
alias = suse-base name = Suse Base Packages
The last one clearly shows that 'name' is not the right one. 'description' is
better as it is more general. If you want to keep a name than use it as 3rd
(info only field). So it can be used as:
name: Pascal Blesser
Is there a central directory that shows which repositories are available?
That should be up to the distro (or contributers) to make it available. Check for example this site: http://easyurpmi.zarb.org (central mirror listing for Mandriva).
So, why is suse not providing this? Or anybody else that wants suse to switch to repodata. Have a look at: ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-i386/examples -- Richard Bos Without a home the journey is endless
Em Seg, 2006-01-09 às 11:56 +0100, Richard Bos escreveu:
error: Failed acquiring release file for 'Mijn pakketten op gwdg on linux01': error: ftp://apt4rpm:*@linux01.gwdg.de/apt4rpm/10.0/repodata/repomd.xml: 550
If the home for 'apt4rpm' is '/home/apt4rpm', and the ftp server isn't chrooted, the above url would point to the root of the server. If that is the case, you should use the full path.
linux:/var/lib/smart/channels # ftp ftp://apt4rpm:*@linux01.gwdg.de/apt4rpm/10.0/repodata/
This probably worked because it did "cd apt4rpm", and not "cd /apt4rpm" (smart interprets ftp://[host][/fullpath]). -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]
participants (15)
-
Adrian Schröter
-
Al Active
-
Christoph Thiel
-
Eberhard Moenkeberg
-
James Ogley
-
Ken Schneider
-
Marcel Hilzinger
-
Marcus Rueckert
-
Mauricio Teixeira
-
Mauricio Teixeira (netmask)
-
Pascal Bleser
-
Patrick Shanahan
-
Paul Borel
-
Richard Bos
-
Siegbert Baude