Bug#772993: Acknowledgement (O: chimera2 -- ancient web browser)

close 772993 thanks This was of course a mistake - should have been filed on wnpp not the package I was orphaning. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#772997: O: pcre3 -- Perl 5 Compatible Regular Expression Library

Package: pcre3 Severity: important I request an adopter for the pcre3 package. If you don't already know what it is, you're probably not the right person to take it over, but the description is: This is a library of functions to support regular expressions whose syntax and semantics are as c

Bug#772995: O: chimera2 -- ancient web browser

Package: wnpp Chimera2 is an ancient web browser for X11. Fifteen years ago when I packaged it, it was handy to have a less bloated web browser, and almost all web pages still worked well on it. Now it's basically useless as a browser, at least for the public internet, as hardly any web pages w

Bug#772994: O: pcre3 -- Perl 5 Compatible Regular Expression Library

Package: wnpp Severity: important I am orphaning and request an adopter for the pcre3 package. If you don't already know what it is, you're probably not the right person to take it over, but the description is: This is a library of functions to support regular expressions whose syntax and se

Bug#772993: O: chimera2 -- ancient web browser

Package: chimera2 Chimera2 is an ancient web browser for X11. Fifteen years ago when I packaged it, it was handy to have a less bloated web browser, and almost all web pages still worked well on it. Now it's basically useless as a browser, at least for the public internet, as hardly any web pag

Bug#760327: pcre: disable JIT on powerpcspe, x32

I apologise for not having done anything about this yet. I've been busy with various things including moving house, and still do not have internet in the new house. Your patch looks good. If you want to do an NMU that would be appreciated; otherwise I will do a release as soon as I can but tha

Bug#656008: nmu for pcre3

Oh I'm sorry, I'd completely forgotten about that one. I have no objection to your NMU. On 29 Sep 2014, at 00:21, Michael Gilbert wrote: > Hi, I've uploaded an nmu enabling build hardening flags for pcre3 to > delayed/5. Please let me know if I should delay longer. > > Best wishes, > Mike >

Bug#763054: pcre3: FTBFS on hurd because of stack size problem

On 27 Sep 2014, at 16:10, Ólafur Jens Sigurðsson wrote: > The package fails to build on hurd because the pthread stack size in > only 2024 kb instead of the 8192 kb that linux has. > > Would it be a good idea to use the heap instead of the stack to fix > this? I have considered using this anywa

Bug#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64

Thanks for the patch. In fact I was intending to do an upload yesterday, and held off when I saw this message. Looking at the bugs you filed on PCRE and glib (thanks), it looks like I should go ahead with a pcre 8.35 release, and glib will have to deal with this, do you agree? On 20 Jul 2014,

Bug#751390: src:pcre3: use dh-autoreconf to fix FTBFS on ppc64el

On 18 Jun 2014, at 18:44, Helmut Grohne wrote: > Control: tags -1 - patch > > On Mon, Jun 16, 2014 at 06:28:40PM +0200, Helmut Grohne wrote: >> On Thu, Jun 12, 2014 at 02:00:26PM +0200, Erwan Prioul wrote: >>> * Build using dh-autoreconf for new port support. > > The original pcre3 package pat

Bug#747385: pcre3 failed to run test on mips64el: segmentation fault

> It build successfully while failed when run test. Specifically it failed when testing pcregrep - the tests of the library itself worked. Have previous versions worked? After the build has failed, you should be able to find pcregrep in the directory where it has built, and try running it your

Bug#745222: src:pcre3: FTCBFS on arm64 m68k and others: sljit detection uses build compiler

> I fully agree with your assessment. Would you like me to work on an improved patch or would you like to do it yourself? I'd like to do it myself. I'm going to add a shell script as follows: #!/bin/sh $1-gcc jit-test.c -o/dev/null If [ $? -eq 0 ]; then e

Bug#745222: src:pcre3: FTCBFS on arm64 m68k and others: sljit detection uses build compiler

