Archive for the 'portmgr' Category

The Ports Management Team: Ports Feature Freeze for FreeBSD 8.3 is now in effect

FreeBSD 8.3 RC1 has been pulicly announced, it is now time for the the
Ports Feature Freeze.

Normal upgrade, new ports, and changes that only affect other branches
will be allowed without prior approval, but with the extra

Feature safe: yes

tag in the commit message. Any commit that is sweeping, i.e. touches a
large number of ports, infrastructural changes, commits to ports with
unusually high number of dependencies, and any other commit that requires
the rebuilding of many packages will not be allowed without prior explicit
approval from portmgr@ after that date.

Thomas
on behalf of portmgr@

The Ports Management Team: Upcoming 8.3 ports feature freeze

The FreeBSD 8.3 release process is under way, you can view the schedule,
http://wiki.freebsd.org/Releng/8.3TODO.

As has become the custom, a ports feature freeze is anticipated to be
announced with the RC1 date, tentatively scheduled at this time
for March 2, 2012. Watch for further announcements as we get closer.

During the feature freeze, committers are expected to be conservative with
their commits, that is, no sweeping commits, infrastructure changes, or
commits to ports with a high number of dependencies.

The Ports Management Team: FreeBSD 9.0 ports slush is over

Just to make it officially official, now that FreeBSD 9.0 has been shipped, the ports slush state is now been lifted.

Ports committers are now entitled to perform sweeping commits. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree.

And just remember, PLEASE TRY TO NOT BREAK THE INDEX!

Thomas
on behalf of portmgr@

The Ports Management Team: New ports announce mailing list

At the request of adamw@ (and others) we have setup a ports-announce@ mailing list to try distinguish the usual traffic on the ports@ list vs the announcements that seem to get lost in there.

You can subscribe at http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce

It is intended, but not limited, to be a means of communicating portmgr@ announcements, Calls for Testing, plus other relevant information to be used by our committers and ports maintainer community.

It is our hope to keep this relatively low in traffic. It is a moderated list, under the auspices of portmgr@.

Please subscribe, sit back, and enjoy.

Thomas
on behalf of portmgr@

The Ports Management Team: Please welcome Beat Gaetzi to the Ports Management team

We are pleased to announce the addition of Beat Gaetzi (beat@) to the team. Beat, like many others was a long time contributor prior to receiving his commit bit in 2009. Beat is well know for his work with the Gecko and Vbox teams, in addition to his hosting of test/development repositories for many of our community members.

Beat’s next unenviable task will be taking us through the rocky road ahead in migrating the CVS Ports repository to Subversion.

Please join me in welcoming Beat to the team. Congratulations Beat!

Thomas
on behalf of portmgr@

The Ports Management Team: Feature freeze for 9.0 is now in effect

With this commit, http://svnweb.freebsd.org/base?view=revision&revision=227337, the RC2 phase is under way.

Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval, but with the extra

Feature safe: yes

tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with
unusually high number of dependencies, and any other commit that requires
the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date.

Thomas
on behalf of portmgr@

Baptiste Daroussin: Aujourd’hui j’ai un an

Il y a un an jour pour jour que je faisais mon premier commit dans les ports FreeBSD sous le mentorat jadawin@ et tabthorpe@ merci à eux :).

Ça passe vite... :)

Le bilan de cette première année est plutôt positif je pense malgré quelques ratés. Plein de bonnes choses mais aussi quelques trucs que je pensais faire que je n'ai pas encore réussi à pousser.

Je vais commencer par les échecs et finir par les réussites c'est toujours mieux de finir par les bonnes choses :)

Pas Bien

Il y a un moment déjà que je bossai sur un framework d'options pour les ports qui viserai à remplacer l'actuel en offrant plus de fonctionnalités: groupe d'options, options incompatibles, options dépendantes d'autres options etc. Dans ce cahier des charges, il fallait aussi que le nouveau framework puisse remplacer le vieux de manière transparente.

La première étape je l'ai atteinte assez facilement, la complication est venue quand il a fallu faire la seconde. Du coup un an après je n'ai toujours pas pu pousser mon framework et il reste toujours le vieux dans l'infrastructure. J'espère pouvoir changer ça rapidement, j'ai une idée à creuser sous le coude :).

