in the process.
Additionally, you so *don't*. The config file is a config file enough
that it's only removed on purge not remove (not that the remove is
necessary as you claim).
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raul Miller <[EMAIL PROTECTED]> writes:
> Looks like libgdbmg1 should be required, [ ... ]
No; perl shouldn't depend on libgdbmg1. libgdbmg1 is obsolete and
deprecated. I asked the perl maintainer if he could fix this back in
March or so, apparently it hasn't happened.
ade process issues ominous sounding threats.
>
> This situation is better avoided.
``This situation'' is similar to that of almost all libc5->libc6
shared library upgrades. Avoiding it might be non-trivial.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email t
very silly to release hamm with 0.99.xx and not
1.0.0 (0.99.xx has been bug-fixes only for a while and 1.0.0 is
too).
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
not a good reason. Certainly nothing like a good enough
reason to justify us shipping with an *out of date* pre-release.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> reason to justify us shipping with an *out of date* pre-release.
>
> Sorry?
>
> What I tried to say is that latest JDK does not work with glibc from hamm,
> but DOES work with (more recent) glibc from slink. And I proposed to move
> slink glibc into frozen (hamm).
*blink*..
"Darren/Torin/Who Ever..." <[EMAIL PROTECTED]> writes:
> Raul Miller, in an immanent manifestation of deity, wrote:
> > James Troup <[EMAIL PROTECTED]> wrote:
> > > No; perl shouldn't depend on libgdbmg1. libgdbmg1 is obsolete
> > > and de
Raul Miller <[EMAIL PROTECTED]> writes:
> James Troup <[EMAIL PROTECTED]> wrote:
>
> > I don't know perl, and am only going on what Ray has been telling
> > me. It was my understanding that perl could be made to
> > dynamically load it's gdbm p
e different issues, and can be done on radically separate and
different machines.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
#x27; will let you look inside of and install `.deb' files also.
Gosh, what a revolutionary concept. I did hear about something else
that could do that though. What was it? dekg? dplg? I can't
remember.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
/toy with users?
> The problem is that the _preinst_ might use the programs useradd and
> groupadd. These are not in the base system nor essential.
No, they _are_ part of the base system and they _are_ Priority:
Required.
> Is there another way to solve this?
Possibly not.
--
J
base system for the minimal or non-existent
``gain'' it offers and b) *not* a suitable replacement for what has
been proposed to be removed.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
row? Your FAQ becomes worse than useless to
anyone who wants to carry on the fine job you've been doing. Legally,
they have to start from scratch. That's a losing situation.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
p Paul. You have zero idea how well (or otherwise) I know
mc, so please stop the FUD. Adding a smiley does not justify
childishness.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
has to be turned back on by
default before release and that after that, although still a bug, this
becomes less than release-critical.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
week (I hope no more),
and will be completely without computer (never mind net) access. If
any severe bugs in my packages turn up, please feel free to do NMUs.
--
James - hoping /var/mail/ survives on comp.brad.ac.uk :|
~Yawn And Walk North~ http://yawn.nocrew.org/
ofs
and mkhybrid-1.12a4.0 is available from ftp://ftp.ge.ucl.ac.uk/pub/mkhfs
James Pearson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in slink.
Of course, I agree, but my point was that gdbm *Shouldn't* be required
and although it will need to be made so in hamm as a kludge, I tried
to get this fixed properly back in March.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNS
Francesco Tapparo <[EMAIL PROTECTED]> writes:
> So my question is: must I add Depends: debianutils (>> 1.6), or I'm
> guaranteed that will be upgraded the essential packages first? Is
> this bug-fix worthy of an hamm release?
Yes, no, IMO no.
--
, gnuplot doesn't break anything. We would be violating the
GNU GPL by distributing a gnuplot linked with readline but gnuplot is
not per se breaking the GNU GPL.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n
contrib?\end{just checking}
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
still?).
No. elvis is non-free; elvis-tiny is not. Look at the copyright
files. AIUI elvis-tiny is a much earlier version of elvis which was
still free. Or something. Of course the copyright files may be
``inaccurate'', I'm disillusioned enough to r
of the funcationality of JDE
> would be lost if jdk1.1-dev wouldn't be installed.
I agree, as I say, I was just checking.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Florian Hinzmann <[EMAIL PROTECTED]> writes:
> Later someone will reassign that bug to the correct package, but the
> maintainer of that package won't get any mail.
That's simply not true.
--
James
~Yawn And Walk North~ http://yawn
the AOL, but...) Well said; I wish people would get over
their epoch-phobia already.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Dale Scheetz <[EMAIL PROTECTED]> writes:
> On 23 Jun 1998, James Troup wrote:
>
> > (Sorry for the AOL, but...) Well said; I wish people would get
> > over their epoch-phobia already.
>
> And I wish people would stop suggesting a poor solution.
How is it a ``poo
Or anyone using epochs is opting for the ``poor'' solution?
[1] 2.9.1-0.1.this.is.really.2.8.1 anyone?
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
s postinst before foo's. Try it
and see.
--
James
~Yawn And Walk North~ http://yawn.nocrew.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raul Miller <[EMAIL PROTECTED]> writes:
> James Troup <[EMAIL PROTECTED]> wrote:
> > Eh? Almost any version-number problem can be solved by a version
> > suffix[1].
>
> Not where 1.0 follows 3.14, for example.
You clearly can, as I demonstrated in my foo
Michael Dietrich <[EMAIL PROTECTED]> writes:
> but i didn't find SOURCE OF WHIPTAIL at all, what's going on there??
You didn't look very hard.
Package: whiptail
Version: 0.21-8
[...]
source: newt
--
James
~Yawn And Walk North~
updated for glibc, reported by Herbert Xu
<[EMAIL PROTECTED]>. [#13140]
* debian/control (dpkg-dev): depend on perl as POSIX (not a part of
perl-base) is needed by most of the perl dpkg-* scripts, noticed by
Joel Klecker <[EMAIL PROTECTED]>. [#22115]
-- James Troup
r can be counted on the fingers of a very mutilated hand.
--
James
27;ve ``proved'' absolutely nothing about Debian's rejection policy.
--
James
Kikutani Makoto <[EMAIL PROTECTED]> writes:
> Do you accept a passport as the above formal documents ?
Yes. [Though if there is any opportunity to meet another developer in
real life and cross sign each others keys, this is the preferred
method, where it's viable.]
--
James
Joseph Carter <[EMAIL PROTECTED]> writes:
> Old/slow/lomem machines can't properly compile X or Mozilla anyway.
Bzzt. I've compiled xfree86 for Debian/m68k on a 386/25 equivalent
with only 14Mb (don't ask) of memory several times. Took 5 days,
like, but it compiled ``properly''.
--
James
Joseph Carter <[EMAIL PROTECTED]> writes in gratuitous QP:
> On Sun, Oct 04, 1998 at 12:15:40PM +0100, James Troup wrote:
> > > Old/slow/lomem machines can't properly compile X or Mozilla anyway.
> >
> > Bzzt. I've compiled xfree86 for Debian/m68k on a 386
a [EMAIL PROTECTED] with the mother of all brain dead
motherboard designs which slows it down by a factor of 2 or so. As
you can see, I'm not overly proud of the machine, quite the opposite
in fact.
--
James
Russell Coker <[EMAIL PROTECTED]> writes:
> What about pop stars? We could have Debian sporty, Debian Ginger, Debian
> Posh...
*bang*
--
James
<[EMAIL PROTECTED]>(James A. Treacy) writes:
> Should apt have to download the dsc file for a package before it
> knows what the source files are?
Why on earth not? If it's going to download the source, the .dsc file
is part of the source and has to be downloaded anyway.
&
[ Please don't Cc me on replies to a public mailing list ]
<[EMAIL PROTECTED]> (James A. Treacy) writes:
> > <[EMAIL PROTECTED]>(James A. Treacy) writes:
> >
> > > Should apt have to download the dsc file for a package before it
> > > knows what
s:Depends=libc6, libc6 (>= 2.0.7u)
>^ ^
Look at fakeroot's shlibs file. This is not a bug (or certainly not
the one you're claiming it is).
--
James
[EMAIL PROTECTED] (Adam P. Harris) writes:
> Roberto Lumbreras <[EMAIL PROTECTED]> writes:
> > On Friday, October 9 1998, at 21:19:38, James Troup wrote:
> > : Look at fakeroot's shlibs file. This is not a bug (or certainly not
> > : the one you're claiming
g -m with dpkg-genchanges) should
> be discussed on -devel.
Blah; debian-devel has _way_ too much traffic already, so much so that
several porters don't read it.
--
James
too and mass cross-posting is
offensive.
--
James
just fine and
you haven't been bothered by it so far (afaik).
--
James - [Actually glad cookie-monster is in .nl and not .de and thus
free from MTA-prejudiced admins]
509e50aba59a6eebbe14b 3880 shells optional es_0.90beta1-3.diff.gz
> 9430833e4c1353fb17206394d6e87423 97390 shells optional
> es_0.90beta1-3_i386.deb
Ehm, no. I've removed this package from Incoming. It's customary to
contact the maintainer of a package before taking it over; package
hijacking is not appreciated.
--
James
Joey Hess <[EMAIL PROTECTED]> writes:
> [ Moving this to debian-devel, discussion doesn't belong in the bug report. ]
[ Killed the Cc: line. ]
> James Troup wrote:
> > There is no i386 port in as much as i386 maintainers 99.5% of the time
> > _don't_ compi
Joey Hess <[EMAIL PROTECTED]> writes:
> James Troup wrote:
> > They don't compile from freshly unpacked source.
>
> How odd. Other maintainer must work substantially differently than I, then.
If you're building foobar 1.1-3, do you really recompile from a
fr
Buddha Buck <[EMAIL PROTECTED]> writes:
> James Troup said:
> > Joey Hess <[EMAIL PROTECTED]> writes:
> >
> > > James Troup wrote:
> > > Why does a binary-only NMU give you the right to skip waiting, while
> > > a normal NMU does not? Why a
get over this GPL obsession, there is *plenty* of
software in main _not_ covered by the GPL.
--
James
[Want to know how Debian violates the GPL all the time? Check how
many GPLed packages in Debian have modifications yet don't obey 2(a).]
Dave Swegen <[EMAIL PROTECTED]> writes:
> Out of curiosity, which version of PGP is the debian de facto standard.
> I'm currently using v5, but I've seen a number of people use 2.6...
2.x; we don't accept later stuff.
--
James
all ?
That would be a big fat no. (1) is patently untrue, (2) is not
happening any time ever and (4) is, with all due respect, stupid
beyond belief.
--
James
Joey Hess <[EMAIL PROTECTED]> writes:
> Hartmut Koptein wrote:
> > 1. binary-only NMUs breaks policity
>
> Probably.
Wrong.
--
James
binary-only NMUs (which you seem to want to
ignore) [see my bash example in <[EMAIL PROTECTED]>].
> I think I could dig up complaints form *you* saying that.
That would be a cunning trick.
--
James
Joey Hess <[EMAIL PROTECTED]> writes:
> Each day you autobuild say, 30 packages from Incoming.
Building (especially auto-building) packages from Incoming is a bad
idea, please don't encourage it.
--
James
Joey Hess <[EMAIL PROTECTED]> writes:
> James Troup wrote:
>
> > Who said [binary-only NMU's for i386] were bad?
>
> You did.
No, I said binary-only NMUs as a whole were not ideal; I didn't say
anything about binary-only NMU's for i386. Please try to
David Frey <[EMAIL PROTECTED]> writes:
> On Thu, Oct 15, 1998 at 08:23:38PM +0100, James Troup wrote:
> >Dave Swegen <[EMAIL PROTECTED]> writes:
> >> Out of curiosity, which version of PGP is the debian de facto standard.
> >> I'm currently using
Bob Nielsen <[EMAIL PROTECTED]> writes:
> What is the status of gnupg?
Not yet used in Debian.
> Is there a Debian package available?
Yes, on non-US.
--
James
t bothered to think about it very hard.
If it really is a problem nowadays, I could, of course...
[Off the top of my head: enforcing a new numbering policy for bin-only
NMU's (e.g. 3.5-1 -> 3.5-1.0.1 (and not 3.5-1.1)) would solve the
problem and would also solve the problem of bin-only NMU's being
clobbered by source NMU's; I did mean to propose this to debian-policy
several months ago, but apparently I never got round to it]
--
James
#x27;s not PGP5 that Debian has an issue with, it's non-RSA keys.
Not true; gnupg keys are surely not RSA but they're accepted in some
ways (i.e. we have a keyring for them and dpkg-dev supports the use of
gnupg, but dinstall doesn't yet).
RSA keys are actually something we want to get away from.
--
James
Santiago Vila <[EMAIL PROTECTED]> writes:
> Could somebody explain me, why, oh why, do we have to wait more than
> two months for trivial ftp.debian.org bugs to be fixed?
Perhaps because the more you whine about it the more prone we are to
ignore you?
--
James
As Brian has said to Santiago already (those he chooses to ignore it
so he can whine more effectively), we do not need more help, and we
certainly do not want his ``help''.
Personally, I'd like to get on with the slink release and other
things, so please, don't carry this thread on.
--
James
architectures are
screwed.
I've been meaning to mark all problems with building source packages
(that I find on m68k) for frozen as release critical for a long time
actually, I just keep forgetting.
--
James
m Author(s): Colin <[EMAIL PROTECTED]>
Copyright:
GPL. Please see /usr/doc/copyright/GPL for full text.
Dres
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.ioa.com/~dres | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
What we do about the logo (with options a) keep current, b) keep
current for some amount of time, c) get new one in some manner).
Dres
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.ioa.com/~dres | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
Hamish Moffatt <[EMAIL PROTECTED]> writes:
> +case ${host} in
> + *-pc-linux-gnu)
^^
s/pc/*/ (pc==non-i386 unfriendly)
--
James
"Never trust trucks"
"Edward John M. Brocklesby" <[EMAIL PROTECTED]> writes:
> I don't think so - Octopi can't fly!
Someone who obviously hasn't read RFC 1925...
--
James
"Never trust trucks"
Hamish Moffatt <[EMAIL PROTECTED]> writes:
> On Wed, Jan 27, 1999 at 08:29:42PM +0000, James Troup wrote:
> > Hamish Moffatt <[EMAIL PROTECTED]> writes:
> >
> > > +case ${host} in
> > > + *-pc-linux-gnu)
> >^^
> >
> > s/pc/
up, the announcements won't
> > come until the package is installed, which in some cases can be
> > several weeks.
>
> Um, hopefully it isn't several weeks any more now that Richard and
> James are helping with day-to-day work.
It isn't, even when Richard'
autobuilders do it (with a source-only upload)?
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
wasn't a drug dealer. Then they came for the sixth amendment, but I kept
quiet because I wasn't guilty. Finally they came for the first amen
space:]]\((alpha|arm|powerpc|m68k|sparc|hurd-i386)\)
/dev/null
This is more specific, and therefor less likely to catch other mail. (also,
I added hurd-i386 to the list -- forgot that one.)
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
wasn
selete libraries is a Bad Thing when at all
avoidable.
BTW, debian-gtk-gnome@lists.debian.org is the cannonical place to ask
debian-related gtk questions, and it's low-volume now that the Great GNOME
Copy is done. (CCed/Reply-toed there.)
-=- James Mastros
--
First they came for
d significantly decrease the bulk of packages that
need to be upgraed (glibc-doc and libc6-dev especially).
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
wasn't a drug dealer. Then they came for the sixth amendment, but I kept
quiet because I
erstand -- but I assume that they are good). I'd suguest subtracting .01
from the debian-version and concatinating '.slink' to the end (somthing like
1.0-0.99.slink); that seems to be standard pratice.
-=- James Mastros
--
First they came for the fourth amendment, but I s
top1. gnome-utils 0.99.3-1 depends on it -- but gnome-utils 0.99.3-1 is
also obselete, but I cannot find a replacement, even though I have the
replacement installed! Is it still stuck in Incoming?
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
w
to use
them fairly easily, and lintian could allow them trivialy. (I would tend to
say that apt-get source shouldn't use them, as getting the source as a
reference, without wanting to compile it, is probably fairly common.
Anyway, that's a call for apt's maintaner.)
So how does this all
buggy.
A soultion to number 1 that was tossed around included using libtricks to
get a list of files accessed, and is therefor (IIRC) obselete. (And in any
case is prohibitively slow.)
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
wasn't a
lib1g (>= 1:1.1.3)
| Installed-Size: 50
| Maintainer: James Troup <[EMAIL PROTECTED]>
| Description: render images of the earth
| xplanet is similar to xearth, where an image of the earth is rendered
| into the X root window. Both mercator and orthographic projections
| can be displaye
tomers use apt's
slickness, and perhaps they will... and we certianly wouldn't mind.
-=- James Mastros
--
First they came for the fourth amendment, but I said nothing because I
wasn't a drug dealer. Then they came for the sixth amendment, but I kept
quiet because I wasn'
apel xemacs21" after
xemacs is installed.
3) The info pages are a bit messed. (Working on it.)
4) Yes I plan on splitting out the -mulesupport and -basesupport into
separate "packages" (in the xemacs sense), but haven't gotten to it
yet.
I think that's about
done (the configure.in file was modified. Know any
other way to recreate the configure file?).
As it is this is no longer neccessary and will go away (patch upstream
fixes the problem I was having).
At least I did remove the configure file so that the patch wasn't
ungodly large.
Dres
s to create a data package and get a MBF
> after getting a consensus here.
>
> Any volontuers for the packaging ?
It's already packaged:
https://tracker.debian.org/pkg/publicsuffix
Do you have a list of packages which need fixing? Can you add a lintian
check for this?
James
signature.asc
Description: OpenPGP digital signature
e to the visibility aspect of your email. In terms
of visibility, it doesn't matter where the repo is hosted or whether
it's in Salsa's debian org or one's own namespace -- Vcs-Git clearly
tells people where to find it.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
roblem that we have is that it's not possible to upload a package
>> to Debian which does not build any binaries on the release architectures,
>> the archive would be removed from the archive immediately.
>>
>> I assume what we could do is maybe have a package that is built
build any arch:all package.
>
> If you say, that this should not be possible, why did this work for
> consolekit?
Because it's not non-release, it's non-ftp-master, and hurd/kfreebsd are on
ftp-master despite being very non-release.
James
Package: wnpp
Severity: wishlist
Owner: James Clarke
* Package name: git-imerge
Version : 1.1.0
Upstream Author : Michael Haggerty
* URL : https://github.com/mhagger/git-imerge
* License : GPLv2+
Programming Lang: Python
Description : incremental
Hi,
My name is James. I have identified your website as a good fit for our
business.
We would like to work out a deal that enables us to place relevant content on
your site with a Do-Follow Link.
If this is something that you would be interested in please reply to this email
so that we can
-kbsd) or via email.
Thanks for your future porting efforts!
Regards,
James
[0] https://db.debian.org/machines.cgi?host=lemon
[1] https://dsa.debian.org/doc/schroot/
(1) is the only thing I've ever used to look inside a deb(5) file.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
icts with user settings if they prefer
something else.[2]
Another complaint I've heard is how many toolkits we should be
installing in a base system, since adding qt5ct will obviously pull in
Qt 5. We don't want it to be a hard dependency of any GTK-based desktop
either, since that's not really the right place.
[2]: https://github.com/linuxmint/Cinnamon/issues/5440
>
> In general: could we please do something to appearance beyond choosing a
> wallpaper once a release? I'm a code hacker not a theme maker, so I see
> this only once it gets in my way -- but text readability does matter.
>
> (Discussing before filing bugs.)
>
>
> Meow!
>
Best,
James
signature.asc
Description: OpenPGP digital signature
On 2019-06-07 12:09 p.m., Adam Borowski wrote:
> On Fri, Jun 07, 2019 at 11:24:03AM -0700, James Lu wrote:
>> As far as I know, Debian mostly uses default upstream desktop defaults,
>> so these concerns apply there too. Evidently some DEs (Plasma, Cinnamon)
>> focus on look
Package: wnpp
Severity: wishlist
Owner: James Valleroy
* Package name: erlang-mimerl
Version : 1.2.0
Upstream Author : Benoit Chesneau
* URL : https://github.com/benoitc/mimerl
* License : Expat
Programming Lang: Erlang
Description : Erlang library to
wraps
around imagemagick, icotools, and msitools to do the bulk of its work,
so it be one of its subprocesses too.)
[1]: https://github.com/exe-thumbnailer/exe-thumbnailer/issues/13
Best,
James
signature.asc
Description: OpenPGP digital signature
security fix. Rather than
having distinct patches for most of those commits, they were mostly
munged into a single "debcherry fixup" patch.
[0]: https://sources.debian.org/src/neovim/0.3.4-3/debian/patches/
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Package: wnpp
Severity: wishlist
Owner: James McCoy
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: tree-sitter-lua
Version : 0.0.14
Upstream Contact: Munif Tanjim
* URL : https://github.com/MunifTanjim/tree-sitter-lua
* License : MIT
Oskari Pirhonen writes:
> [[PGP Signed Part:Undecided]]
> On Tue, Apr 18, 2023 at 16:07:45 +0200, Florian Weimer wrote:
>> Gentoo has been fixing various packages for building with Clang, which
>> covers a superset of the issues that need to be addressed:
>>
>> [TRACKER] Support LLVM/Clang as
ugs with 'Breaks+Replaces' in the title)
https://udd.debian.org/bugs.cgi?release=na&merged=ign&keypackages=only&fnewer=only&fnewerval=7&flastmodval=7&rc=1&cpopcon=1&chints=1&ckeypackage=1&ctags=1&cdeferred=1&caffected=1&sortby=last_modified&sorto=asc&format=html#results
Thanks,
James
On Fri, 28 Apr 2023 at 17:52, Jochen Sprickerhof wrote:
>
> Hi James,
>
> * James Addison [2023-04-28 14:54]:
> >To make sure we don't miss any packages out accidentally: could you
> >confirm that those hundred-or-so errors occurred from 27 or so
> >distinct p
On Tue, 16 May 2023 at 04:22, Russ Allbery wrote:
>
> > It did look like a veto to me. More importantly, isn't relying on
> > passersby to spot alleged harmful changes dangerous, especially for
> > undocumented, uncodified and untested use cases, like unspecified and
> > vague cross-compatibility
On Fri, 19 May 2023 at 12:42, Steve McIntyre wrote:
>
> I'm planning on stopping publishing installer images for i386
> soon. Why? We should be strongly encouraging users to move away from
> it as a main architecture. If they're still installing i386 on 64-bit
> hardware, then that's a horrible mi
501 - 600 of 1134 matches
Mail list logo
