Welcome miwi back to the portmgr team!
The FreeBSD Ports Management team is pleased to welcome back Martin Wilke, aka miwi@, to it's ranks. As everyone knows, Martin is the developer who contributed the largest number of commits to the ports tree: more than 20,000 commits since 2006! In November 2014, Martin decided to step down from duties at FreeBSD in order to save time for both his growing family and real job. Luckily for us, Martin has more time now for FreeBSD, so please join me in welcoming miwi@ back to the portmgr team. Frederic on behalf of portmgr@ pgpQIWqBRdivU.pgp Description: PGP signature
Monthly dashboard
Greetings porters, in case some of you are not into social networks: please find hereafter a post that was published on portmgr's blog which talks about the good figures we saw in last month's dashboard. I believe it is important to share those promising figures with all of you guys who are interested in FreeBSD's ports tree. Many thanks to all for your time and dedication! Frederic --- Thursday morning, 5 AM, I couldn't sleep. I thought I could use the time before work to do something useful, so I started handling a few PRs for FreeBSD. After a couple of commits, a warm shower, and just before heading to work, I quickly browsed through my irc backlog and suddently got very sad: someone was angrily asking why bug reports were being ignored for such a long time, pushing for his own PR to finally be given some consideration. Thinking about it in the bus to work I realized that this guy was right to complain: when a bug is reported it should ideally be fixed right away. Still I was feeling sad because being on the other side of the fence I know how much dedication volunteers put into FreeBSD, but I was not sure everybody was aware of this. I had to find something to express this dedication. That's how the idea of the monthly dashboard came: simple figures that can tell a whole story. See for yourself with this dashboard that can be found in portmgr monthly report for June 2014: -- Monthly dashboard Number of messages to portmgr@: 564 (+53%) Number of commits on ports: 3,717 (+17%) Number of ports PRs closed: 873 (+25%) Active ports committers: 147 (+10%) -- Isn't it amazing? Nearly 4,000 updates on the ports tree and nearly 900 problem reports closed in a single month! That's a tremendous amount of work done by our committers. Take Linux for example: with more than twice as much contributors during the same period four times less commits were applied to the Linux kernel than to the FreeBSD ports tree [1]. Those figures pay tribute to our committers, and I am pleased to see that the activity keeps growing. I personnally believe there has never been a better time to start contributing to the FreeBSD ports tree with all those new features currently being introduced. So come and join the party! -- [1] Statistics taken from http://www.ohloh.net/p/linux: 962 commits done by 344 contributors (activity recorded from Jun 9 2014 to Jul 9 2014) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Porters Handbook update
Beloved porters, following some discussions related to the rights and duties of ports maintainers it became obvious that our handbook was not specific enough on the matter. Hence an update was committed that aims at clarifying the notion of maintainership and all porters are invited to peruse the changes: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html And of course, a big thanks to all of you who dedicate their time to maintain our ports! Frederic, with portmgr-secretary hat on pgpP_OokZ4XxA.pgp Description: PGP signature
Re: Owncloud port update
Hi Loic, Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). Thanks for submitting those updates. I assume kevlo@ has been busy recently and was not able to take care of your PR. Being an owncloud user myself I will be able to test your patches, and I will handle your two PRs to update to 5.0.7 within the next couple of hours. Regards, Frederic PS: Kevin, as those updates fix critical vulnerabilities I prefer not to wait for the usual timeout for ports/179494 so I could update to 5.0.7 in one shot, my apologies for that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Owncloud port update
Thanks for your reply Frederic, that's great for FreeBSD owncloud community users :) Well, there's nothing to be proud of here as we should have been much more reactive considering the number of vulnerabilities that were brought to light since last month. I just committed your update to owncloud 5.0.7, and I also filled an entry in vuxml to describe those vulnerabilities. Again, apologies to our FreeBSD owncloud community users and we will try to be more reactive next time. Regards, Frederic ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: non-WWW calendar/diary software
2013-03-07 12:42, Wojciech Puchar skrev: anyone knows such a thing - with polish translation (or translations at all so i can translate)? preferably integrated with GNOME2, not a must, but DEFINITELY evolution bloatware. Something simple, just like gnote. I know davical+web browser and it works, but something that doesn't require browser would be much better. At a prompt type cal or ncal If you are not afraid of text user interfaces you also have deskutils/calcurse, with which you can do a bit more than cal or ncal. It has polish translation (unfinished so if you want to help), and the good point is that I am the author of the project and also the port maintainer so if you have issues you know who to ask ;) Regards, Frederic ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [CFT+BRAINSTORM] One USE_ to rule them all
On Wed, Feb 06, 2013 at 10:19:32AM +0100, Baptiste Daroussin wrote: Lots of people are asking to change the name saying they don't like USE_FEATURES here is the list of proposition that have been made, please vote for you favorites :) USE_FEATURES: keep it as is it is cool USE_FEATURE: please singular USES: Why bother with something longer USE: singular I said FEATURES: Why keeping USE? FEATURE: I told you singular! regards, Bapt Being one of those who found USE_FEATURES a bit too long I feel I need to cast my vote now: I would go for 'USE' as it is shorter and more generic than 'FEATURE'. Indeed sets of dependencies could be mentioned here as well (equivalent of USE_XORG for example) which for me are more requirements than features. Moreover it is closer to the actual USE_* variables. Anyway to broaden the choice I also thought about the following: COMPULSORY REQUIRE REQUISITE MANDATORY WANT/WANTED NEED/NEEDED But again, 'USE' is fine by me. Regards, Frederic ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-
I have strong opinions against this, at least for ports with an active maintainer. I really see these deprecation campaigns as treading on somebody's toes. I really like linimon's periodic emails FreeBSD ports that you maintain which are currently marked broken, which I see as a reminder that there are ports of mine that require action, but going further than that and deprecate a port that I maintain without even informing me in an official way is not what I consider collaboration. Even more so because I don't see any advantage in moving a port from BROKEN to DEPRECATED state. If a user has a working version of the port installed, he will stick to that, otherwise, installation will be frown upon anyway. I and bapt have already exchanged opinions on this subject more than once, and I would now like to see what other people (other maintainers in particular) think about it. Can we please stop this? -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp As you inquire people's opinion, I would say that I find this way of proceeding a bit pushy and I consider it a good example of closed communication as I find it: - non-caring: such a commit is a detached and impersonal way to give the information to a maintainer that has not unbroken his port for a long time - dogmatic: it looks like an unwillingness to accept the maintainer's point of view or at least to hear about his work on maintaining the port - superior: deprecating without prior communication with the maintainer stresses differences in status between portmgr/committer and maintainers Hence I am not surprised when you say you feel someone is treading on your toes, and more generally I fear this does not do any good to maintainer's motivation and commitment to the project. On the other hand I also believe those deprecation actions are necessary and I thank bapt for his work on this. To conciliate such a necessary action without hurting the feelings of those maintainers who despite their work could not update the state of their port in a timely manner, maybe it would be good to be more verbose in the log of such commits. Inspired by linimon's emails, something like the following could be added: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been marked as broken for a period of at least six months. As a maintainer of one of those ports, feel free to remove the deprecate status if you need more time to fix the breakage and do not hesitate to contact portmgr@ if you need additional information on this policy. I hope this brings something to the discussion. -- Frederic Culot cu...@freebsd.org pgpx1R7qscdc8.pgp Description: PGP signature
Re: Feedback on wanted port: obskurator
Thanks for your feedback but unfortunately the result is the same even if I
provide the prototype for printf in the source file.
Frederic
Frederic Culot frede...@culot.org wrote:
Following the links on the ports tasks wiki page I found
'obskurator' to be a wanted port ... so I gave it a try
and report about it here.
obskurator is supposed to obfuscate source code by changing
variable names ...
I believe the software itself is unusable and should not be
added to the ports tree in its current state. Indeed, I wrote a
simple code to test the resulting obfuscated program generated
by obskurator and it would not compile.
Here is my test code:
-
#include stdio.h
int my_int1;
int
main (void)
{
char *my_txt1 = Hello world;
printf (first var: %d\n, my_int1);
printf (second var: %s\n, my_txt1);
return 0;
}
-
and obskurator transformed it into the following:
-
#include stdio.h
int my_int1;
int
main (void)
{
char *x1 = Hello world;
x2 (first var: %d\n, my_int1);
x2 (second var: %s\n, x1);
return 0;
}
-
That is obskurator believed printf(3) was a user-defined variable
and replaced it with 'x2', which makes the resulting program
impossible to compile.
Does it by any chance work properly if you provide the prototype
for printf in the source file, instead of depending on the one
that should be provided by the #included header file? If it does,
a possible w/a might be to run the program through CPP first, and
then through obskurator.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Feedback on wanted port: obskurator
Hello,
Following the links on the ports tasks wiki page I found 'obskurator' to be a
wanted port (http://wiki.freebsd.org/AndrewPantyukhin/Ports) so I gave it a try
and report about it here.
obskurator is supposed to obfuscate source code by changing variable names. Home
page for the project is: http://obskurator.sourceforge.net.
The port I prepared for obskurator can be found here:
ftp://culot.org/FreeBSD/obskurator.shar
The above port installed obskurator fine for me (8.1-RELEASE on amd64), but I
believe the software itself is unusable and should not be added to the ports
tree in its current state. Indeed, I wrote a simple code to test the resulting
obfuscated program generated by obskurator and it would not compile.
Here is my test code:
-
#include stdio.h
int my_int1;
int
main (void)
{
char *my_txt1 = Hello world;
printf (first var: %d\n, my_int1);
printf (second var: %s\n, my_txt1);
return 0;
}
-
and obskurator transformed it into the following:
-
#include stdio.h
int my_int1;
int
main (void)
{
char *x1 = Hello world;
x2 (first var: %d\n, my_int1);
x2 (second var: %s\n, x1);
return 0;
}
-
That is obskurator believed printf(3) was a user-defined variable and replaced
it with 'x2', which makes the resulting program impossible to compile.
As a conclusion I would say that 'obskurator' should be removed from the wanted
port page at http://wiki.freebsd.org/AndrewPantyukhin/Ports as it does not
manage to generate compilable obfuscated code as it claims to do.
Hope this helps,
Frederic
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
