Re: [HEADSUP] New mailing pkg-fallout
On 2013-07-19 09:05, Tijl Coosemans wrote:
On 2013-07-18 21:33, olli hauer wrote:
On 2013-07-18 21:09, Baptiste Daroussin wrote:
On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote:
Hm, I just picked the bugzilla44 port and struggle over the logs.
=== de-bugzilla-4.4 conflicts with installed package(s):
bugzilla-4.2.6
They install files into the same place.
Please remove them first with pkg_delete(1).
*** Error code 1
But I found no hint in the log that bugzilla-4.2.6 was installed before.
[1]
The same issue for was raised for the de-bugzilla port, I suspect
(ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue.
Is it possible that the new builds do not start with a clean build
environment?
[1]
http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log
http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log
Maybe someone can enlighten my
No it always starts from a clean room, 100% sure of it.
I still have lot of work on the cluster right now, next week I'll probably
have
more time to help
OK, maybe you see why the issue was raised.
I really have no idea since I haven't seen this on my tinderbox builds.
Index: Makefile
===
--- Makefile (revision 323099)
+++ Makefile (working copy)
@@ -10,7 +10,7 @@
MAINTAINER= bugzi...@freebsd.org
COMMENT= German localization for Bugzilla
-RUN_DEPENDS= bugzilla=${PORTVERSION}:${PORTSDIR}/devel/bugzilla42
+RUN_DEPENDS= bugzilla=${PORTVERSION}:${PORTSDIR}/devel/bugzilla44
LATEST_LINK= ${PKGNAMEPREFIX}bugzilla44
Arrrg, thanks for wiping the dust out of my eyes ...
--
Regards,
olli
___
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: [HEADSUP] New mailing pkg-fallout
On 2013-07-18 21:33, olli hauer wrote:
On 2013-07-18 21:09, Baptiste Daroussin wrote:
On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote:
Hm, I just picked the bugzilla44 port and struggle over the logs.
=== de-bugzilla-4.4 conflicts with installed package(s):
bugzilla-4.2.6
They install files into the same place.
Please remove them first with pkg_delete(1).
*** Error code 1
But I found no hint in the log that bugzilla-4.2.6 was installed before. [1]
The same issue for was raised for the de-bugzilla port, I suspect
(ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue.
Is it possible that the new builds do not start with a clean build
environment?
[1]
http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log
http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log
Maybe someone can enlighten my
No it always starts from a clean room, 100% sure of it.
I still have lot of work on the cluster right now, next week I'll probably
have
more time to help
OK, maybe you see why the issue was raised.
I really have no idea since I haven't seen this on my tinderbox builds.
Index: Makefile
===
--- Makefile(revision 323099)
+++ Makefile(working copy)
@@ -10,7 +10,7 @@
MAINTAINER=bugzi...@freebsd.org
COMMENT= German localization for Bugzilla
-RUN_DEPENDS= bugzilla=${PORTVERSION}:${PORTSDIR}/devel/bugzilla42
+RUN_DEPENDS= bugzilla=${PORTVERSION}:${PORTSDIR}/devel/bugzilla44
LATEST_LINK= ${PKGNAMEPREFIX}bugzilla44
signature.asc
Description: OpenPGP digital signature
Re: [HEADSUP] New mailing pkg-fallout
On 07/18/13 00:14, Anton Shterenlikht wrote: The volume unsustainable. I unsubscribed already. Me too. Subscribed yesterday evening; gone this morning. I suggest the mail is sent to maintainers only. This seems to me a far better solution. Just my 2c. bye av. ___ 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: [HEADSUP] New mailing pkg-fallout
On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Erwin -- Erwin Lansinghttp://droso.dk er...@freebsd.orghttp:// www.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
Re: [HEADSUP] New mailing pkg-fallout
Date: Thu, 18 Jul 2013 10:04:52 +0200 From: Erwin Lansing er...@freebsd.org To: freebsd-ports@freebsd.org, po...@freebsd.org Subject: Re: [HEADSUP] New mailing pkg-fallout On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Erwin I want to help, but my commitment and skills are not even close to yours. If there is portscluster/portsmon type failure table, I'll check it periodically to see if there are any ports I can work on. And for all maintained ports, the mail should certainly go to the maintainer. Anton ___ 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: [HEADSUP] New mailing pkg-fallout
On Thu, Jul 18, 2013 at 10:04:52AM +0200, Erwin Lansing wrote: You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit) testing ITYM singing :-) In any event, this may be a case where looking at the mailing list through another lens may be less painful: http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/ mcl ___ 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: [HEADSUP] New mailing pkg-fallout
On 07/18/13 10:04, Erwin Lansing wrote: On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Hello Erwin. I subscribed to that list because I maintain a couple of ports. They are small, not so important ports, I don't think I deserve any medal, but that's what I can do. Perhaps in the future I'll have more time and skills to spare, but that's how it is now. I subscribed to that list exactly because I hope my ports don't show unexpected problems. I thought this would be a good idea, because I thought it would help me achieve this goal. Unfortunately, it does not: it does not save me time and efforts, but, on the contrary, it's been hindering me (by wasting time and resources). We are not discussing the goal, only the tools. If I get a mail regarding a port I maintain, I'll happily try and find some time to look into it. If I have to wade through gobs of mail which means very little to me, already a share of my time may be gone. Don't get me wrong, I'm not saying that list should be deleted; if it is useful to someone, fine, let them go for it. In my case, if I'll get more targeted mails, I'd have a bigger chance to look into them. Again, just my 2c. bye Thanks av. ___ 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: [HEADSUP] New mailing pkg-fallout
On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli ___ 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: [HEADSUP] New mailing pkg-fallout
On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote: On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli No it always starts from a clean room, 100% sure of it. I still have lot of work on the cluster right now, next week I'll probably have more time to help regards, Bapt pgpG9nqY3SKeS.pgp Description: PGP signature
Re: [HEADSUP] New mailing pkg-fallout
On 2013-07-18 21:09, Baptiste Daroussin wrote: On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote: On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli No it always starts from a clean room, 100% sure of it. I still have lot of work on the cluster right now, next week I'll probably have more time to help OK, maybe you see why the issue was raised. I really have no idea since I haven't seen this on my tinderbox builds. -- Regards, olli ___ 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
[HEADSUP] New mailing pkg-fallout
Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt pgpEdKdPn_2MC.pgp Description: PGP signature
Re: [HEADSUP] New mailing pkg-fallout
The volume unsustainable. I unsubscribed already. I suggest the mail is sent to maintainers only. For unmaintained ports something similar to pointyhat would be helpful: http://pointyhat.freebsd.org/errorlogs/amd64-8-previous/ Thanks Anton ___ 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
