I would like to look at how the .deb's have been constructed in the testing repo - I'm particularly interested in the new budgie-desktop deb package.
Is there a web URL where I can browse to to grab unpack the .debian.tar.xz or similar in a similar way that I can do so on Debian Sid or Ubuntu ?
thanks in advance
All sparky tools source code is available in our account at SourceForge git repos.
I don't have the Budgie source tar ball, the source code is available at the Solus github repos.
Anyway, if you'd like to check how the deb is built, simply extract the deb via a archive manager.
many thanks for the reply.
Thanks. I'm particularly interested in how sparky has constructed the debian/control(.in) and the debian/rules files together with any patches that may be applied.
Any thoughts where I can find that information?
I had a quick look at the contents of the .deb - I can see all the files that were built - I'm particularly interested in the construction of the package and how you coped with building for multi-arch.
If the debian/control and debian/rules are on source-forge somewhere please can you point me where?
Many thanks in advance
My ebook reader (kobo) is updating (done finally), but one great source for all things debian with links to elsewhere is
https://debian-handbook.info/
15.2 building your first package.
The source of course code used for budgie is present at with initial instructions for compiling ( but not creating the .deb) at
https://wiki.solus-project.com/Budgie_on_other_Operating_Systems
and more info at the Debian web site.
After reading 15.2 above there is on OFTC irc
#debian-mentor (which I have no experience with)
peace out
thanks,
I've looked at all of that - very interesting.
I'm specifically interested in sparkylinux because the project has a series of interesting packages but I cannot see how those packages were created and what modifications (if any) has been made.
I've been looking at the new budgie-desktop version of sparky - normally in debian and debian derived distros you should just enable/add a deb-src repo and grab the source and the debian package via a:
apt-get source package-name
There doesnt seem to be a source repo for budgie-desktop - I get 404 errors - thus I'm wondering where is it? I've picked on in my opening comment wanting to look at the budgie-desktop package thus
apt-get source budgie-desktop
All linux distros must have their packages and code obtainable if requested to meet GPL reasons - I'm sure sparky-budgie has this info somewhere - just where?
Quotenormally in debian and debian derived distros you should just enable/add a deb-src repo and grab the source
That's right, but I don't have time to do that.
The source code is in the git repos so can be checked as you wish.
A few 3th party apps, such as: e20, budgie and tint2 has been compiled without changes (no patches), means they are vanilla, as the developers created them. I only grab the source (so you can do it too), compile and build debs. I don't provide source packages in sparky repos so you can't find them.
Anyway I can tar the source code and make *orig.tar.gz packages next time if you'd like.
ok - understand. Thanks for the offer.
If you can post somewhere your budgie-desktop DEBIAN folder within the budgie package (rule, control, .install files etc) I would much appreciate it.
I've been fiddling myself creating a .deb for budgie-desktop but am having issues and I just need to compare with something that you have obviously got working.
Once I've got my version working I'll post you my version if you wish to incorporate it ... or just compare for info.
many thanks.
FOSS of demand is not only uncomfortable for now developers. :(
It will stop the evolution of Sparky.
I know the distribution was stopped several published by such leverage in Japan.
I have been plagued really that this has decreased by the distribution user of Japan! :'(
Please you are waiting for the time. It will visit either...
balloon,
sorry - I don't really understand what you are saying.
I'm asking for the packaging. This is a GPL right and all GPL projects must supply when requested - and @pavroo has said that he/she will.
I'm trying to help here - I've looked at the contents of the .deb and I'm pretty sure the .deb contains the development libraries as well as the end-user libraries. This is contrary to the Solus projects wishes. I've corrected this in my packaging and want to share this with the sparky community.
I'm at the final step trying to understand why sparky's much larger package is working whilst my split packaging is not.
You can grab the debs from repos:
http://sparkylinux.org/repo/pool/main/b/budgie-desktop/
I will upload the tar balls soon, No time in this moment, sorry.
Hi @Pavroo
did you upload the debian.tar.gz and budgie-desktop-10.2.1.orig.tar.gz for budgie-desktop somewhere?
I didnt spot this in that link - I've checked your git repo here also
- http://sourceforge.net/p/sparkylinux/code/ci/master/tree/
Hi foss
No. I haven't.
I said that I will do it when I'll be compiling the next version of budgie.
I downloaded v.10.2.2 already so I will try to buid it tomorrow (depends of my time).
thanks
the key difference between 1.2.1 and 1.2.2 is the policy-key additional requirement
So for your build-depends you'll need to add libpolkit-agent-1-dev libpolkit-gobject-1-dev
You'll probably already have the policykey dependency since you bringing in gnome-session
if stretch complains (in configure.ac) about the policykey version must be "110" - then its safe to quilted patch that to "105"
There is 'budgie-desktop' 10.2.2 ready in sparky repos now.
http://sparkylinux.org/budgie-desktop-10-2-2/
The tar balls and source package can be found at sourceforge repos now.
I work on adding source packages to the sparky repos, but not ready yet.
Hi,
am I looking at the wrong location?
http://sourceforge.net/projects/sparkylinux/files/files/apps-src/
I couldnt see the debian tar ball containing the debian/control, debian/rules, debian/patches etc etc
thanks
The path is correct.
Simply download 'budgie-desktop_version*_arch*.tar.gz' package, extract the archive to find what you looking for.
I'm looking at this file
- http://sourceforge.net/projects/sparkylinux/files/files/apps-src/budgie-desktop_10.2.2_amd64.tar.gz
In the DEBIAN folder there are only three files - one is a partial control file, a md5sum and something else.
Where is the rules file and the full control file (that include the build-depends) - I need at least those two files to practise a rebuild.
All the packages are done and placed in the repos now.
Try it out.
Wonderful @Pavroo - I've enabled deb-src in /etc/apt/sources.list.d/sparky.list and I can now do
apt-get source budgie-desktop
I'm trying to rebuild the source and package as follows
mv budgie-desktop_10.2.2-1.tar.gz budgie-desktop_10.2.2.orig.tar.gz
tar -xvf budgie-desktop_10.2.2.orig.tar.gz
cd budgie-desktop-10.2.2
debuild -us -uc
the resultant amd64.deb is smaller that the sparky repo amd64.deb - more importantly after dpkg -i *.deb budgie-desktop just black screens.
Are you building in some other way?
Almost the same, just my last command is:
dpkg-buildpackage -us -uc
Missing dependencies, wait for a next version.
There is an upgraded version of budgie 10.2.2-1-1 in the repos now.
Try again.
ok - ta.
when compiling it is complaining about gir1.2-gee-1.0 not being available - its not in debian testing. So I changed this in the control file for gir1.2-gee-0.8 and rebuilt and installed.
All seems to be OK ... for debian testing.
I've taken the same source and package and rebuilt in ubuntu 16.04 xenial. I'm getting a black-screen on logon. Dont really have any idea why.
What makes it strange - I can take the binary .deb built in sparky debian and install in ubuntu 16.04 and all works ok.
ho hum. Thanks again for packaging this.
gir1.2-gee-0.8 - my mistake - have to change it again.
But the question is: the default budgie installation starts with no wallpaper loaded - it is black, but is there a panel on the top of a screen?
all is well if I compile under debian testing (sparky) and reinstall the built .deb.
If I take the source and build under ubuntu 16.04 - which in theory is the same as debian testing - I just get a black screen - no panel - nothing.
in journalctl I can see the following errors which doesnt mean much to me.
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-wm:1382): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-wm:1382): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-panel:1391): GLib-GObject-WARNING **: cannot register existing type 'BudgieDesktopManager'
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-panel:1391): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-panel:1391): GLib-GObject-CRITICAL **: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-panel:1391): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Jan 2 22:48:07 dad-VirtualBox gnome-session[1092]: (budgie-panel:1391): GLib-GObject-CRITICAL **: g_object_new_valist: object class 'BudgieRaven' has no property named 'manager'
Uninstall your deb built on ubuntu.
Grab a fresh source from sparky repos, untar it, get inside it and run the configuration process manually:
./configure
Then check the output - it will tell you what's missing.
yep - that's the strange thing. I can ./configure and sudo make install the source and then login just fine - panel and everything works just fine.
Its just building a .deb and installing that that fails.
Is the building tool in 100% the same on ubuntu and debian?
I don't know it well, but doesn't it make any change in the deb?
I honestly thought they were identical. Ubuntu takes 99% of all its packages straight from Debian Unstable. The build robot just changes the "unstable" repo name in the changelog (and maybe the section name in the control file) and replaces it with either "main" or "universe" since these are the repo names. Other than that, the package is the same.
There is some very weird obscure ubuntu build issue which I have no idea how to get around :(
Just one more thing - did you build it on 32 or 64 bit systems?
64bit
There was one more issue about the architecture in the source package.
I uploaded v. 10.2.2-3-1.
Not sure it will help you, but you can try.
Solus Project has published a how to build Debian for the Wiki:
https://wiki.solus-project.com/Budgie_on_other_Operating_Systems
You can make this in tips for a successful build.
@pavroo
as promised - https://launchpad.net/~fossfreedom/+archive/ubuntu/budgie-desktop/+files/budgie-desktop_10.2.3-1ubuntu3.debian.tar.xz
this is my reworking of the build - you'll notice the split of library files and the production of debug files as well.
Whilst sparky has a much simpler rules - for Ubuntu it is more complicated - I dont know why autotools-dev just doesnt create stuff that can be installed on ubuntu 15.10 and 16.04
I still can't figure out how to produce both a 32bit and 64bit at the same time (when having an architecture of "any" or "i386 amd64", on launchpad the i386 always fails) - so for the moment 64bit only for Ubuntu.
Anyway - take anything you want from my package for sparky users.
QuoteI still can't figure out how to produce both a 32bit and 64bit at the same time
I don't do that in the same time.
Did you try to specify the arch as an option to dpkg-build?
If I just specify either i386 OR amd64 in the control file then launchpad builds just fine.
If I specify "any" or "i386 OR amd64" - for some reason the amd64 build works fine - it runs through the debian/rules build and binary stuff fine. However the i386 build first runs through debian/rules build and then runs debian/rules build-arch.
At that point it does some very strange dh-auto-configure stuff totally ignoring the ./configure build thing that I explicitly put in.
I've got an explicit override for dh-auto-configure but the building bot totally ignores this.
You have the flexibility to-do individual builds for sparky. On launchpad & debian you have to build all architectures at the same time.
edit - solved!
both 32bit and 64bit builds at the same time can be built!
- https://launchpad.net/~fossfreedom/+archive/ubuntu/budgie-desktop/+files/budgie-desktop_10.2.3-1ubuntu6.debian.tar.xz
That's great!
I add it here, knowing that the number of months has passed.
I recently learned who "foss" is. I would have put a different comment if I knew it.
"budgie-remix" born on this post was released,
that it will become the official Ubuntu flavor "Ubuntu Budgie" a few hours ago:
https://budgie-remix.org/2016/11/08/its-official/
If pavroo did not cooperate, it would not have been born.
That is a wonderful FLOSS contribution!
I appreciate the support to pavroo. Thanks pavroo! ;D