Un autre loupé pour le moment c'est le fakeroot ou pkgdir. J'aimerai bien pouvoir construire des packages sans avoir à les installer. J'aimerai aussi que l'on ne puisse pas installer de packages depuis les ports dont le PLIST est foireux. Je me suis donc lancé dans la création d'un patch fakeroot (en fait j'ai piqué dans un premier temps ce que nos voisins de midnightbsd avaient fait quand ils ont forké notre système de ports). Au final j'ai obtenu quelque chose qui marche dans 80% des cas. C'est pas mal, mais c'est complexe et je n'aime pas ne pas proposer de choses simples. Donc il n'a pour le moment pas été plus loin. En revanche j'ai récemment eu de nouvelles idées à ce sujet et devrait apporter de bonnes choses :). Wait and See.

Moyen pas bien ou moyen bien au choix

Passons des loupés de cette année aux choses mitigées: libreoffice. J'ai fait le port de la version 3.3 avec succès. J'avais 2 motivations pour ça: réutiliser au maximum ce qui est déjà dans les ports (ajouter les ports nécessaires si besoin) et pouvoir tourner sur pointyhat. Dans les deux cas c'est réussit.

En revanche, du côté de 3.4 c'est une autre paire de manches. Pour des raison qui m'échappent pour le moment je n'arrive pas à le compiler :( alors que la version 3.5 (git) compile sans trop de difficultés je galère sur la version 3.4. En même temps je ne consacre pas beaucoup de temps à libreoffice du coup je ne suis pas de près les évolutions et découvre les problèmes sur le tard. J'ai créé il y a peu une équipe office@ pour en prendre soin, en espérant que à plusieurs personnes, on arrive à toujours rester synchronisés avec l'upstream. Pour le moment la mayonnaise à l'air de prendre.

Bien

Les réussites maintenant:

Je suis portmgr@ maintenant, ce qui veut dire que mes démarches pour essayer d'améliorer les choses ont été bien acceptées :). Je ne m'attendais vraiment pas à devenir portmgr et encore moins aussi rapidement. Comme quoi s'investir est payant :)

Les campagnes de "deprecation". Les ports sont tout sauf dictatoriaux, du coup tout le monde peut y mettre ce qu'il veut ou presque. Mais le problème c'est que très peu de gens pensent à enlever les ports morts. Ceux, dont il n'y a plus de distfile publiquement dispo, dont le projet est totalement abandonné, etc. Tout le monde laisse traîner ça dans ports@. Moi je n'aime pas laisser traîner les vieux trucs partout comme ça, j'ai donc lancé 2 campagnes de "deprecation" la première a déjà viré environ 500 ports, la seconde devrait en virer 200 dans quelques jours, je pense que c'est une réussite et je vais le renouveler régulièrement. :)

Enfin last but not least, PKGNG :). Il y a un peu plus d'un an je tentai de porter pkgin sur FreeBSD. Je pense avec un certain succès dans le sens où ça a fonctionné pour de vrai.

Mais j'étais déçu par le côté trop pkgsrc (logique en même temps :)) de l'outil et par les tours de magie qu'il aurait fallu réaliser pour le faire fonctionner vraiment correctement sur FreeBSD. La faute n'est pas à pkgin mais plutôt aux différences entre les ports et pkgsrc.

Bref de là je me dit qu'il faudrait tout refaire "from scratch", en profiter pour avoir une architecture autour d'une bibliothèque et tout et tout. En gros je pensais partir sur une n-ième libpkg-qui-n-aboutira-jamais(c)(tm), pas très motivant :). Heureusement je n'étais pas seul à m'intéresser au sujet. Deux personnes qui ne sont pas motivées à l'idée de faire un projet qui n'aboutira pas et qui si même si il aboutissait ne serait jamais accepté ... Bah c'est assez con pour se lancer dedans :). Julien Laffaye et moi nous lançons donc dans le projet (aidé, surtout au début, de Philippe Pépiot), de longs mois plus tard, et toujours pas convaincu de ne pas faire ça pour rien, on décide de parler du projet pour le faire connaître. En effet nous avions quelque chose de viable et espérions ramener ainsi du monde sur le projet. Ce fut une très bonne idée ce mail :), dans la foulée nous avons été invité à participer au BSDCan pour présenter pkgng, et participer au groupe de travail sur pkgng. Le baptême du feu :). Préparé à recevoir des volées de critiques sur le pourquoi de SQLite, ou de tel autre choix, nous pensions devoir défendre notre bout de gras.

Bilan: pkgng a été accepté sans trop de discussions (grosse surprise :), et est maintenant clairement vu que le remplaçant des pkg_* tools. Dans quelques jours, on devrait sortir l'alpha2 avec beaucoup d'évolutions. Mais pas de teasing pour le moment :).

