/control, and I would prefer
> not introducing a strict dependency.
>
> Are you fine with closing this bug?
Thanks for the explanation. That makes sense, and I'm fine with closing
this bug.
-Mark
--
Mark J. Nelson
Falmouth University
http://www.kmjn.org
didn't get pulled
in. I see the point about complicating backports though, especially if
xapian's upstream isn't carefully versioning its symbols.
-Mark
--
Mark J. Nelson
Falmouth University
http://www.kmjn.org
Package: maildir-utils
Version: 1.0-6
Severity: normal
Dear Maintainer,
After upgrading maildir-utils from 1.0-5 to 1.0-6, some 'mu' commands stopped
working with the following error message:
mu: symbol lookup error: mu: undefined symbol: _ZN6Xapian4MSetaSEOS0_
Since I suspected this was some
tags 839639 upstream fixed-upstream
forwarded 839639 https://rt.cpan.org/Public/Bug/Display.html?id=112442
thanks
This was fixed upstream in the 0.8.2 release.
--
Mark J. Nelson
The MetaMakers Institute
Falmouth University
http://www.kmjn.org
Ah right, I should've checked there to see if the update was already on
its way. Thanks!
-Mark
--
Mark J. Nelson
MetaMakers Institute, Falmouth University
http://www.kmjn.org
Package: texlive-bibtex-extra
Version: 2016.20160623-1
Severity: normal
Dear Maintainer,
The current version of biblatex-ieee included in the
texlive-bibtex-extra package, version 2016/05/08, appears to be
incompatible with the current versions of biber (2.5) and TeX Live
(2016.20160623). It prod
e magic strings replaced with the two
filenames.)
You could change this to,
diff = diff -u CURRENT2 CURRENT1 | pager
--
Mark J. Nelson
Anadrome Research
http://www.kmjn.org
bly need to set fastcheck to false, which will avoid
accidentally missing such files, at the expense of slower
synchronization. I believe that's uncommon on Unix, which is the reason
for the default.
--
Mark J. Nelson
Anadrome Research
http://www.kmjn.org
fixed 394946 2.48.3-1
fixed 394946 2.40.102-2
thanks
Triaging an old bug:
I believe the maintainers can safely close this bug. The 'merge2' option
was removed almost a decade ago, and the documentation has long since
been updated to remove any lingering confusion.
--
Mark J. Nelso
on depends on:
ii libc6 2.19-22
Versions of packages unison recommends:
ii openssh-client [ssh-client] 1:6.9p1-2
Versions of packages unison suggests:
pn unison-all
-- no debconf information
--
Mark J. Nelson
Anadrome Research
http://www.anadrome.org
Fwiw, the current upstream stable (2.48.3) includes the -repeat watch
functionality. Any plans to package the new version?
-Mark
--
Mark J. Nelson
http://www.kmjn.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
fixed 752622 1:1.19.17+dfsg-1
thanks
I believe that since 1.19.17 has been uploaded, this bug can be closed.
-Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org
tags 728976 + upstream fixed-upstream
thanks
Fwiw, the 1.2.18.1 release is now out, and includes this fix (along with
two other bugfixes).
-Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
2.1.0 was released just today, but that's another matter.
Best regards,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
n SDL), which is currently
not the case. A separate bug, #565595, is already about that subject.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
and id3lib upstreams have been dormant for years, I believe the
Debian maintainer (Stefan Ott) was planning to port id3v2 from id3lib to
taglib, which is maintained upstream and handles charsets in a sane way.
But I'm not sure what the status of the port is.
Best,
Mark
--
Mark J. Nelson
IT
Ran across this bug during some miscellaneous triage of old bugs. Since
all currently supported Debian releases (i.e. squeeze onward) include
0.8.15, imo it can be closed.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
--
To UNSUBSCRIBE, email to debian-bugs
ert) read of the PCCTS grammar under the
hood, it *should* be an easy fix: LPAREN as a semantically meaningful
element is only used in one very specific place in a BibTeX grammar, in
@comments, which shouldn't interfere with permitting parentheses in
entry keys. But I have not tried it.
Be
sired behavior.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
forwarded 549653 https://rt.cpan.org/Public/Bug/Display.html?id=84665
thanks
Correction to my previous message: upstream actually does have a new
maintainer. Therefore I've forwarded this request. Apologies for the
misinformation.
Best,
Mark
--
Mark J. Nelson
IT University of Copen
unsupported kind is requested. Unfortunately, upstream has
been unmaintained since 2008, so the chances of significant new
functionality being added are quite low, unless a new upstream
maintainer is found.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
Recent versions of the package no longer load the color hash from
unicolor.txt. Instead it's specified as a hash literal in
PDF::API2::Resource::Colors. Therefore I believe this bug can be closed.
Best,
Mark
--
Mark J. Nelson
IT University of Copenhagen
http://www.kmjn.org/
22 matches
Mail list logo
