[arch-dev-public] KDE: Call for a Co-Maintainer and an unstable repo
Hi, I have some KDE related points I want to discuss here: 1) I need someone who helps me to maintain KDE. It develops quite fast and 4.2 introduces some new features, moredependencies and we need to add/update some packages in [extra]. I know that you allready have more than enough to do. So if ther is noone among us we might ask if there is some TU willing to help. With some additional help the following issues can be fixed: 2) KDE-4.2 will be released in a few weeks. So it makes sense to start packaing beta and rc snapshots. What do you think about a kde-unstable repo? I think it could be live in <package>/repos/kde-unstable and db -update should be able to handle this. The size of this repo would be about 350MB for each architecture. 3) The package dependencies of KDE are goning to be a mess. If you install the kde group you will find nearly the whole [extra] repo on your harddrive. Some of these deps are only on package level and can be fixed. E.g. kde depends on gnome due to some "strange" deps of ghostscript and gstreamer for example. Having a look at 4.2 this situation is getting worse. KDE is more or less modular, but they put a lot of apps in one package like kdegraphics. The only sane way to solve this issue is to split some packages. Optdepends does not help here because some features are enabled at runtime if certain files exist. Support for splitting packages in makepkg/devtools woulbd be more than helpfull if not needed. Who wants to install java, php, ruby, perl etc. just because some apps in kdebase makes use of the python -bindings which iare included in the kdebindings package? Summing things up, this is a call for increasing man power. I need somone to help with packaging KDE (and its dependencies) and somone to implement support for splitting packages in makepkg (and don't forget about the devtools and db- scripts here) Greetings, Pierre -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
Pierre Schmitz wrote:
Summing things up, this is a call for increasing man power. I need somone to help with packaging KDE (and its dependencies) and somone to implement support for splitting packages in makepkg (and don't forget about the devtools and db- scripts here)
FYI, I have been spending time getting package splitting to work properly in makepkg. It is getting there but will require me to have a couple of weekends free at same stage to finish it off. Allan
On Sun, Nov 30, 2008 at 4:24 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Hi,
I have some KDE related points I want to discuss here:
1) I need someone who helps me to maintain KDE. It develops quite fast and 4.2 introduces some new features, moredependencies and we need to add/update some packages in [extra].
I know that you allready have more than enough to do. So if ther is noone among us we might ask if there is some TU willing to help.
With some additional help the following issues can be fixed:
2) KDE-4.2 will be released in a few weeks. So it makes sense to start packaing beta and rc snapshots. What do you think about a kde-unstable repo? I think it could be live in <package>/repos/kde-unstable and db -update should be able to handle this. The size of this repo would be about 350MB for each architecture.
3) The package dependencies of KDE are goning to be a mess. If you install the kde group you will find nearly the whole [extra] repo on your harddrive. Some of these deps are only on package level and can be fixed. E.g. kde depends on gnome due to some "strange" deps of ghostscript and gstreamer for example.
Having a look at 4.2 this situation is getting worse. KDE is more or less modular, but they put a lot of apps in one package like kdegraphics. The only sane way to solve this issue is to split some packages. Optdepends does not help here because some features are enabled at runtime if certain files exist. Support for splitting packages in makepkg/devtools woulbd be more than helpfull if not needed. Who wants to install java, php, ruby, perl etc. just because some apps in kdebase makes use of the python -bindings which iare included in the kdebindings package?
Summing things up, this is a call for increasing man power. I need somone to help with packaging KDE (and its dependencies) and somone to implement support for splitting packages in makepkg (and don't forget about the devtools and db- scripts here)
Go ahead and start with the kde-unstable repo, I created the dirs on gerolde so you should be able to do it at any time. Regarding a KDE maintainer - I would *love* to have people brought on board for specific purposes like this. Feel free to propose it to the TUs. We can pull someone on board for KDE maintenance. Just make sure they're aware that the job is KDE, anything else they maintain should be secondary
Am Montag 01 Dezember 2008 23:34:55 schrieb Aaron Griffin:
Go ahead and start with the kde-unstable repo, I created the dirs on gerolde so you should be able to do it at any time.
Thanks. Just a sidenote: db-update does not work if there is no initial db file. I think it just creates an empty file and repo-add fails later. I used repo-add manually for now. So this does not realy to be fixed soon. :-) I got the following output: pierre@gerolde ~ % /arch/db-update kde-unstable x86_64 Updating DB for kde-unstable x86_64 ==> Copying DB file from 'kde-unstable'... ==> Processing new/updated packages for repository 'kde-unstable'... Checked out revision 20293. Validating package arch (x86_64) akonadi Checking SVN for akonadi Validating package arch (x86_64) phonon Checking SVN for phonon ==> ERROR: Repository file '/srv/tmp/db-update.kde-unstable- x86_64.1031/build/kde-unstable.db.tar.gz' is not a proper pacman database. Copying new files to '/srv/ftp//kde-unstable/os/x86_64/' Cleaning staging dir 1 pierre@gerolde ~ % file /srv/ftp/kde-unstable/os/x86_64/kde- unstable.db.tar.gz /srv/ftp/kde-unstable/os/x86_64/kde-unstable.db.tar.gz: empty -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
On Mon, Dec 1, 2008 at 6:44 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Montag 01 Dezember 2008 23:34:55 schrieb Aaron Griffin:
Go ahead and start with the kde-unstable repo, I created the dirs on gerolde so you should be able to do it at any time.
Thanks. Just a sidenote: db-update does not work if there is no initial db file. I think it just creates an empty file and repo-add fails later.
I used repo-add manually for now. So this does not realy to be fixed soon. :-)
I got the following output:
pierre@gerolde ~ % /arch/db-update kde-unstable x86_64 Updating DB for kde-unstable x86_64 ==> Copying DB file from 'kde-unstable'... ==> Processing new/updated packages for repository 'kde-unstable'... Checked out revision 20293. Validating package arch (x86_64) akonadi Checking SVN for akonadi Validating package arch (x86_64) phonon Checking SVN for phonon ==> ERROR: Repository file '/srv/tmp/db-update.kde-unstable- x86_64.1031/build/kde-unstable.db.tar.gz' is not a proper pacman database. Copying new files to '/srv/ftp//kde-unstable/os/x86_64/' Cleaning staging dir 1 pierre@gerolde ~ % file /srv/ftp/kde-unstable/os/x86_64/kde- unstable.db.tar.gz /srv/ftp/kde-unstable/os/x86_64/kde-unstable.db.tar.gz: empty
Hmm, sounds like a repo-add bug. It should create the file if it doesn't exist. I would assume a hack would be: touch kde-unstable.tar gzip kde-unstable.tar /me shrugs
Aaron Griffin wrote:
On Mon, Dec 1, 2008 at 6:44 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Montag 01 Dezember 2008 23:34:55 schrieb Aaron Griffin:
Go ahead and start with the kde-unstable repo, I created the dirs on gerolde so you should be able to do it at any time.
Thanks. Just a sidenote: db-update does not work if there is no initial db file. I think it just creates an empty file and repo-add fails later.
I used repo-add manually for now. So this does not realy to be fixed soon. :-)
I got the following output:
pierre@gerolde ~ % /arch/db-update kde-unstable x86_64 Updating DB for kde-unstable x86_64 ==> Copying DB file from 'kde-unstable'... ==> Processing new/updated packages for repository 'kde-unstable'... Checked out revision 20293. Validating package arch (x86_64) akonadi Checking SVN for akonadi Validating package arch (x86_64) phonon Checking SVN for phonon ==> ERROR: Repository file '/srv/tmp/db-update.kde-unstable- x86_64.1031/build/kde-unstable.db.tar.gz' is not a proper pacman database. Copying new files to '/srv/ftp//kde-unstable/os/x86_64/' Cleaning staging dir 1 pierre@gerolde ~ % file /srv/ftp/kde-unstable/os/x86_64/kde- unstable.db.tar.gz /srv/ftp/kde-unstable/os/x86_64/kde-unstable.db.tar.gz: empty
Hmm, sounds like a repo-add bug. It should create the file if it doesn't exist. I would assume a hack would be: touch kde-unstable.tar gzip kde-unstable.tar
/me shrugs
It looks to me as if repo-add is encountering a file that is not a database. I have use repo-add a lot of times without first touching a database so I do not think that is the problem. Allan
Am Dienstag 02 Dezember 2008 01:48:45 schrieb Aaron Griffin:
Hmm, sounds like a repo-add bug.
I don't think so. repo-add works fine if there is no db file. But something (db-update) created an empty db file before (0 byte) and that's what repo-add does not like. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
On Mon, Dec 1, 2008 at 6:55 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Dienstag 02 Dezember 2008 01:48:45 schrieb Aaron Griffin:
Hmm, sounds like a repo-add bug.
I don't think so. repo-add works fine if there is no db file. But something (db-update) created an empty db file before (0 byte) and that's what repo-add does not like.
Yeah, stray touch. There was another in db-move. I fixed and pushed to projects.archlinux.org
On Mon, Dec 1, 2008 at 7:03 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Mon, Dec 1, 2008 at 6:55 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Dienstag 02 Dezember 2008 01:48:45 schrieb Aaron Griffin:
Hmm, sounds like a repo-add bug.
I don't think so. repo-add works fine if there is no db file. But something (db-update) created an empty db file before (0 byte) and that's what repo-add does not like.
Yeah, stray touch. There was another in db-move. I fixed and pushed to projects.archlinux.org
How dare you blame me and my team's perfect software! -Dan
On Mon, Dec 1, 2008 at 7:21 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Mon, Dec 1, 2008 at 7:03 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Mon, Dec 1, 2008 at 6:55 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Dienstag 02 Dezember 2008 01:48:45 schrieb Aaron Griffin:
Hmm, sounds like a repo-add bug.
I don't think so. repo-add works fine if there is no db file. But something (db-update) created an empty db file before (0 byte) and that's what repo-add does not like.
Yeah, stray touch. There was another in db-move. I fixed and pushed to projects.archlinux.org
How dare you blame me and my team's perfect software!
Actually, I was still blaming me, as I was the original repo-add author 8)
participants (4)
-
Aaron Griffin
-
Allan McRae
-
Dan McGee
-
Pierre Schmitz