From frateraec at gmail.com Fri Aug 1 04:38:38 2014 From: frateraec at gmail.com (Frater AEC) Date: Fri, 1 Aug 2014 08:38:38 -0300 Subject: Smart 1.4.1 error in PCLOS 2014 Message-ID: Hi! Smart Package Manager 1.4.1 worked well in PCLOS. PCLOS is a APT-RPM rolling release distro. However, in some cases installation or upgrade it presents conflict error: # smart install task-pulseaudio Carregando o cache... Atualizando cache... ######################################## [100%] Calculando transa??o... Instalando pacotes (13): alsa-plugins-pulse-config-1.0.28-1pclos2014 at i586 libalsa-plugins-pulseaudio-1.0.28-1pclos2014 at i586 pulseaudio-4.0-6pclos2013 at i586 pulseaudio-client-config-4.0-6pclos2013 at i586 pulseaudio-esound-compat-4.0-6pclos2013 at i586 pulseaudio-module-bluetooth-4.0-6pclos2013 at i586 pulseaudio-module-equalizer-4.0-6pclos2013 at i586 pulseaudio-module-jack-4.0-6pclos2013 at i586 pulseaudio-module-lirc-4.0-6pclos2013 at i586 pulseaudio-module-x11-4.0-6pclos2013 at i586 pulseaudio-module-zeroconf-4.0-6pclos2013 at i586 pulseaudio-utils-4.0-6pclos2013 at i586 task-pulseaudio-2012.2.0-5pclos2014 at noarch Removendo pacotes (1): task-pulseaudio-remove-2012.12.0-4pclos2014 at noarch 4.3MB ser?o utilizados. Confirma mudan?as? (S/n): s Efetuando transa??o... Preparando... ######################################## [ 0%] erro: file /etc/esd.conf from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 erro: file /usr/bin/esd from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 It ends without completing the installation or upgrade. With "apt-get install" installs without displaying errors. Being pclos rolling release distro some packages only upgrade with the command "apt-get dist-upgrade". And all the packages that need to "apt-rpm dist-upgrade" to upgrade, are those with conflict error in smart. So I'm stuck in apt-get and I can not use only smart in pclos. This problem happens to anyone else? Any tips on how to resolve? I can to solve with configuration or is a bug that needs to be reported? Thanks! FraterLinux -------------- next part -------------- An HTML attachment was scrubbed... URL: From tarek.elsherbiny at gmail.com Tue Aug 26 06:19:14 2014 From: tarek.elsherbiny at gmail.com (Tarek El-Sherbiny) Date: Tue, 26 Aug 2014 14:19:14 +0100 Subject: smart upgrade is not working anymore Message-ID: Hi All, I ended up in a situation where my smart upgrade command is not doing anything. However smart update is detecting the more recent packages on the repo $Updating cache... #################################################################################### [100%] Channels have 3 new packages: example-0.1-r4.0 at cortexa9hf_vfp_neon example-dbg-0.1-r4.0 at cortexa9hf_vfp_neon example-dev-0.1-r4.0 at cortexa9hf_vfp_neon Saving cache... $smart upgrade Loading cache... Updating cache... #################################################################################### [100%] Computing transaction... No interesting upgrades available. when I tried to force the installation of the package manually I've got the following error: $smart install example Loading cache... Updating cache... #################################################################################### [100%] Computing transaction... Installing packages (6): bash-4.2-r6 at cortexa9hf_vfp_neon libtinfo5-5.9-r15.1 at cortexa9hf_vfp_neon example-0.1-r4.0 at cortexa9hf_vfp_neon ncurses-terminfo-base-5.9-r15.1 at cortexa9hf_vfp_neon libc6-2.18-r0 at cortexa9hf_vfp_neon update-alternatives-cworth-1:0.1.8+svnr653-r13.0 at cortexa9hf_vfp_neon 1.9MB of package files are needed. 3.7MB will be used. Confirm changes? (Y/n): Y Fetching packages... -> http://192.168.113.70/utilite/rpm/cortexa9hf_vfp_neon/example-0.1-r4.0.cortexa9hf_vfp_neon.rpm example-0.1-r4.0.cortexa9hf_vfp_neon.rpm #################################################################################### [100%] Committing transaction... Preparing... #################################################################################### [ 0%] error: package libc6-2.18-r0.cortexa9hf_vfp_neon is already installed error: package ncurses-terminfo-base-5.9-r15.1.cortexa9hf_vfp_neon is already installed error: package bash-4.2-r6.cortexa9hf_vfp_neon is already installed error: package libtinfo5-5.9-r15.1.cortexa9hf_vfp_neon is already installed How do I fix the upgrade command ? Thanks -- *Tarek* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.hatle at windriver.com Tue Aug 26 06:41:38 2014 From: mark.hatle at windriver.com (Mark Hatle) Date: Tue, 26 Aug 2014 08:41:38 -0500 Subject: smart upgrade is not working anymore In-Reply-To: References: Message-ID: <53FC8E92.80205@windriver.com> On 8/26/14, 8:19 AM, Tarek El-Sherbiny wrote: > Hi All, > > I ended up in a situation where my smart upgrade command is not doing anything. > However smart update is detecting the more recent packages on the repo This looks like you are using OpenEmbedded or the Yocto Project. You might get more response asking there lists. However, the first thing you need to do is check that you have the rpm-sys loaded, as well as the remote feed. List your available sources, if rpm-sys is missing that is your problem. It's only able to check the remote feed and not the local system. The other thing to check is that your /etc/rpm/platform file is setup properly. This file is used by RPM5 to explain compatibility with packages. If it's not configured properly you can get into a situation where the smart side tries an upgrade and the RPM side determines it's not compatible. --Mark > $Updating cache... > #################################################################################### [100%] > > Channels have 3 new packages: > example-0.1-r4.0 at cortexa9hf_vfp_neon > example-dbg-0.1-r4.0 at cortexa9hf_vfp_neon > example-dev-0.1-r4.0 at cortexa9hf_vfp_neon > > Saving cache... > > $smart upgrade > Loading cache... > Updating cache... > #################################################################################### [100%] > > Computing transaction... > No interesting upgrades available. > > when I tried to force the installation of the package manually I've got the > following error: > > $smart install example > Loading cache... > Updating cache... > #################################################################################### [100%] > > Computing transaction... > > Installing packages (6): > bash-4.2-r6 at cortexa9hf_vfp_neon > libtinfo5-5.9-r15.1 at cortexa9hf_vfp_neon > example-0.1-r4.0 at cortexa9hf_vfp_neon > ncurses-terminfo-base-5.9-r15.1 at cortexa9hf_vfp_neon > libc6-2.18-r0 at cortexa9hf_vfp_neon > update-alternatives-cworth-1:0.1.8+svnr653-r13.0 at cortexa9hf_vfp_neon > > 1.9MB of package files are needed. 3.7MB will be used. > > Confirm changes? (Y/n): Y > > Fetching packages... > -> > http://192.168.113.70/utilite/rpm/cortexa9hf_vfp_neon/example-0.1-r4.0.cortexa9hf_vfp_neon.rpm > > example-0.1-r4.0.cortexa9hf_vfp_neon.rpm > #################################################################################### > [100%] > > Committing transaction... > Preparing... > #################################################################################### > [ 0%] > error: package libc6-2.18-r0.cortexa9hf_vfp_neon is already installed > error: package ncurses-terminfo-base-5.9-r15.1.cortexa9hf_vfp_neon is already > installed > error: package bash-4.2-r6.cortexa9hf_vfp_neon is already installed > error: package libtinfo5-5.9-r15.1.cortexa9hf_vfp_neon is already installed > > > How do I fix the upgrade command ? > > Thanks > > -- > /Tarek/ From tarek.elsherbiny at gmail.com Wed Aug 27 00:00:28 2014 From: tarek.elsherbiny at gmail.com (Tarek El-Sherbiny) Date: Wed, 27 Aug 2014 08:00:28 +0100 Subject: smart upgrade is not working anymore In-Reply-To: <53FC8E92.80205@windriver.com> References: <53FC8E92.80205@windriver.com> Message-ID: Hi Mark, Thanks you very much for the info. You are right. I have deleted the rpm-sys channel by mistake. I've added the channel again and now it's all working fine. Thanks again. Tarek On Tue, Aug 26, 2014 at 2:41 PM, Mark Hatle wrote: > On 8/26/14, 8:19 AM, Tarek El-Sherbiny wrote: > >> Hi All, >> >> I ended up in a situation where my smart upgrade command is not doing >> anything. >> However smart update is detecting the more recent packages on the repo >> > > This looks like you are using OpenEmbedded or the Yocto Project. You > might get more response asking there lists. > > However, the first thing you need to do is check that you have the rpm-sys > loaded, as well as the remote feed. List your available sources, if > rpm-sys is missing that is your problem. It's only able to check the > remote feed and not the local system. > > The other thing to check is that your /etc/rpm/platform file is setup > properly. This file is used by RPM5 to explain compatibility with > packages. If it's not configured properly you can get into a situation > where the smart side tries an upgrade and the RPM side determines it's not > compatible. > > --Mark > > > $Updating cache... >> #################################################################################### >> [100%] >> >> Channels have 3 new packages: >> example-0.1-r4.0 at cortexa9hf_vfp_neon >> example-dbg-0.1-r4.0 at cortexa9hf_vfp_neon >> example-dev-0.1-r4.0 at cortexa9hf_vfp_neon >> >> Saving cache... >> >> $smart upgrade >> Loading cache... >> Updating cache... >> #################################################################################### >> [100%] >> >> Computing transaction... >> No interesting upgrades available. >> >> when I tried to force the installation of the package manually I've got >> the >> following error: >> >> $smart install example >> Loading cache... >> Updating cache... >> #################################################################################### >> [100%] >> >> Computing transaction... >> >> Installing packages (6): >> bash-4.2-r6 at cortexa9hf_vfp_neon >> libtinfo5-5.9-r15.1 at cortexa9hf_vfp_neon >> example-0.1-r4.0 at cortexa9hf_vfp_neon >> ncurses-terminfo-base-5.9-r15.1 at cortexa9hf_vfp_neon >> libc6-2.18-r0 at cortexa9hf_vfp_neon >> update-alternatives-cworth-1:0.1.8+svnr653-r13.0 at cortexa9hf_vfp_neon >> >> 1.9MB of package files are needed. 3.7MB will be used. >> >> Confirm changes? (Y/n): Y >> >> Fetching packages... >> -> >> http://192.168.113.70/utilite/rpm/cortexa9hf_vfp_neon/ >> example-0.1-r4.0.cortexa9hf_vfp_neon.rpm >> >> example-0.1-r4.0.cortexa9hf_vfp_neon.rpm >> ############################################################ >> ######################## >> [100%] >> >> Committing transaction... >> Preparing... >> ############################################################ >> ######################## >> [ 0%] >> error: package libc6-2.18-r0.cortexa9hf_vfp_neon is already installed >> error: package ncurses-terminfo-base-5.9-r15.1.cortexa9hf_vfp_neon is >> already >> installed >> error: package bash-4.2-r6.cortexa9hf_vfp_neon is already installed >> error: package libtinfo5-5.9-r15.1.cortexa9hf_vfp_neon is already >> installed >> >> >> How do I fix the upgrade command ? >> >> Thanks >> >> -- >> /Tarek/ >> > > -- *Tarek* -------------- next part -------------- An HTML attachment was scrubbed... URL: From frateraec at gmail.com Wed Aug 27 02:36:19 2014 From: frateraec at gmail.com (Frater AEC) Date: Wed, 27 Aug 2014 06:36:19 -0300 Subject: Smart 1.4.1 error in PCLOS 2014 Message-ID: Hi! Smart Package Manager 1.4.1 worked well in PCLOS. PCLOS is a APT-RPM rolling release distro. However, in some cases installation or upgrade it presents conflict error: # smart install task-pulseaudio Carregando o cache... Atualizando cache... ######################################## [100%] Calculando transa??o... Instalando pacotes (13): alsa-plugins-pulse-config-1.0.28-1pclos2014 at i586 libalsa-plugins-pulseaudio-1.0.28-1pclos2014 at i586 pulseaudio-4.0-6pclos2013 at i586 pulseaudio-client-config-4.0-6pclos2013 at i586 pulseaudio-esound-compat-4.0-6pclos2013 at i586 pulseaudio-module-bluetooth-4.0-6pclos2013 at i586 pulseaudio-module-equalizer-4.0-6pclos2013 at i586 pulseaudio-module-jack-4.0-6pclos2013 at i586 pulseaudio-module-lirc-4.0-6pclos2013 at i586 pulseaudio-module-x11-4.0-6pclos2013 at i586 pulseaudio-module-zeroconf-4.0-6pclos2013 at i586 pulseaudio-utils-4.0-6pclos2013 at i586 task-pulseaudio-2012.2.0-5pclos2014 at noarch Removendo pacotes (1): task-pulseaudio-remove-2012.12.0-4pclos2014 at noarch 4.3MB ser?o utilizados. Confirma mudan?as? (S/n): s Efetuando transa??o... Preparando... ######################################## [ 0%] erro: file /etc/esd.conf from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 erro: file /usr/bin/esd from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 It ends without completing the installation or upgrade. With "apt-get install" installs without displaying errors. Being pclos rolling release distro some packages only upgrade with the command "apt-get dist-upgrade". And all the packages that need to "apt-rpm dist-upgrade" to upgrade, are those with conflict error in smart. So I'm stuck in apt-get and I can not use only smart in pclos. This problem happens to anyone else? Any tips on how to resolve? I can to solve with configuration or is a bug that needs to be reported? Thanks! FraterLinux -------------- next part -------------- An HTML attachment was scrubbed... URL: From afb at algonet.se Sat Aug 30 04:50:02 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sat, 30 Aug 2014 13:50:02 +0200 Subject: Smart 1.4.1 error in PCLOS 2014 In-Reply-To: References: Message-ID: Frater AEC wrote: > Smart Package Manager 1.4.1 worked well in PCLOS. PCLOS is a APT-RPM rolling release distro. However, in some cases installation or upgrade it presents conflict error: ... > erro: file /etc/esd.conf from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 > erro: file /usr/bin/esd from install of pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from package esound-0.2.41-2pclos2011.i586 Smart doesn't handle the file conflicts, now that "pulseaudio-esound-compat" and "esound" aren't conflicting eachother. > It ends without completing the installation or upgrade. With "apt-get install" installs without displaying errors. Being pclos rolling release distro some packages only upgrade with the command "apt-get dist-upgrade". And all the packages that need to "apt-rpm dist-upgrade" to upgrade, are those with conflict error in smart. So I'm stuck in apt-get and I can not use only smart in pclos. AFAIK, apt-rpm hacks around the problem by using --replacefiles or something like that. Think it's called ReInstall "true" ? > This problem happens to anyone else? Any tips on how to resolve? I can to solve with configuration or is a bug that needs to be reported? Sounds like packaging issue, with the same file(s) belonging to two different packages at the same time (without a conflict). There is no option in smart, to have one package overwrite the files of another package. But rpm does have a --replacefiles. If you want PCLOS to support smart (not sure if they actually do?), you should probably have them change their packaging... --anders From afb at algonet.se Sat Aug 30 07:10:08 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sat, 30 Aug 2014 16:10:08 +0200 Subject: Merged upcoming to master, and launchpad to github Message-ID: I merged the "upcoming" branch to "master", and increased the version to 1.5. Let me know if there are any problems with it, or I'll tag it tomorrow or so. Also moved the code from Launchpad to GitHub: https://github.com/smartpm/smart There's a replacement for http://smartpm.org at http://smartpm.github.io/smart It seemed to be working with CentOS and Debian, but not supported with Fedora and not tested with Ubuntu. Haven't tried with the other distributions either. The Bazaar repository is deprecated, leaving the old code for 1.4 and earlier. Now Git should be used for all new development, see: https://help.github.com/ --anders From afb at algonet.se Sat Aug 30 07:20:32 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sat, 30 Aug 2014 16:20:32 +0200 Subject: Smart future mailstone, and version 1.5 release Message-ID: <4725AAD0-7B95-4FB4-87F2-0659B41D7DF7@algonet.se> I removed the mailstones in Launchpad, the main feature in 1.5 is the addition of "recommends" and a lot of various bugfixes. The addition of the interfaces for Mac OS X and Windows are gone, and the support for Python 3000 is now not an absolute requirement. I left the old code in the "py3k" branch, but it hasn't been updated with the latest changes and they are not compatible. i.e. it was converted with 2to3 and 2to3c, which means that it doesn't work with python any longer - but only with python3. Will let future Smart PM Team decide what the future will be... Most likely it needs both a new language (Go?), and a new database. The current language (Python 2.3 - 2.7) and database doesn't scale. But it should continue working just as before, in the meantime ? --anders From samorris at netspace.net.au Sat Aug 30 19:05:24 2014 From: samorris at netspace.net.au (Stephen Morris) Date: Sun, 31 Aug 2014 12:05:24 +1000 Subject: Merged upcoming to master, and launchpad to github In-Reply-To: References: Message-ID: <540282E4.9020501@netspace.net.au> Hi Anders, Having downloaded smart 1.5, with both python 2.7 and python 3.3 installed, how do I build smart for python 3.3 rather than its default of python 2.7? regards, Steve On 08/31/2014 12:10 AM, Anders F Bj?rklund wrote: > I merged the "upcoming" branch to "master", and increased the version to 1.5. > Let me know if there are any problems with it, or I'll tag it tomorrow or so. > > Also moved the code from Launchpad to GitHub: https://github.com/smartpm/smart > There's a replacement for http://smartpm.org at http://smartpm.github.io/smart > > It seemed to be working with CentOS and Debian, but not supported with Fedora > and not tested with Ubuntu. Haven't tried with the other distributions either. > > The Bazaar repository is deprecated, leaving the old code for 1.4 and earlier. > Now Git should be used for all new development, see: https://help.github.com/ > > --anders > > -------------- next part -------------- A non-text attachment was scrubbed... Name: samorris.vcf Type: text/x-vcard Size: 130 bytes Desc: not available URL: From afb at algonet.se Sun Aug 31 06:30:50 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 31 Aug 2014 15:30:50 +0200 Subject: Merged upcoming to master, and launchpad to github In-Reply-To: References: Message-ID: <715C3429-CAB2-42BD-8B02-6FEBCDE935DC@algonet.se> > I merged the "upcoming" branch to "master", and increased the version to 1.5. > Let me know if there are any problems with it, or I'll tag it tomorrow or so. Good thing I didn't tag that, as I pushed the wrong branch to master (duh). The current contents should include the portability fixes and URL updates... --anders From afb at algonet.se Sun Aug 31 06:40:14 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 31 Aug 2014 15:40:14 +0200 Subject: Merged upcoming to master, and launchpad to github In-Reply-To: <54027B91.8060707@netspace.net.au> References: <54027B91.8060707@netspace.net.au> Message-ID: Stephen Morris wrote: > I have downloads the tar file for smart 1.5 from http://smartpm.github.io/smart and run it, but I have an error saying that cdistance cannot be found. Can you refresh my memory on what needs to be done to rectify this? There is no 1.5 (yet), but I gather you downloaded "master". If you just run "make" (or python setup.py build), then Python will use the "build" directory... To make it possible to run from the source directory, one has to use "make ext" (i.e. --inplace) --inplace (-i) ignore build-lib and put compiled extensions into the source directory alongside your pure Python modules Supposedly this makes it easier for packaging or something ? Smart will *not* fall back to using the pure-python versions, this is an old feature or something. Forgot what the reason was, but one has to hack the source code to make it not try to load them... from cdistance import * --anders From afb at algonet.se Sun Aug 31 06:46:02 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 31 Aug 2014 15:46:02 +0200 Subject: Merged upcoming to master, and launchpad to github In-Reply-To: <540282E4.9020501@netspace.net.au> References: <540282E4.9020501@netspace.net.au> Message-ID: Stephen Morris wrote: > Having downloaded smart 1.5, with both python 2.7 and python 3.3 installed, how do I build smart for python 3.3 rather than its default of python 2.7? If you want to try the python3 version, you need to checkout the "py3k" branch: git checkout -tb py3k origin/py3k Then make (and setup.py, smart.py, etc) should default to "python3" automatically. There is no particularly good reason for doing so, however. python is the default. --anders From frateraec at gmail.com Sun Aug 31 09:44:55 2014 From: frateraec at gmail.com (Frater AEC) Date: Sun, 31 Aug 2014 13:44:55 -0300 Subject: Smart 1.4.1 error in PCLOS 2014 In-Reply-To: References: Message-ID: anders, I understand the questions raised. I would like to ask, what is the equivalent in the Smart for apt-rpm --dist-upgrade command? If not, could be requested as a future implementation to --dist-upgrade option to allow proper operation in rolling release distro like pclos? Thanks, FraterLinux 2014-08-30 8:50 GMT-03:00 Anders F Bj?rklund : > Frater AEC wrote: > > > Smart Package Manager 1.4.1 worked well in PCLOS. PCLOS is a APT-RPM > rolling release distro. However, in some cases installation or upgrade it > presents conflict error: > ... > > erro: file /etc/esd.conf from install of > pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from > package esound-0.2.41-2pclos2011.i586 > > erro: file /usr/bin/esd from install of > pulseaudio-esound-compat-4.0-6pclos2013.i586 conflicts with file from > package esound-0.2.41-2pclos2011.i586 > > Smart doesn't handle the file conflicts, now that > "pulseaudio-esound-compat" and "esound" aren't conflicting eachother. > > > It ends without completing the installation or upgrade. With "apt-get > install" installs without displaying errors. Being pclos rolling release > distro some packages only upgrade with the command "apt-get dist-upgrade". > And all the packages that need to "apt-rpm dist-upgrade" to upgrade, are > those with conflict error in smart. So I'm stuck in apt-get and I can not > use only smart in pclos. > > AFAIK, apt-rpm hacks around the problem by using --replacefiles or > something like that. Think it's called ReInstall "true" ? > > > This problem happens to anyone else? Any tips on how to resolve? I can > to solve with configuration or is a bug that needs to be reported? > > > Sounds like packaging issue, with the same file(s) belonging to two > different packages at the same time (without a conflict). > > There is no option in smart, to have one package overwrite the files of > another package. But rpm does have a --replacefiles. > > If you want PCLOS to support smart (not sure if they actually do?), you > should probably have them change their packaging... > > --anders > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From afb at algonet.se Sun Aug 31 11:56:11 2014 From: afb at algonet.se (=?iso-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 31 Aug 2014 20:56:11 +0200 Subject: Smart 1.4.1 error in PCLOS 2014 In-Reply-To: References: Message-ID: <5710CCCE-7DB1-47CA-AA62-2A9B4995C286@algonet.se> Frater AEC wrote: > I understand the questions raised. > > I would like to ask, what is the equivalent in the Smart for apt-rpm --dist-upgrade command? smart upgrade > If not, could be requested as a future implementation to --dist-upgrade option to allow proper operation in rolling release distro like pclos? I don't see what the conflicting files have to do with a rolling release... You mean that the packages are broken more often, because of the lack of release management ? Or that it needs to be more bug-compatible with apt-rpm, to support whatever it is PCLOS is doing ? --anders -------------- next part -------------- An HTML attachment was scrubbed... URL: From samorris at netspace.net.au Sun Aug 31 14:05:28 2014 From: samorris at netspace.net.au (Stephen Morris) Date: Mon, 01 Sep 2014 07:05:28 +1000 Subject: Merged upcoming to master, and launchpad to github In-Reply-To: References: <54027B91.8060707@netspace.net.au> Message-ID: <54038E18.50502@netspace.net.au> Hi Anders, Is there any documentation on what the directory structures should be when running ./setup.py build? I have run this which created the build directory, with subdirectories of lib.linux-x86_64-2.7 scripts-2.7 and temp.linux-x86_64-2.7. Lib.linux-x86_64-2.7 has the smart subdirectory, while scripts-2.7 has smart.py. If I cd into scripts-2.7 and run smart.py it appears to not be able to load its init import as indicated by the following traceback: ./smart.py Traceback (most recent call last): File "./smart.py", line 27, in from smart import init, initDistro, initPlugins, initPycurl, initPsyco File "/usr/local/downloads/Smart/smart15/build/scripts-2.7/smart.py", line 27, in from smart import init, initDistro, initPlugins, initPycurl, initPsyco ImportError: cannot import name init Am I not supplying enough parameters to setup.py for it to work or is this issue because I am trying to do this in Fedora 20? regards, Steve On 08/31/2014 11:40 PM, Anders F Bj?rklund wrote: > Stephen Morris wrote: > >> I have downloads the tar file for smart 1.5 from http://smartpm.github.io/smart and run it, but I have an error saying that cdistance cannot be found. Can you refresh my memory on what needs to be done to rectify this? > There is no 1.5 (yet), but I gather you downloaded "master". > > If you just run "make" (or python setup.py build), then Python will use the "build" directory... > To make it possible to run from the source directory, one has to use "make ext" (i.e. --inplace) > > --inplace (-i) ignore build-lib and put compiled extensions into the > source directory alongside your pure Python modules > > Supposedly this makes it easier for packaging or something ? > > Smart will *not* fall back to using the pure-python versions, this is an old feature or something. > Forgot what the reason was, but one has to hack the source code to make it not try to load them... > > from cdistance import * > > --anders > > -------------- next part -------------- A non-text attachment was scrubbed... Name: samorris.vcf Type: text/x-vcard Size: 130 bytes Desc: not available URL: From frateraec at gmail.com Sun Aug 31 15:06:19 2014 From: frateraec at gmail.com (Frater AEC) Date: Sun, 31 Aug 2014 19:06:19 -0300 Subject: Smart 1.4.1 error in PCLOS 2014 In-Reply-To: <5710CCCE-7DB1-47CA-AA62-2A9B4995C286@algonet.se> References: <5710CCCE-7DB1-47CA-AA62-2A9B4995C286@algonet.se> Message-ID: Anders wrote: > >I don't see what the conflicting files have to do with a rolling release... > >You mean that the packages are broken more often, because of the lack of release management ? > >Or that it needs to be more bug-compatible with apt-rpm, to support whatever it is PCLOS is doing ? The number of updated packages is different with the commands "apt-get --upgrade" and "apt-get --dist-upgrade". In practical terms, depending on the amount of updated packages, "smart --upgrade" does not solves all dependencies and "apt-get --dist-upgrade" solves. This problem should not occur. What is the difference in treatment rpm dependencies between "apt-get --dist-upgrade" and "smart --upgrade"? Thanks, FraterLinux 2014-08-31 15:56 GMT-03:00 Anders F Bj?rklund : > Frater AEC wrote: > > I understand the questions raised. > > I would like to ask, what is the equivalent in the Smart for apt-rpm > --dist-upgrade command? > > > smart upgrade > > If not, could be requested as a future implementation to --dist-upgrade option > to allow proper operation in rolling release distro like pclos? > > > I don't see what the conflicting files have to do with a rolling release... > > You mean that the packages are broken more often, because of the lack of > release management ? > > Or that it needs to be more bug-compatible with apt-rpm, to support > whatever it is PCLOS is doing ? > > --anders > > -------------- next part -------------- An HTML attachment was scrubbed... URL: