Atolboo,

While I am making package I had the below errors:

kizilyildiz virtualbox-4.1.8-x86_64.pisi # pisi bi pspec.xml
Building source package: virtualbox-4.1.8-x86_64.pisi
DEBUG: ComponentDB initialized in 0.00336194038391.
DEBUG: RepoDB initialized in 0.000144958496094.
DEBUG: InstallDB initialized in 0.00378704071045.
Cannot find component.xml in upper directory, Source is now part of unknown component
VirtualBox-4.1.8.tar.bz2 [cached]
Unpacking archive(s)...
 unpacked (/var/pisi/virtualbox-4.1.8-x86_64.pisi-4.1.8-1/work)
Setting up source...
*** 0 error(s), 1 warning(s)
Program terminated.
ERROR: WorkDir (/var/pisi/virtualbox-4.1.8-x86_64.pisi-4.1.8-1/work/VirtualBox-4) does not exist

Please use 'pisi help' for general help.
kizilyildiz virtualbox-4.1.8-x86_64.pisi #

But actually that directory is existing.
kizilyildiz work # pwd
/var/pisi/virtualbox-4.1.8-x86_64.pisi-4.1.8-1/work

Hello,

Is it possible to have virtualbox latest edition as pisi?

There a lots of bug fixes from 4.1.2 to 4.1.8
his is a maintenance release. The following items were fixed and/or added:

    VMM: fixed VERR_REM_VIRTUAL_CPU_ERROR under rare conditions after the guest has been reset (bug #5164 and others)
    VMM: fixed host freezes with 64-bit guests on 32-bit Linux hosts (bug #10528)
    VRDP: added a workaround for rdesktop clients not properly updating the screen size when minimized
    AHCI: fixed a rare bug which can cause a guest memory corruption after the guest storage controler has been reset
    NAT: another attempt to fix crashes under rare conditions (Windows hosts only; bug #10513)
    Mac OS X hosts: addressed issues running Leopard / Snow Leopard (bug #10631)
    Linux hosts / Bridged Networking: fixed the problem with device driver unloading on kernels 3.2.18 and newer due to an invalid reference counter (bug #10624)
    Linux hosts / guests: Linux 3.5-rc1 fixes
    Linux Additions: the guest content was sometimes not properly updated (bug #9887)
    Solaris Additions: installer fix for X.org Server 1.11 and 1.12

Hi Lisa,

In my office laptop, I have Pardus and Virtual Box. Virtual box is necessary for me due to outlook (since we do not have pop access) and IE and office tools.

The rest use Pardus. nspluginwarpper is used for plugins not supported in 64 bit linux. I am extracting Citrix 32 bit plugins to 64 bit by nspluginwaper.

I strongly suggest you VirtualBox instead of dual booting. It is really useful.

Best Regards,

Murat

Duran Duran,

http://www.youtube.com/watch?v=ICnlyNUt_0o

Hi Lisa,

I am using Pardus 2011.2 and on top of it virtualbox. My office tools works under windows. Virtualbox solves all problems. just install virtualbox and on top of windows guest additions.

Thats all

Murat

They do not have exchange support.

Hello Zvacet,

In one point you are right but on the other hand if your software is not good and strong enough for end user, you are not able to be free. Think that most of the people still dependent on MS office. For operating system part I have no doubt about linux. But for me the weakest Part is office and e-mail client side.

Currently I am working for international Telecom company and I need to use windows on top of ANKA GNU Linux. Why? Because there is no outlook for Linux. Do not tell me Evolution it is not good. I need calendar, I need groupware etc. But the rest I am using linux.

To be free you need to be strong. Really!.

I understand your concerns but we need to see also behind of mirror.

Many thanks for reading and listening me.

Forever Linux.

This is the best I think. Much professional.

me too

Hello Richard,

worldforum is not reachable from this ip block

212.252.168.236

Just to inform you.

Best Regards,

Murat

@dschzz

The problem is without Pisi and Comar why do we need Pardus? There is Debian,Ubuntu Mint etc.

Why we are still discussing this Debian I really do not understand.

We will have Pardus (pisi,comar,yali,tasma,kaptan) or creature?

I do not want creature. If Pardus will end let it end like this. But I (personally) do not want to see useless .deb or .rpm package based distro.

If these distrubitons are really good then we would not discuss Pardus here.

Please lets focus to pisi and Pardus.

Linux does not mean the richness of repository as I said. Stability, ease of use, configuration. Some how we are still living with Pardus despite its repo is not as rich as debian.

Best Regards,

Many thanks all of you friends. I hope I could explanin my feelings without breaking anything.

Hello,

Here is the Pisi link. Why they have choosen.

http://www.brighthub.com/computing/linux/articles/52774.aspx

and

from
http://tr.pardus-wiki.org/Pisi_tasar%C4%B1m%C4%B1#Neden_P.C4.B0S.C4.B0.3F

Neden PİSİ?

Hali hazırda varolan ve geniş bir kullanım oranına sahip paket yöneticileri (RPM, DPKG ve Portage) yukarda saydığımız gereksinimlerin kimilerini bizim olması gerektiğini düşündüğümüz basitlikte yerine getirememekte, kimilerini de hiç vaad etmemektedirler. Bu paket yöneticilerinin geliştirilmesi ve istenen noktaya getirilmeye çalışılması yeni ve ayakları yere daha sağlam basan bir paket yöneticisini yeniden yazmaktan daha kolay değildir.

Daha önemlisi, varolan paket yöneticilerinin paket formatlarında görevleri ve bilgileri birbirinden düzgün bir biçimde ayrılmadıkları görülmektedir. Bu araçlar basit olarak hazırlanmış ve zaman içinde ortaya çıkan ihtiyaçları karşılamak için sürekli yeni özellikler eklenerek bugünkü hallerine gelmişlerdir. Bunun getirdiği karmaşıklığı temizlemek için aşağıdaki iki ilkeyi temel alan yeni bir paket yöneticisinin yazılmasına karar verilmiştir:

    Kurulum ve yapılandırma birbirinden ayrı iki görevdir. Kurulum, yalnızca programların kurulumu, güncellenmesi ve kaldırılması esnasında iş görürken, yapılandırma hem kurulumda hem de çalışan sistemde söz konusudur. Bu ayrı görevleri sorumluluk sınırları belirlenmiş ayrı araçların yerine getirmesi uygundur. Uludağ projesi için yapılandırma işlerini yürütecek araç ÇOMAR'dır. PİSİ bu görevleri ÇOMAR'a devredecektir.
    Paket meta bilgileri ile paketin derlenme ve kurulumunu yöneten betikler iç içe geçmemelidir. Varolan paket yöneticilerinde paket tanımlama dosyaları kod ile bilginin birbirine karıştığı, araçlarla işlemesi, içinden bilgi çıkarılması zor, net ve kesin tanımlanmamış biçimlerdedir.

@jasperodus
The problem is not only Debian, but also Tübitak. They want to close the Pardus project but not by themselves. They are trying people to leave by their own decision and close the shop.

For me, the spirit of Pardus is ,Pisi,Comar,Tasma,Kaptan,Yalı, but not the apt or aptitude.

This is something like you love a person but he/she is dead but soul lives somebody Else's body.

Where is the person I love? Body dead soul exists in somebody Else's body. 

For me like that but everybody has his/her own feelings.

There was a song "I will never dedicate my love to somebody else's lover"

Thank you all.

Forget them. It was obvious, now clear.

Pardus, Anka, what ever you name it , will/should continue independently from Tübitak. There are already too many Debian based distributions. Why next one will be Pardus?

It is meaningless. What makes Linux is not the richness of package repositories. It is freedom, ease of use, ease of configuration, functionality. Pardus has all of these.

I think /hope good days are coming.

If it is really will be Debian based, I am really disappointed.

Can we call this creature Pardus?

Shame on you Tübitak.