You are not logged in.
Are there any difference between chenxiaolong's appmenu-gtk, gtk2-ubuntu, gtk3-ubuntu, etc and the ones on AUR?
What's the best way to combine both of your efforts and obtain a FULLY working Unity?
Offline
first install unity from ayatana repo, then add all of chen's packages you want to have...
I don't know if it's the best way, but it's how I did it.
Last edited by oi_wtf (2012-12-12 19:05:18)
Laptop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-4771 @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB
Offline
Hello there...
So, as I said, unity@arch is dead now. Ayatana repo isn't functional, chenxialong's isn't fully independent anymore.
For those who want to install unity by one command there is no actual solutions, and many compatibility issues,
In this circumstances, I think that unity.xe-xe.org must be closed.
May be someone want to fork both githubs and make new repo, but not me.
Opensource at it's best, my ass.
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
Hello there...
So, as I said, unity@arch is dead now. Ayatana repo isn't functional, chenxialong's isn't fully independent anymore.
For those who want to install unity by one command there is no actual solutions, and many compatibility issues,
In this circumstances, I think that unity.xe-xe.org must be closed.May be someone want to fork both githubs and make new repo, but not me.
Opensource at it's best, my ass.
Why are you saying Ayatana repo isn't functional? I think the maintainer is waiting for some patches to be accepted by upstream to avoid future issues, which isn't dead but suspending for easier maintainance for future.
For me, the ayatana repo is functional enough together with a few packages from AUR.
Offline
Functional enough? Hehehe. But not fully functional.
For me, situation is clear: chenxiaolong did great work for months, then City-busz appeared again and "waiting for upstream". Chen just abandoned his work after this, and I bet that in couple of months City-busz again abandon ayatana repo. Because Unity never will be upstream project, it's Ubuntu project. So, we must use their patches or GTFO.
Last edited by pekmop1024 (2012-12-14 04:58:51)
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
Functional enough? Hehehe. But not fully functional.
For me, situation is clear: chenxiaolong did great work for months, then City-busz appeared again and "waiting for upstream". Chen just abandoned his work after this, and I bet that in couple of months City-busz again abandon ayatana repo. Because Unity never will be upstream project, it's Ubuntu project. So, we must use their patches or GTFO.
Sad to hear that. That's why I also suggest chenxiaolong to work directly on a fork of City-busz's git repo.
Anyway, thanks for the repo you've kindly provided. I think it really helped.
Offline
I'll continue to build repo if there will be good source, like chenxiaolong's github at good old times.
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
Guys, why don't upload packages from chens repo to AUR and build from there? At least there will be chance that someone will actually maintain or accasionally update bugs in packaging...
Now it doesn't look very good from the comments I see...
Offline
Packages are need to be built in right sequence, one by one, it's why chenxiaolong has placed them on github with readme containing that sequence.
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
not necessarily, not all packages are dependent on each other, it's just some that must be built before some others...
it was mainly because at the beginning most dependencies of the packages were not right, but thats resolved mostly now
so there's no need for an absolutely exact building sequence.
Most of the time I didn't build my packages in the right order, just paying attention to some relationships (e.g. building gtk before appmenu-gtk), and I never had regressions caused by that
Last edited by oi_wtf (2012-12-16 14:36:51)
Laptop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-4771 @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB
Offline
oi_wtf, it's mainly because you building packages not on clean system, but with installed unity
try to build it on clean chroot or VM, and you will see that there massive build dependencies problems with most of unity core packages.
also some packages needs as build deps another ubuntu-patched packages... it's a dep hell
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
Well, I built my packages at least 5 to 10 times in a clean environment... 2 times on my old "testing"-laptop, 1 time on my new laptop, and 2 to 3 times on my desktop, since I broke my system on it 2 times...
I didn't want to say it would be a good idea to put the packages into aur... the aur isn't suitable in this case, i think... at least not without a... well... some central place with instructions...
like: "if you want to have unity, you'll need to..."
I just wanted to say that city-busz and chen's remaining packages are working well together for me, no problems I know of...
Last edited by oi_wtf (2012-12-16 14:50:36)
Laptop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-4771 @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB
Offline
oi_wtf, agree with you about centralised manual and PKGBUILDs source. It may revive unity@arch project here..
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
If I may be so bold as to chime in here.
unity@arch will only die if you let it.
While chenxiaolong and City-busz are working hard to get this into community, it's a very simple task to fork chenxiaolong's previous work at say https://github.com/chenxiaolong/Unity-f … ddf507a8e5 and then it becomes an easy maintenance job just making sure it works with version bumps.
Unity-for-Arch and Unity-for-Arch-Extra could even be merged together and developed by the active hackers here.
But if you *are* going to do it, don't delay doing it, or the task becomes ever increasingly harder bringing it up to date.
Hacking on radical developmental Unity releases and how that ties in with the community repos might be an interesting prospect also, potentially putting the project in a permanent state of "waiting for upstream" and you lose the immediacy of enjoying the shiny packages *now*.
Keep on the good work and contributions that have brought it to this level, community still needs this band of pioneers otherwise new stuff may never make it in
Offline
Hey, I'm not sure about whre to post this.
I'm trying to run unity inside a VM (Oracle VirtualBox)
I did a fresh install of Arch, installed virtualbox-guest-additions as explained on the arch wiki.
I then installed unity from the repos (Not the AUR one - http://unity.xe-xe.org/$arch )
After starting unity here is what I get: http://imageup.fr/uploads/1355786992.png
Main problems related to that are the fact background won't show, i'm not sure about the side bar color.. and the top right menu allowing you to sign off and stuffs won't work (I don't have gdm or anything like that installed, that's maybe why)
Any advices, solutions to fix those problems ? x:
Thanks.
Last edited by EvilSakray (2012-12-17 23:32:49)
Offline
I created an overview page about the differences of my packages from Ubuntu, and about know bugs: https://github.com/City-busz/ayatana-repository/wiki
It's still work in progress, I'll send some more bugs and patches to upstream developers in the next days.@chenxiaolong: are you the original author of timedated patch for indicator-datetime? I would like to modify and forward it to the upstream developers.
Sorry for being away for so long. My finals are finally done, so I can start working on Unity again
In regards to the timedated patch, yes, I'm the author. Feel free to modify it any way you like and send it upstream.
Offline
I'm not against the movement towards unity with vanilla gnome as long as it's fully functional. So I would vote for no.
Just one suggestion for chenxiaolong's repo. if you decide to give up those packages, why not directly work on a fork of City-busz's packages?
It would make it easier to track, and also provides convenience for packagers like pekmop1024.
That's a good idea. I'll think about it.
Offline
I thought about this for a while and I'm deciding to bring back the Unity packages deleted after commit: 99b8b0b8e30aed09e02c50db80643eddf507a8e5
(I typed up a list of reasons, then pushed F5 by accident, so here's the short list):
1. I like to track the mostly-stable prereleases of packages with all the new features.
2. My server rebuilds the packages daily, like pekmop1024, and having packages from two sources is a pain.
3. I like to provide every available feature, which may require rebuilding all the packages.
4. And of course, to make all of Unity-for-Arch's users happy
There will be some changes though:
1. I will rename my packages to match City-Busz's and the AUR's package names.
2. I will try my best to ensure compatibility with City-Busz's packages and make sure that incompatible packages cannot coexist.
For example, my bamf package will provide 'bamf-webapps-support'. My packages that require the webapps support will depend on both "bamf" and "bamf-webapps-support", rather than just "bamf". This will make sure that City-Busz's bamf package cannot be installed (unless 'pacman -Udd' is used, of course). This is similar to the way openSUSE handles its packages.
3. I will use some of City-Busz's changes, like the moving of gsettings-desktop-schemas-ubuntu functionality to Compiz-ubuntu.
pekmop1024: Unity-for-Arch will be back, just like it was before, with Unity and all of its dependencies I have some issues to take care of right now (broken Lenovo battery), but the packages should start popping up in the next day or two.
Last edited by chenxiaolong (2012-12-18 07:01:58)
Offline
Addressing some technical issues (some from City-Busz's github wiki):
[bamf]
* No distro has anything similar to Debian's apt triggers (which basically runs something when a packages changes a file or directory). I will write a small daemon to monitor /usr/share/applications/ and update /usr/share/applications/bamf.index when necessary.
* I will merge City-Busz's patch from here: https://code.launchpad.net/%7Eballogy/b … rge/137762
[indicator-messages]
* I will create a subpackage that contains modified desktop files necessary for the messaging indicator to work properly.
[indicator-datetime]
* I will finish writing my patch that removes the broken timezone changing functionality from the control center panel.
* I will (at least try to) make the GNOME timezone settings panel show up in indicator-datetime's settings panel.
[unity]
* I write a patch to stop the launcher icons from disappearing when packages are updated. I'm not entirely sure on how this is going to be implemented yet.
[gnome-control-center-unity]
* This will be packaged. This replaces the big ugly background settings panel in GNOME 3.6 with the patched Unity one from GNOME 3.4.
Fixed in commit: 52c39b36c048aa39ccce853b07413404c14d7818
Are there any other things I forgot that I need to fix?
Last edited by chenxiaolong (2012-12-20 06:58:20)
Offline
pekmop1024: Unity-for-Arch will be back, just like it was before, with Unity and all of its dependencies I have some issues to take care of right now (broken Lenovo battery), but the packages should start popping up in the next day or two.
Thanks for your great work!
btw, this Lenovo unit seems to be damned, may be you need to change it for Dell Latitude
Last edited by pekmop1024 (2012-12-18 09:42:26)
ArchLinux x86_64 (passively cooled): Xeon E3 1230v2 - 32GB - GTX1050Ti KalmX - Samsung 850 EVO 1TB - 3x2TB Seagate - Creative X-Fi Titanium - Cheiftec GPS-500C
ArchLinux x86_64 (FrankenPad T420): i7 2720QM - 16GB - NVS 4200M - Samsung 840 EVO 1TB - FullHD IPS mod - Intel 7260AC - Sierra Wireless MC7304
Offline
Happy (late) holidays to everyone! I'll continue working on unity after New Year
Offline
All the packages are updated to the 13.04 versions The versions for GNOME packages match up with the Arch Linux versions and so far, Unity is far more stable than the 12.10 versions (at least on my computer).
Offline
glew 1.8 patch is still in the source array of the nux pkgbuild, thus makepkg fails with
==> ERROR: 0003_Glew_1.8.0_fix.patch was not found in the build directory and is not a URL.
and in some indicators there was still "libido3" as dependency...
Last edited by oi_wtf (2013-01-08 13:15:11)
Laptop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-3630QM @ 2.40GHz, 8 GiB RAM, NViDiA GeForce GT 650M w/ 2 GiB
Desktop: Arch Linux (x86_64) and Win10 (x86_64); Intel Core i7-4771 @ 3.50GHz, 32 GiB RAM, AMD Radeon RX 480 w/ 8 GiB
Offline
glew 1.8 patch is still in the source array of the nux pkgbuild, thus makepkg fails with
==> ERROR: 0003_Glew_1.8.0_fix.patch was not found in the build directory and is not a URL.
and in some indicators there was still "libido3" as dependency...
Thanks! Fixed
Commits:
b5dd5b0e36df99e66a359dd5b780ff8264b59213
8a5dc1afe6c78dece7e2f8e1376f8ed8a4e2a0f8
f24f1e6b7efeab9347bda11808c57caa2e2f6f84
Offline
2013-01-09 release note (lots of awesome stuff )
Unity-for-Arch
* Unity now includes /usr/share/glib-2.0/schemas/10_unity.gschema.override, which sets the window dragging key back to Alt since Super- + Drag is completely broken in Unity.
* Updated compiz to 0.9.9.daily12.12.05.0ubuntu2, which has many performance improvements and enables unredirected windows by default (upstream choice).
Unity-for-Arch-Extra
* ubuntu-themes was added. This is Ubuntu's new package that replaces light-themes and ubuntu-mono.
** I've added a GSettings/dconf defaults mechanism to LightDM. Files like the following can be placed in /etc/guest-session/gsettings/:
[org.blah.some.path]
key-1="value1"
key-2=0.5
key-3=['element1','element2']
Those files will set the default dconf settings for the guest account. Files should be named like 10-something.defaults. The higher the number, the higher the priority.
**The Unity LightDM greeter now provides /etc/guest-session/gsettings/10-unity.defaults. This will make the guest session look all nice. It uses some of the Ubuntu defaults (Ambiance theme, Ubuntu wallpaper, etc) instead of the horrible mess that the regular defaults make
**LightDM now properly uses the systemd PAM module so that the LightDM environment is properly set up. This allows the NetworkManager applet to show up on the login screen, which allows remote logins to work
* The FreeRDP PAM module now has a working configuration file.
*The remote login configuration session (lightdm-remote-session-uccsconfigure) uses Chromium for now, since something is causing Firefox to hang in that session.
I find the guest account and remote login features so cool, but maybe that's because I've been reading policykit, pam, and systemd man pages for hours
Last edited by chenxiaolong (2013-01-09 18:01:16)
Offline