PS: pkgng c'est ici que ça se passe :)

The Ports Management Team: FreeBSD portmgr thank you to the FreeBSD Foundation

We would like to publicly thank the FreeBSD Foundation for granting Baptiste Daroussin and Julien Laffaye a travel grant to travel to BSDCan 2011 for the Ports and Packages Working Group held at in Ottawa last week.  The working group itself was a huge success and a number of improvements with regard to automated binary package creation and distribution to ease upgrade procedures for our users were discussed and will hopefully be implemented over the next few months.

None of these improvements, however, would be possible without a long overdue rewrite of the package tools provided by FreeBSD.  Over last few years, a number of attempts were made to enhance the current tools, but none have been as all-compassing as the PKGNG project by Baptiste and Julien.  The presentation given by Baptiste at the packages summit and summariszed at the DevSummit track of BSDCan showed a comprehensive new tool that can completely replace the current tools, and provide a clear migration path from the old to the new tool.  It also provides a large number of new features while keeping the old ones and is a lot more flexible to be able to add more features later.  As you may have heard, Baptiste has also joined the ports management team as a result of his efforts.

Thanks again to the Foundation for sponsoring Baptiste, Julien, Simon Nielsen (Deputy Security Officer) and Thomas Abthorpe (Ports Management Team) who all were instrumental into making the ports working group such a success.

 

Thomas
on behalf of portmgr@

The Ports Management Team: So long HP Blade Cluster and thanks for all the packages

After many years of faithful service, today the FreeBSD Ports Management Team decided to decommission the HP Blade Cluster. When the 20-node BladeSystem was donated to the FreeBSD Foundation, by Hewlett-Packard back in 2005, it tripled the speed of the i386 package building process. Today, and several hardware generations later however, it is no longer profitable to keep the system running inside the cluster. The portmgr team has been very pleased with the system, especially the built-in out-of-band power management- and console system. The system has also proved to be very reliable; even with continuous high workloads for so many years, the only hardware failures we experienced were some of the disks. The i386 package cluster now consists of 5 Xeon-based servers hosted at ISC until the new clusters are fully online.

We again wish to thank HP for their generous donation and Yahoo! for hosting it in one of their datacenter.

Erwin Lansing: Summary of the FreeBSD Ports and Packages Summit at BSDCan 2011

Just a quick note to point to my slides that summarize the Ports and Packages Summit at the FreeBSD DevSummit during BSDCan 2011, which can be found here. Also, we looking forward to feedback on the PKGNG project that was announced earlier and will replace the current pkg_* tools to handle ports installation and package handling and which will be a focus for portmgr over the next few months.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The Ports Management Team: New portmgr member: Baptiste Daroussin

Portmgr is pleased to announce that Baptiste Daroussin, bapt@, has joined the ranks of the Ports Management team. He has been working hard on some large infrastructure improvements, including a new OPTIONS framework and PKGNG that will replace the current pkg_* tools and bring them into the 21 century. We are very happy to have him onboard, where he will continue working on these and other much needed infrastructure improvements with the full power of the pointyhats.

The Ports Management Team: Ports and Packages for Supported Releases

Portmgr published a new page on their website which describes the current support and EoL policies for the ports tree and released packages. The main take-home messages are:

  • Support of FreeBSD releases by ports and the ports infrastructure matches the policies set out by the FreeBSD Security Officer.
  • Package builds will use the oldest supported minor release within each major branch to ensure ABI and KBI backwards compatability within each major branch, and support all minor versions of each major branch, including -RELEASE and -STABLE.

See the full policy on the portmgr webpage.

The Ports Management Team: New member for portmgr@

The Ports Management team is pleased to announce that Thomas Abthorpe, tabthorpe@, has become a full voting member of the team.  He will continue in his substantive postion as the -secretary in addition to other duties he will pick up along the way.

http://www.freebsd.org/news/newsflash.html#event20110310:01

Martin Wilke: PCBSD sponsor FreeBSD KDE Build box

I’d like to note that the KDE FreeBSD Team is now
receiving assistance from PCBSD again. Since I left
the KDE Team, things have gone terribly wrong. After
having a few conversations with my old team, I finally
figured out what the problems were. But the main problem
was missing a package build system, and I managed to find
a solution for that with Kris’s help. Apparently this was
a root cause to some other issues and having it solved
helped to speed up other processes.

I’d like to say thanks to Kris Moore, Josh Paetzel,
Dru Lavigne and of course the iXsystem for their
generous donation to build a test machine for KDE.

