n making time to take a look at the patch more
intensively, if there's some doubt about it, but anything that actually
*works* for both Linux and kfreebsd*-gnu and/or knetbsd*-gnu is unlikely to
break netbsdelf*-gnu (one possible point of note is that the Debian NetBSD
port follo
e will, in fact, correctly solve this
problem on a 64-bit architecture. Since I don't particularly trust that I can
verify this sufficiently, myself, would it be possible to get a test build
verified in some fashion?
--
Joel Aelw
It would also be nice if you can ask upstream to update
config.guess and config.sub in their next release.
I could ask, but given that the upstream has not made a release in several
years, I doubt it will change much in the immediate future.
Thanks for your cooperation.
Of course,
than 'wishlist' - the early RFCs had strong reasons for
establishing 'be conservative in what you send' as well as 'be liberal in
what you accept', and fixing this seems likely to be fairly straightforward
(though given the state of 3.0RC3, I would, I would expect it may w
ot... well, the patch is still in
the package, fear not.
--
Joel Aelwyn <[EM
ince it does not cause failures in the normal
case (thus warranting a severity of only 'minor
nsider lowering the priority and tagging it wontfix for the
relevant versions.
--
Joel Aelwyn <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
ses of autoconf, before I was willing to maintain it as anything but
d to check on
whether $check_section having a trailing part at this stage in the code
is a "must", "must not", or "may"; you've covered the first two, if the
latter is actually what&#
bad. I'll try to look into this soon.
> Correcting the otpw_1.3-2sarge.package file manually and running debpool
> --rebuild-all made debpool use the correct values when generating the Packages
> file.
This is consistant; ‐‐rebuild‐all works from the .pac
Debian (mostly work) has
been kicking me six wa
gly, but I do intend to resolve this as
soon as I can manage to do the legwork; it's annoying, at the very least,
and there's no reason to let annoyin
would be
possible to do with the package meta-files. I sus
ors or not produce them, but it looks like I'm going to need more
information to duplicate the situatio
On Thu, Feb 17, 2005 at 12:46:26PM +0100, Bill Allombert wrote:
> On Tue, Feb 15, 2005 at 02:38:34PM -0700, Joel Aelwyn wrote:
> > On Tue, Feb 15, 2005 at 11:51:45AM +0100, Bill Allombert wrote:
> > > On Thu, Feb 10, 2005 at 11:29:43PM -0700, Joel Aelwyn wrote:
> > >
hether that version fixes this. If so, there's nothing to be done
for it but wait for the Sarge release (and possibly use a ba
is more or less useless, so I'll simply add it as a forcible
alternative and hope that the Zope maintainer actually rolls it back into
the Zope package
On Tue, Feb 15, 2005 at 11:51:45AM +0100, Bill Allombert wrote:
> On Thu, Feb 10, 2005 at 11:29:43PM -0700, Joel Aelwyn wrote:
> > Package: libjpeg6b
> > Version: 6b-9
> > Severity: minor
> >
> > The libjpeg62-dev package currently Depends on 'libc6-dev'
it didn't fit with the style
or cleanest code path, but DebPool does now search for the first blank line
of the message as the end of the header section.
The fix will be uploaded a
an't simply do 'libc-dev', due to limitations of the packaging system,
currently)
it, for many years; I definitely wouldn't
want to see it fall from Debian. I would potentially be interested in
co-maintaining it with Clém
lease let her know).
2) The current version is now 1.2.5.
Just an update, since the topic came up.
--
Joel Aelwyn <[EMAIL P
his
bug makes Release file signing utterly useless, and that's
tags 275642 +pending
thanks
This feature has been implemented in the SVN repository, and will be part
of the next upload.
--
Joel Aelwyn <[EMAIL PROTEC
tags 275642 -moreinfo
tags 275642 +confirmed
thanks
On Thu, Jan 20, 2005 at 07:15:22PM +0100, Andreas Barth wrote:
> * Joel Aelwyn ([EMAIL PROTECTED]) [050120 19:10]:
> > On Thu, Jan 20, 2005 at 10:30:03AM +0100, Andreas Barth wrote:
> > > However, I think this feature
rimental
However, if you wanted to point testing-volatile at sarge-volatile, you
would first need to add sarge-vola
On Thu, Jan 20, 2005 at 10:30:03AM +0100, Andreas Barth wrote:
> Hi Joel,
>
> * Joel Aelwyn ([EMAIL PROTECTED]) [050120 01:10]:
> > This bug is tagged moreinfo, and has been for about three months now;
> > without this information, I am unable to evaluate whether or not the
&
deal with
manually.
The second option could be set up to trigge
e bug;
otherwise, if I don't hear back from you on it in a week or two, I'll close
it as unfixable in it's current state (specifically, a feature request that
I can't fathom).
--
Joel
agree that the --rebuild-* options need to be able to handle situations
that are somewhat more pathological than they currently can, but I'm not
(yet) sure just what they need to do or how they should do it yet, so this
bug may not be fi
for this has been committed to the SVN repository, and will
appear in version 0.1.10.
--
Joel Aelwyn
it).
Some useful logging added to the Monitor_Incoming routine to make it more
obvious when som
y.
Eventually the logging subsystem should be rewritten to be much more
flexible; in the meanwhile, however, timestamps added to logging entries.
Committed to SVN, will be availabe in 0.1.10.
--
Joel Aelwyn
uld be @reboot
Entirely a thinko. Fixed.
All of the above have been commited to SVN, and will appear in 1.0.10,
which will be prep
imately ran for > 5 minutes).
Definitely not the intended behavior, but I may need more information if I
can't replicate it on my systems. Does the logfile show anything odd?
--
Joel A
tags 291110 +upstream
tags 291110 +patch
thanks
This has been filed as bug #1005 in the upstream IssueTracker, with a
pointer back to this BTS entry.
--
Joel Aelwyn <[EMAIL PROTEC
compatibility matrix; I will be
sure to cross-check that for new versions (and consider poking the Zope
maintainer to check the situation with Zope; if it never supported python
2.2, we probably *should* be requiring 2.3 a
tags 291036 +experimental
severity 291036 minor
thanks
I'll take a look into this, but if it's true, then it's definitely at
least a minor bug, and not just a wishlist item. Severity duly upgraded.
--
Joel Aelwyn &l
nd
it (that would mean these patches apply against Zope, rather than having to
be done by every Zope-based package).
Patches noted, and I will deal with them as soon as the above is resolved.
--
Joel Aelwyn <[EMAIL P
39 matches
Mail list logo
