Package: wnpp
Severity: wishlist
Owner: Peter Pentchev
X-Debbugs-Cc: debian-devel@lists.debian.org, r...@debian.org,
team+pkg-...@tracker.debian.org
* Package name: deltarpm
Version : 3.6.3
Upstream Author : Michael Schroeder
* URL : https://github.com/rpm-software-m
Package: wnpp
Severity: wishlist
Owner: Diane Trout
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: sphinx-remote-toctree
Version : 0.0.3
Upstream Author : Chris Holdgraf
* URL : https://github.com/executablebooks/sphinx-remove-toctrees
* License :
Package: wnpp
Severity: wishlist
Owner: Doug Torrance
X-Debbugs-Cc: debian-devel@lists.debian.org, dtorra...@debian.org
* Package name: r-cran-m2r
Version : 1.0.2
Upstream Author : David Kahle
* URL : https://github.com/coneill-math/m2r
* License : GPL
Program
On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
Exactly that.
I'd suggest anyone who's interested in seeing Chromium supported to first
update it in unstable (and then work towards updated in bullseye-security).
I started doing just th
On Sun, 12 Dec 2021 at 12:56:42 -0600, Steven Robbins wrote:
> Can you (or anyone) confirm whether the Debian i386 build SHOULD or SHOULD
> NOT
> enable SSE of any flavour?
Our current i386 baseline does not have SSE, so i386 packages should
not enable SSE in general:
"i686 since Debian 9 'stre
On 12.12.21 19:22, Jeremy Bicha wrote:
Therefore, it seems pretty easy to me for you to just bump the
upstream version in its next release from 0.9.0 to 13.11.0 (or 14.0 or
14.9.0 or whatever higher number). Blame Ubuntu in your release notes.
That seems like the least complex way to handle thi
Hi Steve,
* Steven Robbins [2021-12-12 12:56]:
Can you (or anyone) confirm whether the Debian i386 build SHOULD or SHOULD NOT
enable SSE of any flavour? I've googled numerous times but can't seem to find
this kind of detailed port information.
https://wiki.debian.org/ArchitectureSpecificsMemo
Thank you Andrey!
> For example, in this case it's not about compilation flags because the
> relevant code uses SSE2 explictly when USE_SSE2_32IMPL is set. I haven't
> checked how is it set but the configure step output suggests it checks the
> hardware support on the build machine, which must not
On Sun, Dec 12, 2021 at 8:47 AM Mike Gabriel wrote:
> Yeah, I am aware of that possibility. However, I don't really feel
> like inheriting the versioning from the Ubuntu package (year.month) in
> the Debian package and be forced to carry that one along with me in
> the future forever...
>
> I'd ra
Hi Jonas, hi all,
On So 12 Dez 2021 16:13:33 CET, Jonas Smedegaard wrote:
Quoting Mike Gabriel (2021-12-12 14:47:26)
HI Jonas,
On So 12 Dez 2021 14:26:35 CET, Jonas Smedegaard wrote:
> Hi Mike,
>
> Quoting Mike Gabriel (2021-12-12 13:53:55)
>> the src:package ayatana-indicator-messages con
Quoting Mike Gabriel (2021-12-12 14:47:26)
> HI Jonas,
>
> On So 12 Dez 2021 14:26:35 CET, Jonas Smedegaard wrote:
>
> > Hi Mike,
> >
> > Quoting Mike Gabriel (2021-12-12 13:53:55)
> >> the src:package ayatana-indicator-messages contains bin:pkgs
> >> (libmessagingmenu*) that have the same name
HI Jonas,
On So 12 Dez 2021 14:26:35 CET, Jonas Smedegaard wrote:
Hi Mike,
Quoting Mike Gabriel (2021-12-12 13:53:55)
the src:package ayatana-indicator-messages contains bin:pkgs
(libmessagingmenu*) that have the same name as Ubuntu's src:pkg
indicator-messages.
The src:pkg indicator-messag
Hi Mike,
Quoting Mike Gabriel (2021-12-12 13:53:55)
> the src:package ayatana-indicator-messages contains bin:pkgs
> (libmessagingmenu*) that have the same name as Ubuntu's src:pkg
> indicator-messages.
>
> The src:pkg indicator-messages has a higher version number than
> ayatana-indicator-mes
Hi all,
the src:package ayatana-indicator-messages contains bin:pkgs
(libmessagingmenu*) that have the same name as Ubuntu's src:pkg
indicator-messages.
The src:pkg indicator-messages has a higher version number than
ayatana-indicator-messages and thus the latter fails to be imported
in
14 matches
Mail list logo
