Thanks! Wondering if I should maybe bring this to the Python team.
On Sat, Aug 24, 2024 at 7:33 AM Alexandre Detiste <
alexandre.deti...@gmail.com> wrote:
> Hi,
>
> The repo for the nmu is here:
>
> https://salsa.debian.org/detiste-guest/click-man/
>
> Please import all 3 branches.
>
gt; On Tue, 19 Oct 2021 10:48:35 -0500 Ryan Pavlik
> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Ryan Pavlik
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> >
> > * Package name: rhsrvany
> > Version : 0.20210127
> >
Thanks for this advice on how to fix it better and unblock migration!
I've pushed an updated revision to both mentors and salsa. I'll reach
out to the science team for review and sponsorship.
On Fri, Dec 2, 2022 at 6:15 AM Graham Inggs wrote:
>
> Source: solvespace
> Version: 3.1+ds1-2
> Severit
Package: ftp.debian.org
Severity: normal
Looks like this is only for a mapping integration (?! Must have been after
my time) using the old libchamplain, should just be able to disable that
build option.
I'm having trouble reproducing this locally in a Docker container
using qemu on sid: it seems to work here. Similarly a Bookworm docker
in qemu into which I installed the sid package also seems to test OK.
(Ran the full autopkgtest suite in it, and while it did appear to fail
an assertion elsewhere
I'm wondering if you still see this bug in any newer stable release:
it looks like we couldn't track down any reproduction of the issue at
the time but 3.0 has a lot of changes since 2.3.
accept an mr to make the copyright file complete again.
Ryan
On Wed, Dec 15, 2021, 5:24 AM Adrian Bunk wrote:
> On Mon, Nov 15, 2021 at 02:53:40PM -0600, Ryan Pavlik wrote:
> > Upstream has fixed this, and I have a package with the latest upstream
> > sources in progress, happy
Oh wow, thanks! I was trying to figure out why it wasn't reproducible even
though it "should have" been. I'll apply this soon.
On Fri, Dec 17, 2021, 6:09 PM Vagrant Cascadian <
vagr...@reproducible-builds.org> wrote:
> Source: meshlab
> Severity: normal
> Tags: patch
> User: reproducible-bui...@l
A new upstream release solves this. A package is currently in progress.
Ryan
OpenPGP_signature
Description: OpenPGP digital signature
Upstream has fixed this, and I have a package with the latest upstream
sources in progress, happy to accept help to put it over the edge.
Ryan
OpenPGP_signature
Description: OpenPGP digital signature
Looks like this is because of a dynamic exception specification, which
is forbidden by C++17. I'll see if upstream has fixed this, and if not,
I'll just modify the packaging to build in C++14 mode.
Ryan
OpenPGP_signature
Description: OpenPGP digital signature
I have figured out a fix (the issue was in detecting what flags were
needed to use std::filesystem, my conclusion is: with gcc11+, tell CMake
C++17 or it will misbehave), and an updated package will be available
soon pending sponsorship.
OpenPGP_signature
Description: OpenPGP digital signature
This has been fixed upstream, and I'm cherry-picking that patch to the
package in lieu of a new upstream release, which we should do sometime
soon here.
OpenPGP_signature
Description: OpenPGP digital signature
I have tried the package here:
https://salsa.debian.org/libvirt-team/virt-v2v and it seems to work
well. In combination with that package, I have filed
https://bugs.debian.org/996850 for the two tools used when processing a
Windows guest: so, probably a "recommends".
OpenPGP_signature
Descriptio
Package: wnpp
Severity: wishlist
Owner: Ryan Pavlik
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: rhsrvany
Version : 0.20210127
Upstream Author : Richard W.M. Jones, Red Hat Inc.
* URL : https://github.com/rwmjones/rhsrvany
* License : GPL-2
This was a floating-point related issue with negligible impact, detected
by pixel-wise compare of an export. It has been fixed upstream and will
be included in the 3.0 stable release:
https://github.com/solvespace/solvespace/pull/987 (Debian Bullseye
currently contains 3.0 RC2)
signature.asc
De
I've been working on a similar bug, possibly the same bug or subset of
it? https://bugs.debian.org/972820 is one of its many names. I had made
a reproducer minimal test case from my own experience, which I posted
here https://salsa.debian.org/rpavlik/gcc-upgrade-testcase and, to get
myself out of
also looks like https://bugs.debian.org/972936 might be related, as
well as the archived bug https://bugs.debian.org/946285
I've collected some mentions of this issue in the readme of
<https://salsa.debian.org/rpavlik/gcc-10-compat>
Thanks for your help!
Ryan
On 12/4/2020 12:27 PM, R
Control: reassign gcc-10 10.2.0-19
I have also experienced this bug, as have a lot of others on the
internet (try searching for "libc6-dev : Breaks: libgcc-8-dev (<
8.4.0-2~) but 8.3.0-6 is to be installed" to see). The bug appears to be
in the new gcc-10 package, not the gcc-8 package it's repla
This has been fixed upstream, so an upcoming update will resolve it.
signature.asc
Description: OpenPGP digital signature
I'd be willing to look into updating this package, as long as the
maintainer has no objection. It would be helpful if the git repo of
packaging were available (see https://bugs.debian.org/928335 ), though
failing that I could just use dgit.
Ryan
Package: src:linux
Version: 5.5.17-1~bpo10+1
Severity: wishlist
Dear Maintainer,
Linux 5.5 includes HWMON support for NVMe drives[1][2] without needing a
superuser
userspace binary like nvme-cli. However, it appears to be off in this build:
$ grep NVME /boot/config-5.5.0-0.bpo.2-amd64
...
# CO
Control: reassign -1 git-buildpackage 0.9.14
Control: retitle -1 gbp-pq should not wrap long subjects
Thanks for following up on this one, that makes sense. In the mean
time, I'll try to keep those subject lines shorter when I control
them. I've reassigned the issue accordingly - not sure how fea
I'm not sure who was in the wrong here, if OpenXR shouldn't have had
that NVX line in the source, or if the removal of that symbol form the
header was not expected. In any case, the error-inducing line
"_(INDIRECT_COMMANDS_LAYOUT_NVX)" can be patched out of
OpenXR-SDK-Source - the next upstream rel
Is there anything I can do to help resolve this issue? It's
(transitively) blocking a package I maintain, so if there's a way to
help fix this I'd be happy to do so.
Ryan Pavlik
signature.asc
Description: OpenPGP digital signature
On Sun, 17 Oct 2010 15:08:56 +0200 Guido =?iso-8859-1?Q?G=FCnther?= <
a...@sigxcpu.org> wrote:
> On Sat, Oct 16, 2010 at 07:26:07PM +0200, Guido Günther wrote:
> > Hi David,
> > sorry for the late reply.
> >
> > On Tue, Oct 05, 2010 at 12:12:17AM -0300, David Bremner wrote:
> > > Package: git-build
not-needed) and saving
again,
the second half of the subject line is now un-indented and placed among the
other headers
(see attached before.patch and after.patch)
I would expect the subject to be persisted unmodified if I don't modify it -
perhaps only
adjusting wrap point or in
between gbp-pq and cme, would have been made, not modifying the line
with the URL.
(My suspicion is that it parsed the https: as a RFC882 header name, so it
formatted
that "field" with a space between the header/field name and the "contents".)
Thank you,
Ryan Pavlik
-- System
Package: mu-editor
Version: 1.1.0~alpha2+dfsg-0.1
Severity: wishlist
Tags: patch
Dear Maintainer,
It would be good to get the alpha version of mu-editor in Debian, since the
existing version
has some issues in my experience accessing (at least newer) Adafruit devices
with
CircuitPython (blank R
Package: libopenhmd0
Severity: wishlist
Dear Maintainer,
In order for OpenHMD to access the input devices it's designed to use,
permissions or udev rules are needed.
Currently, the package does not provide any, as upstream only provides
instructions
for making your own.
I have recently filed a
Package: wnpp
Severity: wishlist
Owner: Ryan Pavlik
* Package name: xr-hardware
Version : 0.2.1
Upstream Author : Ryan Pavlik
* URL : https://gitlab.freedesktop.org/monado/utilities/xr-hardware
* License : BSL-1.0
Programming Lang: udev rules, generated by
Package: wnpp
Severity: wishlist
Owner: Ryan Pavlik
* Package name: monado
Version : 0.1.0
Upstream Author : Jakob Bornecrantz
* URL : https://gitlab.freedesktop.org/monado/monado
* License : BSL-1.0, some parts Apache-2.0
Programming Lang: Primarily C
On 3/30/20 4:21 PM, Antonio Terceiro wrote:
> Control: tag -1 + patch
>
> On Mon, Mar 30, 2020 at 05:45:33PM -0300, Antonio Terceiro wrote:
>> Package: terminator
>> Version: 1.91-4
>> Severity: normal
>>
>> I just installed terminator. All the documentation I found, and the
>> preferences dialo
NOTE:
This is an updated upstream version: the pypi package now includes the
unit tests, so they're included both in the build process and as
autopkgtests, in addition to the other upstream changes.
Dear mentors,
I am looking for a sponsor for my package "click-man"
* Package name: click-m
On 3/26/20 11:58 AM, gregor herrmann wrote:
> On Thu, 26 Mar 2020 11:23:23 -0500, Ryan Pavlik wrote:
>
>> OK, I found lintian 2.55.0~bpo10+1 on snapshot.d.o, and cme edit dpkg
>> works fine there. So, some change between lintian 2.55.0~bpo10+1 and
>> 2.57.0~bpo
control: affects -1 lintian
OK, I found lintian 2.55.0~bpo10+1 on snapshot.d.o, and cme edit dpkg
works fine there. So, some change between lintian 2.55.0~bpo10+1 and
2.57.0~bpo10+1 broke cme edit dpkg.
Ryan
Package: libconfig-model-dpkg-perl
Version: 2.122
Severity: important
Dear Maintainer,
Recently, I have had cme edit dpkg stop working on my Buster system, which is
mostly clean,
with some use of buster-backports. This seemed to occur in conjunction with an
update in which
lintian was upgraded
Package: src:meshlab
Version: 2020.02+git200217-1
Severity: serious
Justification: Policy 2.3
Tags: pending
Owner: ryan.pav...@gmail.com
Dear Maintainer,
The recently uploaded 2020.02+git200217-1 package has some DFSG
violations - some of which are file-exclusions that got lost in the new
package
Control: tags -1 + fixed-upstream pending
Looks like this is fixed upstream in the newest release, which I have
sitting on Mentors ready for review and upload:
https://mentors.debian.net/package/meshlab
On Sun, 7 Jan 2018 19:52:55 + Ian Jackson
wrote:
> Package: meshlab
> Version: 1.3.2+dfs
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
Dear mentors,
I am looking for a sponsor for my package "click-man"
* Package name: click-man
Version : 0.3.0-1
Upstream Author : Timo Furrer
* URL : https://github.
Back in the day I was closely involved with AbiWord, including packaging
on Debian and Ubuntu. Since it's not a very fast-moving project right
now, I think I can safely offer to help keep it alive in Debian.
Ryan
Ah, I figured out the conflict.
Qt5 on armel/armhf uses OpenGL ES, not OpenGL full (desktop). So, using
full OpenGL causes conflicts. My most recent changes (pushed to salsa,
waiting on my cowbuilder before pushing to mentors) change the
dependency in control to libqt5opengl5-desktop-dev, so that
I have a work in progress package here that will resolve this issue.
The referenced RFP bugs have been closed for lack of activity. My most
recent work resolves this bug differently, by simply not exposing the
"broken" exporter. I've listed this bug in the changelog so it will be
closed once that package enters the archives.
OK, I got a chance to build aarch64 and it does build there.
Unfortunately I hit a more fundamental error with armhf, that it has
type mismatches when trying to use GLEW. Not sure if this is intrinsic
or if it can be solved: the last version that was in Debian was a long
time ago...
This error re
On 3/4/20 1:12 PM, Moritz Mühlenhoff wrote:
> On Tue, Mar 03, 2020 at 05:56:18PM -0600, Ryan Pavlik wrote:
>> armel and armhf: these platforms only have OpenGL-ES, not desktop
>> OpenGL, so the correct thing to do is to disable this package on those
>> platforms. Is there a
I now have a package for this tool up on mentors, seeking sponsorship.
(And yes, the package builds its own man pages with itself.)
https://mentors.debian.net/package/click-man
I have the source maintained on salsa at
https://salsa.debian.org/rpavlik-guest/click-man
Let me know if there are chan
arm64 and s390x (and maybe ppc64el?) are all an issue with signed char
conversions. I have a patch to fix that in my git repo, along with other
fixes that effectively block further usage (dfsg, etc):
https://salsa.debian.org/rpavlik-guest/meshlab/-/commit/2631636f29b7375a1d7977a1484b826db55ba153
a
This blocks updating policy version past 4.0.1 since 4.1.0 mandates that
-e works in this way:
https://www.debian.org/doc/debian-policy/ch-customized-programs.html#packages-providing-a-terminal-emulator
(This is the only item I've noticed in the upgrading checklist up
through 4.5.0)
signature
I am also an active user. I have a few hours a week of "upstream" time
at work that I could look at this package during.
Ryan
signature.asc
Description: OpenPGP digital signature
I created a package for this as a part of packaging a Click-based tool
where, as you described, I didn't like the manual options for manpage
creation. (Started with py2dsp output but have made it better than
that.) I'd be happy to collaborate with you on it.
Ryan
On Sat, 09 Mar 2019 16:05:08 +0
Package: g++-mingw-w64-x86-64
Version: 8.3.0-6+21.3~deb10u1
Severity: normal
Tags: patch
Dear Maintainer,
I had some issues linking an application being built as C++14 and using the
std::experimental::filesystem -
it mentioned unresolved "fs_err_concat" symbols. When researching it, I
discovere
Package: meshlab
Severity: important
Tags: patch
Dear Maintainer,
I saw that meshlab was removed due to build issues. I have done some work on it
upstream recently, including incorporating patches/functionality from the
debian package. It now builds easily with fewer patches - and my PR to add a
helper programs to maintain Debian
ii ubuntu-dev-to 0.99.1 useful tools for Ubuntu developers
ii w3m 0.5.2-2.1ubuntu1.2 WWW browsable pager with excellent
-- no debconf information
>From 041f90cb124128cf74dc7db90185ffd36ec1cd0f Mon Sep 17
55 matches
Mail list logo