On 19 Apr 2014, at 10:03, Helmut Grohne wrote: > Surely that's not going to work? Having used the host compiler to build the test program, it then tries to execute it on the build machine. I think what is needed is to use #error to abort the compilation of the test program when JIT is not s

Bug#745114: src:pcre3: FTBFS on arm64 m68k and others: sljit not implemented

Rather than hard-coding a list of architectures in the build script, I have included this very simple program: #define SLJIT_CONFIG_AUTO #include "../sljit/sljitConfigInternal.h" #include int main(void) { #ifndef SLJIT_CONFIG_UNDEFINED

Bug#24509: test patch for this issue

On 11/05/13 15:58, Flos Lonicerae wrote: I rebuilt the package 'chimera2_2.0a19-7_amd64.deb' with '-g -O0' then collected the core dump file. And try to look into the issue with gdb: [...] And from the context, it seems that the XLFD_COUNT is related to the XLFD, not the count of FontList info.

Bug#686495: libpcre3: Very large value for re_nsub

I wasn't attempting to get a fix into testing. I agree that the bug is not that serious and I would have no problem with wheezy releasing with the bug present. However I don't need to cherry pick the patch, it's quite separate from the new version update that was also in that version, so I can v

Bug#686495: libpcre3: Very large value for re_nsub

The patch has now been accepted by upstream and will be in the next release. http://bugs.exim.org/show_bug.cgi?id=1287 I'm happy to include it in the debian package before that, and will do when I get time in the next week. On 2 Sep 2012, at 12:35, Patrick Häcker wrote: > Package: lib

Bug#670018: libpcre3-dbg: arch-dependent files in multiarch: same package

Is there any consensus about where debug files should go? Or should I use .buildid instead? On 22 Apr 2012, at 14:20, Julien Cristau wrote: > Package: libpcre3-dbg > Version: 1:8.30-4 > Severity: important > User: multiarch-de...@lists.alioth.debian.org > Usertags: multiarch > > Hi, > > libpcr

Bug#667664: libpcre3: upgrade from 8.12 to 8.30 breaks (oldstable-era) dansguardian

On 5 Apr 2012, at 20:19, Yann Dirson wrote: > Disclaimer: I am still using an old dansguardian (2.9.9.7-2.1, last > pre-2.10 packaged version) because http://bugs.debian.org/536778 which > in itself is a blow in the face of us developers, but that's another > story which *should not* be related t

Bug#667664: libpcre3: upgrade from 8.12 to 8.30 breaks (oldstable-era) dansguardian

I can't reproduce this with dansguardian 2.9.9 either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#665421: pcre3: Invalid version string 8.30..-3 makes impossible to download the packages with apt

On 24 Mar 2012, at 00:53, Dmitrijs Ledkovs wrote: > > Please do not use two consecutive dots in the package name? There's nothing wrong with two consecutive dots. The specification says only that a version number consists of digits separated by non-digits. There is nothing special about dots,

Bug#664983: closed by Mark Baker (Bug#664983: fixed in pcre3 8.30..-2)

In personal email, Hector Oron wrote: > There were more files with wrong SONAME. I assume you have verified it. There were two libraries that were wrong, and I fixed the only two places that had a version number set, so I assumed it was all fixed, but I only checked libpcre.so.3. After I got

Bug#664983: pcre3 #664983

On Thu, March 22, 2012 12:44 pm, Torsten Wohlfarth wrote: > EXTRA_LIBPCRE_LDFLAGS="$EXTRA_LIBPCRE_LDFLAGS \ > - - $NO_UNDEFINED -version-info 1:0:0" > + $NO_UNDEFINED -version-info 16:1:13" Thanks. Actually I knew what the problem was as soon as I saw t

Bug#664983: Version

Since someone has released an 8.30.really8.12-1.1 version, I'm going to released the fixed version as 8.30..-2, as that sorts correctly after 8.30.really8.12-1.1 and before 8.31-1. What would have been wrong with 8.30-1.really.8.12.1 which would have let me replace it with a proper 8.30 version ea

Bug#634250: Please transition pcre3 for multiarch