PS: This means not i jump back to the KDE Team
but I’m always willing to Help when i can.

Martin Wilke: Python Infrastructure changes Roadmap

Howdy,

I just want to inform you that the python team plans to make some infrastructure changes.
The changes involves the following 3 steps:

[python 2.5/2.6/2.7 improvements/ py 3.2 adding]
We plan to integrate some important patches:
ports/153952 ports/148406 ports/149167 ports/152224 ports/133081

python 3.2 will be released on 12 Feb, we’ll wait for the final release
before adding it to the build. For all of these we will do an exp-run
to make sure nothing will break during the build. It takes approximately 2 weeks if all works fine.

[python24 removal]
Python 2.4 is not supported anymore since 2008, and it has a lot of security problems.
Unfortunately this will cause the removal of some zope stuff. The following ports are affected:

www/zope210
www/zope211
www/zope28
www/zope29
+ zope plugins which are dependant on one of these ports. Philip is working on an
update to some new zope versions. I hope we can cooperate with him to get things
smoothly done. For all these we will do an exp-run to make sure nothing will break during
build. It takes approximately 3 weeks if all works fine.

[python 2.7 move to default]
python 2.7 is already stable enough to be moved over as default. For this one we will do an exp-run
to make sure nothing will break during the build. If all works fine, we think we can complete it by the
first week of March.

Martin Wilke: [CFT] xf86-video-ati 6.14.0

Howdy,

2 days ago was a new ati driver released. fluffy@ and me was using for
few weeks the git version without problems, but we’d like to make
sure this dosen’t broke anything for our ati users.
Here is a patch: http://people.freebsd.org/~miwi/ati-6140.diff
Changelog: http://lists.freedesktop.org/archives/xorg-announce/2011-February/001602.html

Please test and report back, if no problems I’d like to commit it next week.

thx
PS: this release fix some problems with HD54XX chips the bug with strg+ctrl+backspace; bug is gone for me.
PSS: Thx Dima for preparing the git tarball :P

Martin Wilke: [CFT] KDE SC 4.6.0 for FreeBSD.

Hello Internet,

The FreeBSD KDE Team is happy to let you know that KDE SC 4.6.0 has been
released a few Days ago, and the Release is ready for a public test. Before
you ask, no, we do not want to put KDE 4.6.0 in the ports tree before
FreeBSD 8.2/7.4 is released.

What’s new:
KDE SC 4.6.0 provides major updates to the KDE Plasma workspaces, KDE
Applications and KDE Platform. Theses releases, version 4.6, provide many
new features in each of KDE’s three product lines. The official
release notes for these releases can be found at
http://kde.org/announcements/4.6/

Now you can get KDE SC 4.6 via svn checkout:

svn co http://area51.pcbsd.org/trunk/area51/PYQT/
svn co http://area51.pcbsd.org/trunk/area51/PORTS
svn co http://area51.pcbsd.org/trunk/area51/KDE
svn co http://area51.pcbsd.org/trunk/area51/Tools/

Then try:

sh Tools/scripts/portsmerge
sh Tools/scripts/kdemerge

Happy updating!!

The Ports Management Team: Ports Feature Freeze for 7.4 and 8.2

phase is under way.
Normal upgrade, new ports, and changes that only affect other branches
will be allowed without prior approval but with the extra Feature safe:
yes tag in the commit message.  Any commit that is sweeping, i.e.
touches a large number of ports, infrastructural changes, commits to
ports with unusually high number of dependencies, and any other commit
that requires the rebuilding of many packages will not be allowed
without prior explicit approval from portmgr@ after that date.
Thomas on behalf of portmgr@

Martin Wilke: Qt-4.7 and friends update coming soon,

Slowly i start back to my FreeBSD and also portmgr work.
I’ll start with a exp-run of Qt-4.7 and friends, the build
will start tonight and should be done in 2 days, so
if everything good we’ll get it maybe in the weekend :-) .

so long ..

The Ports Management Team: MD5 for distinfo has been deprecated

erwin@ committed http://www.freebsd.org/cgi/query-pr.cgi?pr=149657, based on work by dougb@ and rene@.   It deprecates the use of md5 checksums in distinfo.  So here on in, when you run make makesum, the md5 will no longer be generated, only the sha256 checksum.

Existing distinfo containing md5 info will silently be ignored.  So at this time there is no need re-create distinfo for the sake of removing it, just allow the regular flow of ports updates take care of it.