[www/sams] #make package doesn't stick an empty dir.
Hi all, Right after the installation process there is a backup directory (that is empty yet) relevant to the prefix. After typing #make package there is a .tbz appears. I don't know the reason but there is no backup directory in it. On the other hand, pkg-plist does include backup, so if I try to #make deinstall it can't find the directory and stops (couldn't find a ./backup. Incorrectly specified huh?) The strange thing is that if you type #cd /usr/ports/www/sams && make install clean #pkg_delete sams-1.0.5,1 there are no warnings! How to fix this? OR Can I skip the warning and go ahead submitting the upgrade? Thank you. -- Yuriy Grishin. ___ 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: [www/sams] #make package doesn't stick an empty dir.
Scot Hetzel wrote: 2010/1/10 Yuriy Grishin: Hi all, Right after the installation process there is a backup directory (that is empty yet) relevant to the prefix. After typing #make package there is a .tbz appears. I don't know the reason but there is no backup directory in it. On the other hand, pkg-plist does include backup, so if I try to #make deinstall it can't find the directory and stops (couldn't find a ./backup. Incorrectly specified huh?) The strange thing is that if you type #cd /usr/ports/www/sams&& make install clean #pkg_delete sams-1.0.5,1 there are no warnings! How to fix this? OR Can I skip the warning and go ahead submitting the upgrade? You should fix the port, so that the package will contain the backup directory. Add the following to the pkg-plist: @exec mkdir -p %D/%%DATADIR%%/backup Thanks, it works! -- Yuriy Grishin ___ 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"
[www/sams] What's wrong with my patch?
Hello, More than 2 weeks ago I tried to take maintainership of www/sams because it hasn't been updated for a long time. Current state : feedback. (but I've sent the file) Could somebody please explain me what wrong with the patch is? Why didn't the state changed? See the pr here : http://www.freebsd.org/cgi/query-pr.cgi?pr=128124 -- Kind Regards, Yuriy Grishin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[www/sams] why did commiter bump PORTREVISION ? Now it's broken.
Hello
I'm the maintainer of the port www/sams.
In early of December 2008 the developer released new version of SAMS --
1.0.4
I tried to take most of users comments and sent pr
http://www.freebsd.org/cgi/query-pr.cgi?pr=129816
Few days afterwards miwi wrote that he couldn't extract my diff (may be
because I had sent it using windows+seamonkey?)
I upload files to my homepage and submitted follow-up.
A few days later I saw that the port has been updated, BUT:
1) http://www.freebsd.org/cgi/query-pr.cgi?pr=129816 the pr is open (is
it normal?)
2) commiter bumped PORTREVISION and it leads to port corruption because
---Makefile---
DISTNAME= ${PORTNAME}-${PORTVERSION}
---Makefile---
thus it searches sams-1.0.3 instead of sams-1.0.4 ==> hash check will fail
Questions :
1.Should have I say in the pr that it was not only has been updated by
me but also by the developer?
2.What should I do now?
___
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: [www/sams] why did commiter bump PORTREVISION ? Now it's broken.
Wesley Shields wrote:
On Fri, Jan 16, 2009 at 09:48:30PM +0400, Yuriy Grishin wrote:
Hello
I'm the maintainer of the port www/sams.
In early of December 2008 the developer released new version of SAMS --
1.0.4
I tried to take most of users comments and sent pr
http://www.freebsd.org/cgi/query-pr.cgi?pr=129816
Few days afterwards miwi wrote that he couldn't extract my diff (may be
because I had sent it using windows+seamonkey?)
I upload files to my homepage and submitted follow-up.
A few days later I saw that the port has been updated, BUT:
1) http://www.freebsd.org/cgi/query-pr.cgi?pr=129816 the pr is open (is
it normal?)
The PR is still open because it has not been resolved yet. Your patch
is still outstanding.
I see.
2) commiter bumped PORTREVISION and it leads to port corruption because
---Makefile---
DISTNAME= ${PORTNAME}-${PORTVERSION}
---Makefile---
thus it searches sams-1.0.3 instead of sams-1.0.4 ==> hash check will fail
According to the CVS logs PORTREVISION was bumped because of the
OpenLDAP update. This is normal.
The distfile information never changed with this commit. I was just now
able to fetch and verify the checksums for the distfile so I don't see
any problem. When the patch in ports/129816 is applied there won't be a
problem with checksum either as the distinfo will be updated to reflect
the new distfile.
I didn't know that distfile is untouched now. Thanks for the explanation.
Questions :
1.Should have I say in the pr that it was not only has been updated by
me but also by the developer?
I don't understand what you're trying to say here.
I mean Not only a few options to the port added (make config options).
Binaries are also different thus distfiles must be different otherwise
the port is broken.
I didn't know about the trick with distfiles, sorry for the panic.
2.What should I do now?
Nothing. I'm sure Martin will get to this PR when he has time and will
contact you if there are any problems with the update.
Allright, okay.
___
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"
