Ya know...
If the same effort was put into fixing bugs as was put into ensuring tickets
entered are correct, I think we would have a lot less bugs.
How about configuring Trac with Drop Down selections for maintainers, or
Error checks that automatically prompt us, or even prevent the ticket from
Hi
I updated one of my boxes yesterday and the texlive ports where
updated to the new 2009 version, since then some of my documents have
been failing to build as the wrapfig.sty and moreverb.sty files are
missing, i.e. the build fails with:
! LaTeX Error: File `wrapfig.sty' not found.
or
!
On Tue, Jun 22, 2010 at 08:51:38AM -0500, Adam Mercer wrote:
! LaTeX Error: File `wrapfig.sty' not found.
! LaTeX Error: File `moreverb.sty' not found.
these documents built fine using the texlive 2007 ports, is there some
other port I need to install to get these missing style files?
Yes,
On Tue, Jun 22, 2010 at 10:36, Dan Ports dpo...@macports.org wrote:
Yes, texlive-latex-extra.
The new texlive ports don't install a full installation by default. You
can get one by installing texlive +full, but it's pretty big so I
recommend installing any specific packages you need instead
On Jun 22, 2010, at 9:08 AM, Jeff Singleton wrote:
But I would think the maintainer should be maintaining which should include
the random test builds to ensure everything still works.
As a maintainer, I do a bunch of testing before I do an update to a port. I
rarely test it between updates,
At 8:16 PM +0100 6/21/10, Julian Wilcox wrote:
Netgen is a fantastic mesher and I would also like to
encourage more finite element opensource software to be ported.
FWIW: It appears that Netgen is also a tool for comparing netlists,
ie. a circuit design thingy. It's probably some other things as
Thanks for the reply.
FYI .. the whole refund thing doesn't work on me, and probably doesn't
with most seasoned tech-heads.
I understand the free aspect, but when people use something on a large
scale, free or not free, expectations still have to be met or else there is
risk of dead-pooling the
On Jun 22, 2010, at 08:08, Jeff Singleton wrote:
How about configuring Trac with Drop Down selections for maintainers,
We had a drop-down for maintainers. It slowed Trac to a crawl. We removed the
drop-down. Most people seem to manage just fine with the text field.
or Error checks that
On Jun 22, 2010, at 2:52 PM, Jeff Singleton wrote:
I understand the free aspect, but when people use something on a large
scale, free or not free, expectations still have to be met or else there is
risk of dead-pooling the project.
I don't know what you mean by dead-pooling.
Lots of people
On Tue, Jun 22, 2010 at 12:56 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jun 22, 2010, at 08:08, Jeff Singleton wrote:
How about configuring Trac with Drop Down selections for maintainers,
We had a drop-down for maintainers. It slowed Trac to a crawl. We removed the
drop-down. Most
On Jun 22, 2010, at 15:14, Scott Webster wrote:
I think this is likely the most common mistake people make when
submitting tickets (failing to cc the maintainer). Perhaps we can add
a little comment next to the cc box that reminds people to do so and
tells them how to find the maintainer
On Tue, Jun 22, 2010 at 1:18 PM, Ryan Schmidt ryandes...@macports.org wrote:
We already have a big red banner reading Please read the Ticket Guidelines
before submitting at the top of the New Ticket form which explains about
Cc'ing the maintainer and everything else we want submitters to
If the current banner doesn't work I don't expect a different banner to work.
I just looked around and it seems if we want the port maintainer to magically
get cced we nee the entry point for ticket submission process to be aware of
the port the ticket is being filed against.
One method would
Yeah ... its why there is a heavily used acronym called RTFM. Because nobody
ever does read the manual.
Besides ... reading, remembering, and knowing the correct way are completely
different.
Humans are not computers and thus do not retain everything we read all of
the time for ever. I doubt
On Tue, Jun 22, 2010 at 1:46 PM, Jeff Singleton gvib...@gmail.com wrote:
piece of information on there. Oh .. I never have this conversation with
other bug sites...probably because the bug form itself contains enough
information that reading a manual is not required.
Well, the current system
On 2010-6-22 23:08 , Jeff Singleton wrote:
Ya know...
If the same effort was put into fixing bugs as was put into ensuring
tickets entered are correct, I think we would have a lot less bugs.
If one or more people wanted to volunteer to wrangle the incoming
tickets, thus freeing up time for
On Jun 22, 2010, at 3:18 PM, Ryan Schmidt wrote:
On Jun 22, 2010, at 15:14, Scott Webster wrote:
I think this is likely the most common mistake people make when
submitting tickets (failing to cc the maintainer). Perhaps we can add
a little comment next to the cc box that reminds people
I don't think I have ever entered the maintainer of a port. Up until
now, I wasn't aware that I needed to.
Saying RTFM for everything that you do isn't the answer. People
expect that Z will work; that's why we have the horrible disasters
that we have in society. Retraining people is hard.
On 2010-6-23 07:41 , Michael_google gmail_Gersten wrote:
So here's a question: If there is a maintainer field in the ports
database for each port, then why can't the bug tracker grab that field
on it's own?
It can, if someone writes the aforementioned plugin. But of course
people don't often
On Jun 22, 2010, at 5:46 PM, Joshua Root wrote:
On 2010-6-23 07:41 , Michael_google gmail_Gersten wrote:
So here's a question: If there is a maintainer field in the ports
database for each port, then why can't the bug tracker grab that field
on it's own?
If users are willing to navigate
On 2010-6-23 08:04 , Ben Greenfield wrote:
On Jun 22, 2010, at 5:46 PM, Joshua Root wrote:
On 2010-6-23 07:41 , Michael_google gmail_Gersten wrote:
So here's a question: If there is a maintainer field in the ports
database for each port, then why can't the bug tracker grab that field
on
21 matches
Mail list logo
