Package: wnpp
Severity: wishlist
Owner: Marco Trevisan (Treviño)
X-Debbugs-Cc: debian-de...@lists.debian.org, ma...@ubuntu.com
* Package name: joycond
Version : 0.1.0
Upstream Contact: Daniel Ogorchock
* URL : https://github.com/DanielOgorchock/joycond
* License
Oh, actually an even more conservative approach can be by also honoring
the DEB_PYTHON_INSTALL_LAYOUT env variable, because if that is set it
should have the priority so that `lib/python3/dist-packages` is used
instead of `lib/python3.XX/site-packages`
setuptools-support-explicit-setup-install-v2.
Control: tags 1071601 patch
Adding a patch that fixes this issue by using the `posix_prefix` schema
when the install prefix is explicitly requested
setuptools-support-explicit-setup-install.patch
Description: Binary data
Package: python3-setuptools
Version: 68.1.2-2
Severity: important
X-Debbugs-Cc: none, ma...@ubuntu.com
Dear Maintainer,
In a simple distutils project:
$ cat hello
#!/usr/bin/env python3 print("Hello world")
$ cat setup.py
from distutils.core import setup
setup(name='hello', scripts=['hello'])
It's worth mentioning that using ${FOO_INSTALL_PATH} instead works, but
I feel it would be better to also support debhelper's ${env:VARIABLE}
format as it's a bit safer.
I'm unsure if that would break further debhelper substitutions, but I
feel that some cases like this could be handled better to
Package: dh-exec
Version: 0.27
Severity: normal
X-Debbugs-Cc: ma...@ubuntu.com
Dear Maintainer,
When using dh-exec to rename a file using a path provided as variable in
debian/rules such as:
usr/bin/foo-bin => ${env:FOO_INSTALL_PATH}/foo
Does not work and I get this failure:
with FOO_INSTALL
Package: wnpp
Severity: wishlist
Owner: Marco Trevisan (Treviño)
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: node-long
Version : 5.2.3
Upstream Author : Daniel Wirtz
* URL : https://github.com/dcodeIO/long.js#readme
* License : Apache-2.0
Package: node-babel7
Version: 7.20.15+ds1+~cs214.269.168-6
I'm trying to use a project that uses babel, importing it as a module as
stated on babel docs [1]:
However, when loading something as simple as:
❯ cat /tmp/foo.mjs
import { transform } from "@babel/core";
console.log(transform)
❯ node
Oh, yes... So I agree that seems to be a problem.
We should probably try to run the tests alone to figure out which ones
are causing the issue.
Hi,
On nov 21 2022, at 1:51 pm, Santiago Vila wrote:
> El 21/11/22 a las 11:20, Simon McVittie escribió:
>> In case there's a kernel difference, I've just tried it in a bookworm
>> VM containing bookworm's sbuild and schroot, again with 2G of RAM. That
>> was also successful.
>
> The package b
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93821
Upstream commit fixing this is
https://gcc.gnu.org/git/?p=gcc.git;a=commit;f=libcpp/init.c;h=445430e16bd08ade34637d2346ded40dd49de508
Package: g++
Version: 4:10.2.1-1
In bullseye:
$ echo | g++ -dM -E -x c++ -std=c++20 - |grep _cplusplus
#define __cplusplus 201709L
It should instead be:
#define __cplusplus 202002L
Ok,
That's fixed in 0.8.1 now, please can you handle the debian side?
Thanks
On lug 17 2022, at 2:51 pm, Jeremy Bicha wrote:
> On Sun, Jul 17, 2022 at 2:49 PM Marco Trevisan
> wrote:
>> Mmh, there are no ABI/API breaks afaik, so there was no need to change
>> package n
Mmh, there are no ABI/API breaks afaik, so there was no need to change
package name
On lug 16 2022, at 11:11 am, Jeremy Bicha wrote:
Control: reassign -1 src:libnotify
Control: severity -1 serious
Control: affects -1 src:gnome-tweaks src:comfy src:gnome-gmail src:isenkram
On Sat, Jul 16, 2022 a
While specific boolean typed hints can't be created, transient
hint can be set with
notify-send 'Transient test' 'Yeppp' --hint=int:transient:1
Source: base-files
Severity: normal
Dear Maintainer,
/etc/os-release can provide a logo name, this is now used by
gnome-control-center to show the logo into the info panel.
If debian would provide its logo name in such file we would be able to
remove the downstream patch that forces the usage of
Hi,
On Tue, 16 Feb 2021 08:47:33 +0200 Martin Paljak
wrote:
> Package: fprintd
> Version: 1.90.9-1
> Severity: important
>
> Dear Maintainer,
>
> After upgrading from version 0.8, flushing print database as requested by
> NEWS,
> I can not enroll fresh prints, due to missing permissions
This is
Hi Jonas,
On mar 18 2021, at 12:05 pm, Jonas Smedegaard wrote:
> Quoting Marco Trevisan (2021-03-18 05:23:41)
> By "launching in a clean schroot" you probably imply that you install
> without respecting recommendations: Debian respects recommendations by
> default, but
Hi Jonas,
> eslint does not depend on but recommends node-text-table, and does so
> because it is needed only in "all but unusual installations" as
> covered by Debian Policy § 7.2:
I'm a bit confused by this as launching in a clean schroot where I've
only eslint installed I get:
eslint -h
Package: eslint
Version: 5.16.0~dfsg-8
Severity: serious
Justification: Missing runtime dependency
Dear Maintainer,
Using eslint from repository fails as per missing dependency on
node-text-table that is used by the default formatter (stylish).
When using other formatters everything works fine.
Package: opensc-pkcs11
Version: 0.21.0-1
Severity: normal
Tags: patch
Dear Maintainer,
When using pkcs11's C_GetSlotList function with the open-pkcs11 module,
the tokenPresent value is ignored, and so slots with no tokenPresent are
returned.
Fixed upstream in https://github.com/OpenSC/OpenSC/pu
Package: libvncserver1
Version: 0.9.13+dfsg-1
Severity: important
Tags: upstream patch
Upstream-Bug: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/45
Dear Maintainer,
When connecting via gnome-remote-desktop using the VNC protocol, there's
a crash:
#0 0x7f39d7c08497 in rfbMake
Il 25/09/20 00:06, Simon McVittie ha scritto:
> Nobody is likely to have tested gjs 1.66 with GNOME 3.36 very thoroughly,
> if at all, so we should not let gjs migrate to testing until we're ready
> for GNOME 3.38 to migrate. I'm opening this RC bug to stop that happening.
For what it worth, I've
02:51:42.0 +0200
@@ -1,3 +1,9 @@
+meson (0.55.0-2.1) UNRELEASED; urgency=medium
+
+ * Fix test with setuptools 49. Closes: #968704
+
+ -- Marco Trevisan (Treviño) Thu, 20 Aug 2020 02:51:42
+0200
+
meson (0.55.0-2) unstable; urgency=medium
* Fix crossbuild test from Gianfranco
(0.55.0-2.1) UNRELEASED; urgency=medium
+
+ * Fix test with setuptools 49. Closes: #966923
+
+ -- Marco Trevisan (Treviño) Thu, 20 Aug 2020 02:51:42
+0200
+
meson (0.55.0-2) unstable; urgency=medium
* Fix crossbuild test from Gianfranco Costamagna. Closes: #963546
diff -Nru meson-0.55.0
Package: meson
Version: 0.53.2-2ubuntu2
Severity: serious
Tags: upstream patch
Justification: FTBFS on amd64
Dear Maintainer,
Building meson in latest experimental fails per:
(experimental-amd64)root@tricky:/build/meson-UGL0Hc/meson-0.55.0#
./run_meson_command_tests.py Meson build system 0.55.0
-1,3 +1,9 @@
+meson (0.55.0-3) UNRELEASED; urgency=medium
+
+ * Don't consider skipped tests as failures. Closes: #966923
+
+ -- Marco Trevisan (Treviño) Thu, 20 Aug 2020 02:51:42
+0200
+
meson (0.55.0-2) unstable; urgency=medium
* Fix crossbuild test from Gianfranco Costamagna. Close
-addLikelySubtags-minimizeSubtags.patch:
+-
+
+ -- Marco Trevisan (Treviño) Tue, 18 Aug 2020 16:47:02
+0200
+
icu (67.1-3) unstable; urgency=medium
* Don't run self-tests parallel until make-dfsg is fixed (closes: #964682).
diff -Nru icu-67.1/debian/patches/Fix-addLikelySu
Source: icu
Version: 67.1-3
Severity: normal
Tags: patch upstream
Dear Maintainer,
Test included in mozjs78 performing local minimization fails when using
system ICU.
In particular, we get these errors:
## non262/Intl/Locale/likely-subtags.js: rc = 3, run time = 0.040125
/<>/js/src/tests/non262
Il 26/02/20 19:13, David Mohammed ha scritto:
> Thx. Has mutter 6 been uploaded yet? If so... experimental or unstable?
Yes, it's in experimental so far.
mutter (3.35.91-1) experimental
Package: git-buildpackage
Using postunpack command is possible to change the content of the source
directories, with something way more advanced than `filters`, however
once the content is modified, it will only be part of the repo, while
it's not possible to repack the resulting orig file.
This
After further investigation this is due to the debian patch no-soname.diff
Any rationale to keep it?
Upstream version just works fine, we can probably fix the issue in other
way with some CMake flags, though.
Package: python3-pypamtest
Version: 1.0.7-2
It's not possible to load the python module as it's not properly linked
with libpamtest.so
$ python3
Python 3.7.5 (default, Oct 15 2019, 16:15:10)
[GCC 9.2.1 20191008] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
m
+
+ * debian/patches/0001-Fix-segfaults-with-readline-8.0.patch:
+- Fix a crash when using readline 8.0 (LP: #1851235)
+
+ -- Marco Trevisan (Treviño) Mon, 04 Nov 2019 16:59:51
+0100
+
tig (2.4.1-1) unstable; urgency=medium
* New upstream version.
diff -Nru tig-2.4.1/debian/patches/0
Package: git-buildpackage
It would be nice to be able to easily see diffs on what patches changed
without having to manually handle this.
Under to hood right now this is possible by:
git checkout -b "temp-branch"
gbp import
git checkout debian/master
gbp import
git diff temp-branch
Or prob
Package: libfprint
Version: 1:0.7.0-1
There's an upstream patch that fixes a potential security hole upstream,
that should be backported:
* https://github.com/freedesktop/libfprint/commit/4bfee76
Package: google-mock
Version: 1.7.0-18092013-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkey
The fix provided for bug #812289 doesn't fix all the cases.
In Ubunutu we use google-mocks in unity and when using gcc-6, things
doesn't work well when mocking some function.
Starti
Package: google-mocks
Version: 1.7.0-18092013-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkey
The fix provided for bug #812289 doesn't fix all the cases.
In Ubunutu we use google-mocks in unity and when using gcc-6, things
doesn't work well when mocking some function.
Start
+0100
@@ -1,3 +1,11 @@
+gtest (1.7.0-5) unstable; urgency=medium
+
+ * patches/test-case-p-unused-dummy-variable-fix.patch:
+- Add GTEST_ATTRIBUTE_UNUSED_ to the dummy variable generated
+ in INSTANTIATE_TEST_CASE_P (LP: #1521177).
+
+ -- Marco Trevisan (Treviño) Mon, 30 Nov 201
39 matches
Mail list logo