On 18/07/11 07:47, Steve Langasek wrote: Please find attached a patch to pcre3 to transition it to use of the multiarch library paths as described at . Thanks. I've been meaning to look into this for a while. I hadn't realised it was so straigh

Bug#522441: misreported gzip-compressed files

Similarly, my manpage is mis-reported as a GRUB stage 2. (that's /usr/share/man/man3/pcre_copy_substring.3.gz in libpcre3-dev). gunzip --test would be a more reliable check for whether something is really in gzip format. It's potentially far slower of course, but for changelogs and man pages I

Bug#581202: libpcre3 8.02-1 causes approx/stable to segfault

On 11/05/2010 15:59, Lucas Nussbaum wrote: Upgrading libpcre3 from version 7.8-3 (in testing) to version 8.02-1 (in unstable) causes approx 3.3.0 (in stable) to start segfaulting at startup (on amd64). It works OK on i386. The version in unstable works on both. Although I can reproduce this e

Bug#555808: libpcre3: segfault on matching certain regexes with large input

I believe this is a duplicate the many other bugs in PCRE; basically that it's possible to get stack overflows with certain regexes. It's not a major security problem, in that I don't think you can get arbitrary code execution by a stack overflow. It could possibly allow DoS attacks in some ca

Bug#552002: Time to remove pcregrep?

> It's unclear to me that pcregrep is a genuinely useful alternative, as > as far as I can see it just tries to be like a standard grep but with > PCRE regexs, hence I don't think this is squashing choice or insisting > on One True Grep, but reducing confusion and effort. There is one useful featu

Bug#465676: I have the same bug with subtitleeditor (0.20.0)

Anibal Avelar wrote: Some users has gone this message: $ subtitleeditor subtitleeditor: symbol lookup error: subtitleeditor: undefined symbol: _ZN7pcrecpp6no_argE I think the problem is exactly the same described on this bug. The users had the version 7.4-1+lenny1 and 7.6-1, but I can't reprodu

Bug#464320: Request for binNMUs for libpcre3 [Fwd: Bug#463413: problem solved by recompiling the package !]

On Wed, Feb 06, 2008 at 06:54:47PM +0100, Andreas Metzler wrote: > It simple rebuild would still break partial upgrades. Yes, I agree. I don't think rebuilding the reverse dependencies is the right solution. The changelog suggests that the ABI change is un-necessary (it was an attempt to fix a p

Bug#377587: Patch to ship pcredemo.c in libpcre3-dev

Daniel Hahler wrote: In Ubuntu, we've applied the attached patch to achieve the following: - debian/libpcre3-dev.examples, debian/rules: Install pcredemo.c example. We thought you might be interested in doing the same. Thank you, yes I will do this. -- To UNSUBSCRIBE, email to [EMA

Bug#443114: Please provide an udeb

On Tue, Sep 18, 2007 at 09:32:58PM +0200, Loïc Minier wrote: > Do you think you could provide an udeb for libpcre3? I can't think of any reason why not. I've never built a udeb before so it will have to wait until I've got a few hours free to learn how to do it. -- To UNSUBSCRIBE, email to

Bug#436277: pcregrep: unknown option bit(s) set

Carl Fürstenberg wrote: Everytime I tries to use pcregrep, it just fails telling: pcregrep: Error in command-line regex at offset 0: unknown option bit(s) set It works fine for me: p4-7088:~>grep power.*wait /etc/inittab pf::powerwait:/etc/init.d/powerfail start po::powerokwait:/etc/in

Bug#420280: libpcre3: Please package PCRE 7.0, which includes important fixes and updates

Magnus Holmgren wrote: PCRE is now at version 7.2, with 7.3 coming up. I've tried to package it before. Most of it was easy, but I couldn't get the test-suite to pass because the tests for pcregrep are dependent on a directory listing being in a particular order, which it wasn't. No, I k

Bug#329759: I have this problem

I've got a sarge/testing system, and tried to upgrade to lenny this week, but ran into exactly this problem. Mark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#420280: libpcre3: Please package PCRE 7.0, which includes important fixes and updates

I was waiting for etch to come out. I guess I don't have that excuse any more. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#420191: ftp.debian.org: please remove exim from sid and lenny

Marc Haber wrote: please consider removing exim (that is exim 3, not exim4) from sid and lenny. The package is unmaintained upstream, the last updates have been NMUs (with Mark Baker's consent), exim4 is a replacement. Just to confirm that I agree with this; exim should be removed. -- To

Bug#385718: Are you sure?

Are you sure? This web page, which appears to be the official download site, says at the top that the latest version is 6.30. http://www.inform-fiction.org/software/current.html Yes, I can see that there's a Windows binary that claims to be 6.31. Perhaps there's a Windows specific bug-fix in t

Bug#400121: Can't reproduce 400121 with libpcre3

On Wed, Nov 29, 2006 at 03:49:02PM +0100, Tom Parker wrote: > about my system... where exactly does pcregrep crash? A stack trace > would be nice. p4-7088:~>for i in $(seq 1 8192); do echo -n Z >>file; done p4-7088:~>pcregrep '(.)*' file Segmentation fault Running it under gdb, using the copy i

Bug#400121: Can't reproduce 400121 with libpcre3

On Wed, Nov 29, 2006 at 12:59:47PM +0100, Tom Parker wrote: > I've just been doing the test that Olivier Trichet mentioned with > pcretest, with a file containing 30,000 Z's, and I don't get a crash. > This is with libpcre3 6.7-1 on i386. I can reproduce it with pcregrep; no idea why pcretest mi

Bug#380725: incompatible soversion

On Tue, Aug 01, 2006 at 09:40:26AM +0200, Harald Dunkel wrote: > Upstream uses a different soversion for libpcre than Debian. > RedHat and Suse are using upstream's soversion, i.e. packages > built on these distros cannot be run on Debian. Debian have always built libpcre as a shared library, sta

Bug#375965: Bug#359397: Bug#359404: [exim] Intend to NMU: /usr/doc transition

xim 3 is > maintained by Mark Baker, not me. I'm happy with this suggestion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377295: exim: db_upgrade error during configuration

severity 377295 normal thanks Marc Haber wrote: On Fri, Jul 07, 2006 at 02:32:04PM -1000, Ryo Furue wrote: bash# dpkg-reconfigure exim db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid argument ba

Bug#369241: Esperanta traduko de exim4/debian/po/eo.po

reassign 369241 exim4 thanks Serge Leblanc wrote: Hello, herewith a translation in esperanto of the file: ./exim4/debian/po/eo.po Sincerely, Thanks, however this is for exim 4, which is in the exim4 package; the package called exim contains the (obsolete) exim 3. I've reassigned your bug re

Bug#359662: libpcre3-dev doesn't install libpcre.pc, so pkg-config can't find libpcre

Charles Kerr wrote: > In this case, the only way this bug would be 'important' would be if > most people only use libpcre3-dev for compiling someone else's > software, rather than for writing and developing their own. If you're > writing your own software that uses pcre, obviously you'll know be

Bug#354754: chimera2: Crashes on www.debian.org (recompile needed?)

Helge Kreutzmann I rebuild the sid version on Sarge without problems and now chimear works on several pages where it used to crash badly with the above error (including www.debian.org) Good. The sid version includes some changes to the source code to work with libpng12, which has a slightly d

Bug#354754: chimera2: Crashes on www.debian.org (recompile needed?)

On Tue, Feb 28, 2006 at 10:12:26PM +0100, Helge Kreutzmann wrote: > [EMAIL PROTECTED]:~$ env LANG=C chimera2 > Cache resource not found. Not caching. > libpng warning: Application was compiled with png.h from libpng-1.0.6 > or earlier > libpng warning: Application is running with png.c from li

Bug#353075: exim: Can't send mail: sendmail process failed with error code 1

Tuomo Valkonen wrote: After recent upgrade exim stopped working at all. 'mail' and 'mutt' simply report "Can't send mail: sendmail process failed with error code 1" Hi. Sorry I didn't get back to you sooner. I can't think of any reason why this would happen. I suggest running with debuggi

Bug#347350: unclear errors on clean install

Edwin Martin wrote: The second part of the error message "File exists" is confusing, since the doesn't seem to exist (but maybe existed at the time of the error). The error is very unclear. Especially on a freshly installed system, you wouldn't expect errors. A previous bug report claims tha

Bug#339250: libstdc++ allocator change

Adeodato Simó wrote: > please find a patch at http://people.ubuntu.com/patches/c2a-pcre3.diff Mark, please don't use that patch. The libpcre3 package ships both a C library and a C++ library, and only the C++ one is affected by this libstdc++ change. That's why I haven't done anything

Bug#339630: 'man exim' typos: "matically" and "straightfoward"

A Costa wrote: Found a few typos in '/usr/share/man/man8/exim.8.gz', see attached '.diff'. Thanks for this and the others. I'll include them in the next release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338658: [Fwd: pcre-config.1]

Package: pcre --- Begin Message --- Mark, I've cleaned up the pcre-config man page you wrote for Debian. If you like, you can get the updated version here: http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/pcre/pcre-config.1 Thanks, -- Alexander Peslyak GPG key ID: B35D3598 fp: 6429

Bug#324531: pcre3: CAN-2005-2491

On Mon, Aug 22, 2005 at 06:15:53PM +0200, Adrian Bunk wrote: > It should be checked which of the versions in unstable/testing, > stable and oldstable might be affected by CAN-2005-2491 > (PCRE Heap Overflow May Let Users Execute Arbitrary Code). I'm away on business until wednesday night; if anyt

Bug#323024: /usr/bin/newaliases: error in manpage for "newaliases"

On Sun, Aug 14, 2005 at 09:11:13AM +0200, root wrote: > In the manpage for newaliases it sais "This is a simple shell script > calling /usr/lib/sendmail with the -bi option" > When I look into `which newaliases` it calls /usr/sbin/sendmail instead > of /usr/lib/sendmail. Could maybe get correct

Bug#130902: patch for chimera2 png segfault

Jeremie Koenig wrote: The attached patch fixes the random segfaults from chimera when loading PNG files. The libpng interface used by image/png.c was deprecated, I updated it to the newer one. Thankyou. Your patch looks good (though I've never used libpng so I'll take your word for it that w

Bug#318725: libpcre3-dev: Cannot be installed (wrong dependency)

Helge Kreutzmann wrote: The following packages have unmet dependencies: libpcre3-dev: Depends: libpcre3 (= 4.5-1.2) but 5.0-1 is to be installed E: Broken packages It is built to depend on the same version as the library that's built at the same time. I therefore uploaded library and -dev p

Bug#316553: exim: db_upgrade noisy on lockfile

Justin Pryzby wrote: | db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type | db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid | argument Yes, I know. Oops. Now, those lockfiles are stale; I seem to recall that there's an opened bug about that, too. I

Bug#309606: [ia64] FTBFS: testsuite failure

Luk Claes wrote: Relevant snippet of the build log [1]: ./RunTest: line 111: 25459 Bus error ./pcretest -i $testdata/testinput2 testtry make[1]: *** [runtest] Error 1 I can't reproduce this. I've logged in to merulo.debian.org, got the latest source using apt-get, and built it, without any prob

Bug#307659: exim: /var/lib/dpkg/info/exim.postinst: line 70: db3_upgrade: command not found

severity 307659 important severity 307602 important merge 307659 307602 thanks On Wed, May 04, 2005 at 10:15:11AM -0400, Michael Erana wrote: > need to add libdb3-util to depends list to ensure db3_upgrade will be > there. This will likely affect users moving from woody to sarge and > should be a

Bug#304538: Still broken: 248622 - exim_tidydb failed to open DB file

Shannon Dealy wrote: The bug previously reported in #248622 (caused by incompatible database formats), and closed by this version of exim (3.36-14) still exists in this version. Among the changes noted in the message closing the previous bug report was that the postinst script was calling db3_u

Bug#303684: 'exim' v3.36-15 setup: /var/lib/dpkg/info/exim.postinst: 5: Syntax error: "(" unexpected

A Costa wrote: /var/lib/dpkg/info/exim.postinst: 5: Syntax error: "(" unexpected Line five is function press_return() { which only works on bash (standard POSIX syntax doesn't have the "function". I'm guessing your /bin/sh is not bash? I'll fix this and release another version that should

Bug#302185: breaks noninteractive installations

Henning Glawe wrote: automatic installations fail because read -p is called after displaying the 'exim 3.x is obsolete' message in postinst _without_ checking for DEBIAN_FRONTEND="noninteractive". this makes the whole machine wait during the installation and thus renders the system unusable It

Bug#171774: should I do an NMU?

On Fri, Feb 25, 2005 at 09:06:44AM +0100, Tomas Pospisek wrote: > Since the patch for the security vulnerability has been out since > November 2004 - should I do an NMU with this bugfix only? Please don't. I'd forgotten about that one. I was planning to do a new release soon, I'll include this.

Bug#248622: old DB version bug: need to fix the upgrade procedure

On Fri, Feb 25, 2005 at 08:56:54AM +0100, Tomas Pospisek wrote: > # db3_upgrade retry > # db3_upgrade reject > # db3_upgrade wait-remote_smtp There's not much point. They can just be deleted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troub

Bug#296784: exim: some error messages live infinitely

Al Nikolov wrote: After looking in /var/spool/exim/msglog/ i found that all those aged frozen error messages have identical reason to be frozen: 2005-02-11 18:10:54 [EMAIL PROTECTED] R=lookuphost defer (-1): lowest numbered MX record points to local host *** Frozen That is interesting. Could you

Bug#296784: exim: some error messages live infinitely

Al Nikolov wrote: I believe, that's a bug. In exim.conf i have following directives: timeout_frozen_after = 7d ignore_errmsg_errors_after = 3d and _usually_ they work. But i see some aged messages in the queue (exim -bp): 50d 4.6K 1CmKa0-0005UJ-00 <> *** frozen *** [EMAIL PROTECTED] Ye

Bug#296478: exim: incomplete initialization of groups when running commands in system_aliases

Jerome Alet wrote: but only the primary group for this user is initialized, not the additionnal groups this user is a member of. This is designed behaviour. The documentation for the user option says: If this option is set, it specifies the user under whose uid the delivery process is to be run.

Bug#295713: Exim 3 is obsolete and should be removed from future releases

severity 295713 normal thanks Nigel Metheringham wrote: Future debian releases should either:- * Not provide an exim 3 package and obsolete it so that existing installations are upgraded to exim4. * Very clearly mark the package as deprecated so that users do not continuing

Bug#295287: pcre3: pcre version 5.0 is out

I've put some packages I've just built of pcre 5.0 at http://www.mnb.org.uk/pcre/ If you could test these that would be much appreciated. They seem to work for me, in as much as pcregrep works and it hasn't broken my very simple exim installation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] w

Bug#295287: pcre3: pcre version 5.0 is out

Jay Berkenbilt wrote: I can look into this in more depth to see whether one is required or not. There's a good chance there won't be even though 5.0 supports many more Unicode properties. From a five minute look through the header files, I don't believe that a new soname is required. It seems to

Bug#147564: exim: Exim consistently segfaults on sample message

root wrote: Exim consistently segfaults on the message listed below - errors are also listed. I can't see anything strange about this particular message, but it is crashing exim consistently. I can't see anything strange about it either. Do you have core dumps turned on on your system? If so, a

Bug#291542: rcs: [source] warning: the use of `mktemp' is dangerous, better use `mkstemp'

Jari Aalto wrote: Severity: minor Minor? It's a potential security hole, albeit not a serious one. During compiling from source there are several warnings: warning: the use of `mktemp' is dangerous, better use `mkstemp' This could be fixed upstream. If upstream were developing it at all, it