Package: wnpp
Severity: wishlist
Owner: Abraham Raji
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name : node-ist
Version : 1.0.0
Upstream Author : 2016 by Marijn Haverbeke
* URL : https://github.com/marijnh/ist#readme
* License : Expat
Programming L
On 11.12.20 10:08, Timo Aaltonen wrote:
I noticed that crypto-policies is packaged, but not really used
anywhere. Would it be worthwhile to make it the official way to
configure the system-wide crypto policy as it was implemented in Fedora
[1]? This has been briefly mentioned before at least i
❦ 11 décembre 2020 20:36 -05, Mark Pearson:
>> They seem to say future releases will be tagged. So, I think you should
>> use in gbp.conf:
>>
>> upstream-tag = v%(version%~%-)s
>> pristine-tar = False
>>
>> No need for upstream-branch since you won't use "gbp import-orig" as the
>> origin lives
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name : node-route-recognizer
Version : 0.3.4
Upstream Author : Yehuda Katz
* URL : https://github.com/tildeio/route-recognizer
* License : Expat
Programming Lang: JavaScript
Descripti
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name : node-miragejs
Version : 0.1.41
Upstream Author : Sam Selikoff
* URL : https://github.com/miragejs/miragejs
* License : Expat
Programming Lang: JavaScript
Description : client-s
On Wed, 2020-12-09 at 23:12 +0500, Andrey Rahmatullin wrote:
> On Wed, Dec 09, 2020 at 12:52:30PM -0500, Calum McConnell wrote:
> > Hi all,
> > I just wanted to note the breakage, and ask for an NMU. I have
> > prepared
> > and uploaded a patch, both to Salsa and to the BTS, and it has been a
> >
On Wed, Dec 09, 2020 at 04:25:54PM +, Stephan Lachnit wrote:
> Hi all,
>
> maybe you already have heard it, CentOS is basically dead now. It used to be
> an exact RHEL clone, but now it's kind of an RHEL beta [1].
>
> Now what does that have to do with Debian?
>
> When we look into why peop
On 12/12/2020 05:48, Vincent Bernat wrote:
> ❦ 11 décembre 2020 20:36 -05, Mark Pearson:
>
> You need to use "~rc" instead of "-rc", otherwise, users won't be able
> to upgrade to "1.6" when they have "1.6-rc3" installed.
>
Ooops - my bad. I started wearing glasses this year...but don't always
p
On Tue, Dec 08, 2020 at 05:46:26PM +, Simon McVittie wrote:
>...
> I think it's necessary to consider what the purpose of the i386 port is,
> and set expectations and an appropriate baseline based on that.
>
> I see two possible use-cases for i386:
>
> 1. It's a compatibility layer for legacy
Hi,
sorry for the late reply and thanks a lot Graham for pinging me
directly. I didn't monitor -devel closely lately, but
I am an active porter for the following architecture and I intend
to continue this for the lifetime of the Bullseye release (est. end
of 2024):
For ppc64el, I
- test most pack
Am Sa, Dez 12, 2020 at 18:09:02 +0200 schrieb Adrian Bunk:
4. People who wrongly installed i386 on amd64-capable hardware.
Well, some releases ago befor multi-arch I used to install i386 even on
am64-capable hardware if ram was quite low (=< 8GB) and if the chance
wasn’t that low that you nee
On Wed, 2020-12-02 at 21:02 +0100, Jonas Smedegaard wrote:
> Quoting John Lines (2020-12-02 19:47:02)
> > > Where is the code?
> >
> > Much of the code, which is essentially a set of configuration
> > options
> > is on my test system at present, but I am cleaning it up and
> > migrating
> > it t
Stephan wrote:
>Am Sa, Dez 12, 2020 at 18:09:02 +0200 schrieb Adrian Bunk:
>>4. People who wrongly installed i386 on amd64-capable hardware.
>
>Well, some releases ago befor multi-arch I used to install i386 even on
>am64-capable hardware if ram was quite low (=< 8GB) and if the chance
>wasnât
Quoting John Lines (2020-12-12 20:27:44)
> On Wed, 2020-12-02 at 21:02 +0100, Jonas Smedegaard wrote:
> > Quoting John Lines (2020-12-02 19:47:02)
> > > > Where is the code?
> > >
> > > Much of the code, which is essentially a set of configuration
> > > options is on my test system at present, bu
On Sat, 12 Dec 2020 at 18:09:02 +0200, Adrian Bunk wrote:
> 3. Computers that do support MMX and SSE2, but do not support 64bit.
Right, that's basically the second use-case I mentioned, but moving the
boundary for what we do and don't support to be more modern. We could
put the boundary anywhere w
On 12.12.20 21:53, Jonas Smedegaard wrote:
It was good that you introduced your project here on the d-devel@ list,
but I suspect no all 2500 subscribers want to follow closely your
detailed progress going forward.
I'd prefer if the conversation stayed here. It's not like you are
literaly spam
Then there was the short netbook boom, but AFAIR some early ones
had 64bit CPUs but 32bit-only firmware.
My memory is that at the height of the boom the dominant processors
were the N270 and N280, which are 32-bit only. By the time 64-bit
netbook processors showed up the boom was on the dec
Hi all,
As someone who runs amd64/i386 multiarch, this statement from Adrian:
> i386 hardware is so numerous and widely spread, that every tiny fraction
> of i386 users might be more users than half of our release architectures
> combined. It is not even clear whether this is just an exaggeration
18 matches
Mail list logo
