Bug#978594: O: pylint-plugin-utils -- Utilities and helpers for writing Pylint plugins (Python 3)

Package: wnpp Severity: normal X-Debbugs-Cc: aerosti...@debian.org I intend to orphan the pylint-plugin-utils package. I haven't taken any time for my packages this year and don't see this changing anytime soon so retiring. The package description is: This is not a direct Pylint plugin, but

Bug#978593: O: pylint-django -- Pylint plugin for analysing code using Django (Python 3)

Package: wnpp Severity: normal X-Debbugs-Cc: aerosti...@debian.org I intend to orphan the pylint-django package. I didn't take any time for my packages this year and don't see this changing anytime soon, so retiring. The package description is: Features * Prevents warnings about

Bug#978592: O: asciidoc -- Highly configurable text format for writing documentation

Package: wnpp Severity: normal I intend to orphan the asciidoc package. I haven't had taken the time to take care of my packages over the last few months and don't see this changing anytime soon so I'm retiring. The package description is: AsciiDoc is a text document format for writing

Bug#971704: gnome-shell-pomodoro: diff for NMU version 0.18.0-0.1

Thanks for doing that. I unfortunately haven't taken any time for opensource since the beginning of this COVID madness. Feel free to push it now. It's totally fine with me. Thanks Joseph

Bug#960400: gnome-shell-pomodoro: gnome-shell 3.36 compatibility

Thanks for the report Antonio and sorry for the late reply, things have been kind of crazy on my side lately. I'll try to take care of the upgrade over the weekend. Thanks, Joseph

Bug#954780: Duplicate: almost identical content already shipped with vim-runtime

Control: forwarded -1 https://github.com/asciidoc/asciidoc-py3/pull/100 Hi Pavel, Thanks for pointing it out. I had no idea Stuart got it in vim too. I pushed a PR upstream to get rid of it in the asciidoc repo. I'll delete vim-asciidoc once upstream signed off on its removal. Thanks, Joseph

Bug#949780: maptool: Maptool segfaults

Thanks for your answers. On Sun, Jan 26, 2020 at 4:39 AM ael wrote: > I used the simplest defaults I think. > > In my history I just have > cmake ../navit/ > make maptool > > Does that tell you what you need to know? It does, thanks. Joseph

Bug#949780: maptool: Maptool segfaults

Hi, Taking the england-latest.osm.pbf from https://download.geofabrik.de/europe/great-britain.html it does fail with 0.5.4 after several minutes of processing with (not a segfault per say but still failing): PROGRESS9: Processed 47104 nodes (8208 out) 0 ways 62282 relations 0 tiles 7:17 181 MB

Bug#949780: maptool: Maptool segfaults

Hi, On Fri, Jan 24, 2020 at 2:00 PM ael wrote: > Package: maptool > Version: 0.5.3+dfsg.1-2+b1 Please try with the 0.5.4 version currently in unstable as here have been a lot of changes to maptool since 0.5.3. > This was encountered while looking at the issues with navit on wince: > see

Bug#949484: navit FTBFS on ppc64el, rsvg crashes.

Hi Peter, Thank for your report. On Tue, Jan 21, 2020 at 6:09 AM peter green wrote: > Unfortunately the new version failed to build on ppc64el, > it seems rsvg is crashing. I noticed this issue but it seems to me like it's really an issue with librsvg2 more than an issue with Navit itself. >

Bug#949214: Bug#948388: navit: fails to connect to gpsd

Control: merge 948388 949214 Hi Mattia, thanks for the official FTBS report. It appears this issue has already been reported in #948388 so I'm merging the 2 bugs. if you don't mind. Hi guys, thanks for the report, investigation and patching. On Fri, Jan 17, 2020 at 5:18 PM Peter Green wrote: >

Bug#946810: python3-commonmark-py: update the source url in watch to match the currently supported repo

Package: python3-commonmark-bkrs Version: 0.5.4+ds-4 Severity: wishlist Dear Maintainer, The watch file of the package points to the old repository (rolandshoemaker/CommonMark-py): https://salsa.debian.org/python-team/modules/commonmark- bkrs/blob/master/debian/watch But that repository clearly

Bug#946805: ruby-hamlit: Please upgrade to latest upstream

Package: ruby-hamlit Version: 2.9.2-2 Severity: wishlist Dear Maintainer, Since the upgrade of ruby-tilt to 2.0.10 yesterday the tests for ruby-hamlit fail. See: https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby- hamlit/3668609/log.gz It seems that this has been fixed in the latest

Bug#946619: python3-pylint-django: Re-enable the tests after pylint 2.5 has been released.

Package: python3-pylint-django Version: 2.0.11-1 Severity: wishlist As explained in #945426, pylint 2.4 has removed the unit tests from the package installation and the test functional classes have only been re-introduced in the package in pylint 2.5 so for now I'll disable the unit tests and

Bug#895462: Please keep asciidoc in Debian

Hi Simon, I'd be interested in your use case. Do you have some examples of what you call "proper localization with support for multiple languages and flexibility through additional config files"? I also work with asciidoctor so I'd be happy to see with them if upstream has that on their backlog.

Bug#945426: pylint doesn't ship the test libraries anymore

Hi, FYI what I'm looking for is the test_functional-related classes and those have been moved to pylint/testutils.py in the upcoming version 2.5 so we can also wait until that new version is released and leave the tests in the source package only tooif you want. Thanks, Joseph

Bug#945391: asciidocapi: fails with AttributeError: 'NoneType' object has no attribute 'loader'

Control: forwarded -1 https://github.com/asciidoc/asciidoc-py3/pull/86 Hi Simon, Thanks a lot for the report! I was able to reproduce the bug you described and I can confirm that your patch works as expected. Thanks a lot for that! :) I forwarded your patch to the upstream repo:

Bug#945426: pylint doesn't ship the test libraries anymore

Package: pylint Version: 2.4.4-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, Thanks a lot for the prompt upgrade of pylint the other day. Unfortunately since the upgrade, it seems we lost the testing libraries that other packages like pylint-django rely on.

Bug#944987: pylint: please upgrade to >= 2.3.0

Source: pylint Version: 2.2.2-4 Severity: wishlist Hi Sandro, Would it be possible to upgrade pylint to latest please? I'm currently in the need of pylint 2.3.0 minimum to be able to upgrade pylint- django. If you want me to take care of it, please let me know I can try. Thanks, Joseph --

Bug#943456: m2r: maintain in python group?

Hi Jonas, I noticed that your ITP mentioned that you plan to maintain m2r in the Debian group. Any chance you could put it in the Python module group instead? https://salsa.debian.org/python-team/modules Thanks, Joseph

Bug#942751: RM: gnome-shell-pomodoro/unstable [s390x] -- ANAIS; dependency not building on s390x

Package: ftp.debian.org Severity: normal Hi guys, As gnome-shell isn't in s390x anymore and is required for the installation (but not the build) of gnome-shell-pomodoro, Jeremy suggested in https://salsa.debian.org/debian/gnome-shell-pomodoro/merge_requests/2 that I release a new version that

Bug#940718: xml-core: please remove versioned depends on sed

Hi Andrej, > xml-core depends on sed (>= 4.1.2-8). However, looking at sed, I don’t > see the reason why this particular version, and it’s not even in > oldoldstable anymore anyway. Please consider dropping the versioned > requirement and replacing it with a plain one. Just FYI this specific

Bug#940718: xml-core: please remove versioned depends on sed

Control: owner -1 ! Hi Andrej, Thanks for the report. It indeed doesn't makes sense anymore and I don't have the entire history of it so I'm not sure why it was setup this way. I'll clean that up. Thanks, Joseph

Bug#936151: New asciidoc version uploaded with python3 support

Control: tags -1 + pending Hi, Thanks for the report and sorry for the late reply. I've just uploaded to the ftp queue a new git snapshot of the python3 implementation of asciidoc. Hopefully everything works as expected with that unreleased implementation. Thanks for your patience, Joseph

Bug#936422: django-tables: Python2 removal in sid/bullseye

Hi Matthias, I was surprised to receive this mail as I thought that migration had already been done but it turns out that the doc package was still depending on python-doc instead of python3-doc. I'll upload the new version shortly. Thanks, Joseph

Bug#935196: asciidoctor: Source highlighting does not work any more

Control: forwarded -1 https://github.com/asciidoctor/asciidoctor/issues/3394 Control: owner -1 ! Hi Sebastien, Thanks for your report. I'm working on a patch with upstream. Thanks, Joseph

Bug#934998: asciidoctor: new upstream version

Control: owner -1 ! Hi Brian, Thanks for your report. I was working on that upgrade a few wweeks ago but hit some roadblock as you can see in https://lists.debian.org/debian-ruby/2019/06/msg3.html I'll try to see if I can package the new version today. Joseph -BEGIN PGP SIGNATURE-

Bug#919479: gnome-shell-pomodoro: multimonitor setup: pomodoro break 'breaks' gnome shell, restart needed

Package: gnome-shell-pomodoro Followup-For: Bug #919479 Hi Wim, Can you reproduce it in newer versions of the package? What windows manager do you use when you have the problem? Is it only happening with 3 screens? I've been running that app for a long time on dual screen using i3 and haven't

Bug#934530: ruby-sequel-pg - new version available

Package: ruby-sequel-pg Version: 1.6.16-1+b2 Severity: wishlist Dear Maintainer, I can see that ruby-sequel-pg has a new version available and has a RC bug (#899307 which is not happening anymore, I checked). Do you mind if I prepare the new version and upload it as a team upload? Thanks for

Bug#926711: gnome-shell-pomodoro: workaround for notification volume going to 100%

Hi, Sorry for the late reply. I thought I already answered that report but it seems it's just that I replied to another one that was saying the exact same thing, I'm not sure there's a fix for it. Just a workaround (I know it's not ideal but I don't have enough knowledge of Vala to propose a

Bug#934271: #934271: patch integrated!

Control: tags ! + pending Control: forwarded ! https://github.com/vinayak-mehta/tablib/pull/374 Hi Mathieu, Thanks for the report and sorry for the late reply. I've uploaded the latest version of python-tablib and included your patch. I also forwarded your patch to upstream to hopefully get it

Bug#934020: O: libnxml -- C library for parsing, writing and creating xml 1.0/1.1 files or streams

Package: wnpp Severity: normal I intend to orphan the libnxml package. The package description is: libnxml is a C library for parsing, writing, and creating XML 1.0 and 1.1 files or streams. It supports UTF-8, UTF-16be and UTF-16le, UCS-4 (1234, 4321, 2143, 2312).

Bug#934019: O: cmph -- C Minimal Perfect Hashing Library development files

Package: wnpp Severity: normal I intend to orphan the cmph package. The package description is: Minimal perfect hash functions are widely used for memory efficient storage and fast retrieval of items from static sets, such as words in natural languages, reserved words in programming languages

Bug#934018: O: libmrss -- C library for parsing, writing and creating RSS files or streams

Package: wnpp Severity: normal libmrss is a C library for parsing, writing and creating RSS (0.91, 0.92, 1.0, 2.0) files or streams. . This package contains the shared libraries. It is not really maintained upstream anymore but should be relatively clean.

Bug#934017: O: gnome-shell-pomodoro -- GNOME Shell time-management app

Package: wnpp Severity: normal I intend to orphan the gnome-shell-pomodoro package. The package description is: This GNOME Shell app helps you to manage time according to the pomodoro technique. . Features: * puts a countdown timer in the GNOME Shell top panel; * nags you with reminders

Bug#934015: O: asciidoc -- Highly configurable text format for writing documentation

Package: wnpp Severity: normal I intend to orphan the asciidoc package. The package description is: AsciiDoc is a text document format for writing articles, books, manuals and UNIX man pages. AsciiDoc files can be translated to HTML (with or without stylesheets), DocBook (articles, books and

Bug#933921: src:python-tablib: Unsafe use of yaml.load()

Hi, Thanks Scott for the report. Tomas: the repository in Openstack was archived long ago because it was ported to https://salsa.debian.org/python-team/modules/python-tablib The module is used by other packages than openstack (like django-tables if I remember correctly), so could you please hold

Bug#899307: ruby-sequel-pg: All SELECT ::Dataset methods fails with FrozenError

Control: tags -1 + moreinfo Hi Andrey, I'm trying to reproduce your issue but I can't seem to be able to. I get an error the 1st time I try to establish the connection but I believe that's linked to something else. Here's what I see (I use docker run --rm --name pg-docker -e

Bug#660687: Update on ITA: xml-core

Hi guys, I haven't had much time to work on this over the last few weeks. Other priorities have showed up. I'll get back to this when I get more time. In the meantime if someone else wants to get on, take care of the bug reports and adopt the package, go ahead. If not, I'll finish that later.

Bug#918340: pylint-django build depends on python3-factory-boy that is currently not in buster

FYI, the new version of factory-boy is on the ftp-master queue. This will solve itself in the next few days. I'll close it once the package reaches testing. Cheers, Joseph

Bug#918340: pylint-django build depends on python3-factory-boy that is currently not in buster

Hi Adrian, Thanks for the report. I was hoping to get a quick answer from https://github.com/FactoryBoy/factory_boy/issues/552 to push the new version of factory-boy without patching but I'll probably try to update the package and add the patch for python 3.7 that has been already merged so that

Bug#910318: factory-boy: do you mind if I upload the new version and fix the FTBS?

Hi Brian, One of my packages needs factory-boy to be able to run properly (see #918340). Do you mind if I upload the latest version of factory-boy and add the subset of the relevant patch that fixes the compatibility with python 3.7? (the part about factory/utils.py in

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Note that I'm having trouble with the latest release right now (see https://github.com/PyCQA/pylint-django/issues/215) so I won't upload it today. But I should be able to get that fixed shortly.

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Control: tags -1 + fixed-upstream Reading through the changes of 2.0.1 to 2.0.5 of pylint-django, it seems that this change has already been dealt with in the latest version. See:

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Control: tags -1 - fixed Control: tags -1 + patch Hi guys, Thanks Lucas for the report. Sorry for the late reply, I was out of the country with very limited internet access. Thanks Emmanuel for the quick patch. Notes for next time: * Please use meaningful commit messages, especially when

Bug#907105: Bug#909105: consider switching asciidoctor to Architecture: all

Hi Jeremy, On Thu, Nov 22, 2018 at 6:11 AM Jeremy Bicha wrote: > Could you go ahead and do this upload now? Sorry but I've been waiting for 2 months for the debian-keyring to be uploaded to be able to upload my packages. As long as it's not been released with my key I believe I can't upload my

Bug#911650: [developers-reference] usage of dh_strip conflicts with debhelper documentation

Hi Tobias! :) On Mon, Oct 22, 2018 at 10:43 PM Tobias Frost wrote: > I think that would be great; my (related) merge request > https://salsa.debian.org/debian/developers-reference/merge_requests/7 > misses the information what to do when you mirgrate from manual to > automatic debug packages. >

Bug#911650: [developers-reference] usage of dh_strip conflicts with debhelper documentation

Package: developers-reference Version: 3.4.21 Severity: normal Hi, Based on the man page of dh_strip[1], "the `--dbg-package` option is a now special purpose option that you normally do not need" which contradicts with the paragraph 6.7.9. )Best practices for debug packages) of the developers

Bug#910841: xml-core: more elts

Another element to keep in mind when working on that one is what is explained in https://lists.debian.org/debian-qa/2015/08/msg00015.html

Bug#910841: xml-core: review how the catalogs updates are handled

Package: xml-core Version: 0.18 Severity: wishlist This is a follow-up on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660687#15 as it makes more sense in its own bug report rather than on the ITA bug report. The following content was from Daniel Leidert, previous maintainer of the package:

Bug#910838: xml-core: add unit tests

Package: xml-core Version: 0.18 Severity: whishlist It would be nice to have some unit tests on this package. It's pretty widely used and unit tests would prevent from some unexpected bugs after a given change.

Bug#660687: ITA: xml-core -- XML infrastructure and XML catalog file support

Control: retitle 660687 ITA: xml-core -- XML infrastructure and XML catalog file support Hi, Based on the lack of answer I'm guessing you didn't have the time to look at it so I'm going to go ahead and work on the package in the next few weeks. Let me know if you still want to adopt it, I can

Bug#910702: gnome-shell-pomdoro: Please Build-Depends on gjs

On Thu, Oct 11, 2018 at 3:02 PM Jeremy Bicha wrote: > Would it be ok if I uploaded to Debian from your git repo if we do need it? I have absolutely no problems with that. :) I'm done with my changes for now. Feel free to cut the release whenever you need it. Joseph

Bug#910057: Proposed patch

Control: tags -1 + patch Proposed patch: https://salsa.debian.org/aerostitch/userdir-ldap/merge_requests/1 I contacted the DSA team via #debian-admin, waiting for feedback. Not sure if there's any package this ticket should be reassigned to or if it should be just closed manually when the MR is

Bug#909105: consider switching asciidoctor to Architecture: all

> I reported that bug. Indeed, that's why I was confused! :D > After reading my report three times, I see how you > might have interpreted it that way. I wrote that there is a problem, > "because asciidoctor is Architecture: all and implicitly Multi-Arch: > no". The problem results from the

Bug#909105: consider switching asciidoctor to Architecture: all

Hi Helmut, Thanks for your report. I think you can find the explanations to those questions in #893467 which is the origin of th split of the asciidoc package. Let me know if there are still more questions about it after reading #893467. Regarding the dependency version, that's a good point

Bug#906504: pulseaudio: FTBFS in buster/sid (failing tests) => patch available

Hi Sven and Felipe, Thanks for the report on those architectures and the intermediate upload. I think I found a better way to handle that test that I proposed in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/7 The idea is rather than allowing a random number of rounding

Bug#908291: developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU

Hi Ian, On Sun, Sep 9, 2018 at 7:39 AM Ian Jackson wrote: > Maybe adding a link or xref to policy 5.6.12.1 would be helpful. Good point, thanks! I updated the MR to include the reference to the policy. Joseph

Bug#908291: developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU

Source: developers-reference Severity: wishlist Tags: patch Dear Maintainer, The Developer's reference explains a lot about NMUs and corresponding version scheme but it does not explain the naming convention to use when you have to revert an NMU that brings a new upstream version. Lintian has a

Bug#907936: nuntius-linux FTBFS with vala 0.42.0-1

Hi Barak, On Thu, Sep 6, 2018 at 2:35 AM Barak A. Pearlmutter wrote: > > Thanks. But even with that patch I'm still getting a build error with > valac 0.42.0-1 > > src/notification.vala:37.17-37.29: error: Equality operation: `null' > and `bool' are incompatible > if (_read != null)

Bug#906504: pulseaudio: FTBFS in buster/sid (failing tests) => patch available

Control: forwarded -1 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/4 Control: tags -1 + patch Control: tags -1 + upstream Hi, The issue is due to a optiomizations impacting precision with GCC8. There is an existing bug report on this issue upstream:

Bug#907936: nuntius-linux FTBFS with vala 0.42.0-1

Control: forwarded -1 https://github.com/holylobster/nuntius-linux/pull/79 Control: tags -1 + upstream Hi, FYI I pushed a patch upstream to fix that specific issue. See https://github.com/holylobster/nuntius-linux/pull/79 Best, Joseph

Bug#907897: gnome-shell-pomodoro: FTBFS

Control tag -1 + pending Hi, The issue is related to the Vala upgrade to 0.42.0 which was released on 09/02 in Debian and brings this commit in: https://github.com/GNOME/vala/commit/0d396f7daaf34596b159380b8ee2a57799ac9336 which forces the absence of "default" to custom get accessors. Anyway,

Bug#907897: gnome-shell-pomodoro: FTBFS

Control: forwarded -1 https://github.com/codito/gnome-pomodoro/issues/369 Control: owner -1 ! Hi Paul, Thanks for the report. Perfect timing, I was preparing a release for another FTBS! :) Working on a fix right now. It should be available soon. Thanks Joseph

Bug#905107: gnome-shell-pomodoro: patch in the repo

Control: tags -1 + pending Patched version available in the repo. I'm in the process of becoming a DD. If my usual sponsor don't have the time to review and upload it before I finish the process, I'll take care of it (hopefully in about 2 weeks). Thanks, Joseph

Bug#905107: gnome-shell-pomodoro: global.screen is not available in GNOME Shell 3.29

Hi Simon, Sorry for the late, I just saw this bug. Thanks for forwarding it upstream. I'll work on a PR for that this weekend. Joseph

Bug#869194: awscli failing to upload empty files on => due to python-s3transfer

Control: reassign -1 python-s3transfer Control: forwarded -1 https://github.com/boto/s3transfer/pull/102 Reassigning this bug to python-s3transfer as it is the one that will be patch to support the missing argument. Upstream issues:

Bug#898592: lintian: add tag debian-pyversions-is-obsolete

Hi Chris, On Mon, May 14, 2018 at 2:31 PM, Chris Lamb wrote: > (FYI I think your MR missed the debian/changelog entry as well as not > shipping the two "pyversions" test fixtures, presumably because they > were files "new" to Git?) Oops, I indeed forgot the git add on the 2

Bug#898592: lintian: add debian-pyversions-is-obsolete => patch

Control: tags -1 + patch Patch proposed: https://salsa.debian.org/lintian/lintian/merge_requests/3 Thanks Joseph

Bug#898592: lintian: add tag debian-pyversions-is-obsolete

Package: lintian Version: 2.5.86 Severity: wishlist Dear Maintainer, Since the transition to dh_python2 [1], it is recommended by the python policy [2] to use X-Python-Version and X-Python3-Version tag in debian/control (if necessary) instead of the debian/pyversions file. I think it would be a

Bug#895166: ben: move out of asciidoc

On Sun, May 13, 2018 at 4:27 AM, Mehdi Dogguy wrote: > I've done the necessary changes to use asciidoctor instead of asciidoc and > pushed my changes to Ben's Git repository. This bug will be closed with > the next upload. Awesome, thanks a lot Mehdi! :)

Bug#896396: python*-django-tables2: django_tables2 fails to import => usage problem???

I just saw that that there was a discussin on #896429 (I was looking at #896396). > I wonder whether we can draw anything useful from these bugs before > closing them. > > For one thing, you cannot use autopkgtest-pkg-python on these modules as is. > So yeah, for django this may make sense, but

Bug#896396: python*-django-tables2: django_tables2 fails to import => usage problem???

Control: severity -1 minor Control: tag -1 + moreinfo Hi The error message you posted seems pretty explicit: it seems you're missing some configuration apparently: django.core.exceptions.ImproperlyConfigured: Requested setting DEFAULT_INDEX_TABLESPACE, but settings are not

Bug#865855: New version of tablib ready for review/upload

Hi guys, I updated the package to use standard branches, pybuild, autopkgtest, make it run with python3 and get the latest version in. I pushed it to the following repository: https://salsa.debian.org/python-team/modules/python-tablib Let me know if it's acceptable. If so

Bug#896263: django-haystack: 2 RC bugs => 1 MR

Dear maintainer, I believe those 2 bugs would be fixed by https://salsa.debian.org/python-team/modules/django-haystack/merge_requests/1 Could you have a look please? I see in https://github.com/django-haystack/django-haystack/pull/1603 that other people outside of Debian seem to have the

Bug#895186: asciidoctor: url-related issues are fixed upstream

Control: tag -1 + fixed-upstream Hi, The issue has been fixed upstream and will be released as part of 1.5.7 whose timeline is being discussed in https://github.com/asciidoctor/asciidoctor/issues/2663 Thanks, Joseph

Bug#895187: asciidoctor: url-related issues are fixed upstream

Control: tag -1 + fixed-upstream Hi, The issue has been fixed upstream and will be released as part of 1.5.7 whose timeline is being discussed in https://github.com/asciidoctor/asciidoctor/issues/2663 Thanks, Joseph

Bug#895613: asciidoctor FTBFS: test failures

Thanks a lot for the quick answer! :) > I can reproduce in a chroot with "dpkg-buildpackage -B" > (there's likely some way to do the same in sbuild). I'm now able to reproduce it with the following flags: `--arch-any --no-arch-all` I'll try to fix it this morning. Thanks for the help! Joseph

Bug#895613: asciidoctor FTBFS: test failures

Hi Adrien, Thanks for reporting. I was looking into it already. My only problem is that I can't reproduce it when using sbuild in my gbp buildpackage locally. I tried with different parameters but can't understand why. The missing files should have been installed by dh_install as they are defined

Bug#895501: btrfs-progs: move out of asciidoc

Package: btrfs-progs Version: 4.15.1-1 Control: block 895462 by -1 Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. btrfs-progs already supports asciidoctor to build its documentation natively

Bug#895485: booth: move out of asciidoc

Package: booth Version: 1.0-6 Severity: wishlist Control: block 895462 by -1 Control: forwarded -1 https://github.com/ClusterLabs/booth/pull/67 Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth.

Bug#895462: asciidoc: deprecate in Debian

Package: asciidoc Version: 8.6.10-2 ​Control: b​ lock -1 by 884213 893467 895186 895187 894192 894194 894188 894697 894700 894710 895165 895166 895167 895168 As announced by upstream in their last release[1], this is probably the last release of asciidoc and encourage people to move to alternate

Bug#895188: asciidoctor: E-mail addresses are rendered twice [manpage backend]

Hi, I think this is due to the way the links are rendered in general. To achieve your goal you would need to use the following: mailto:debian.a...@manchmal.in-ulm.de[Christoph Biedl] instead of: Christoph Biedl See:

Bug#895167: bgpdump: move out of asciidoc

Hi Christoph, > Switching to asciidoctor was the obvious thing to do although it's not a > simple drop-in replacment for a2x. Probably "asciidoctor --attribute > reproducible --backend=manpage" does the trick. Yes, that's the command to generate manpages in asciidoctor. > But I'm stuck with

Bug#895168: boot-info-script: remove unused dependency on asciidoc

Package: boot-info-script Version: 1.5.0-2 Severity: wishlist Dear Maintainer, It seems that asciidoc has been forgotten to be removed in https://salsa.debian.org/debian/boot-info-script/commit/c079e0276ef46516399f211613b1240522a742b8 Patch available here:

Bug#895167: bgpdump: move out of asciidoc

Package: bgpdump Version: 1.5.0-2 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the

Bug#895166: ben: move out of asciidoc

Package: ben Version: 0.7.7 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the replacement

Bug#895165: awesome-extra: move out of asciidoc

Package: awesome-extra Version: 2017110501 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is

Bug#894710: awesome: move out of asciidoc

Hi Reiner, > What is your planned timeline for getting rid of asciidoc? > Is it sufficient to wait for the next awesome release, or do you want to > have it already applied to the currently released version? Asciidoc will be removed on next Debian major release when python2 will be removed so

Bug#894710: awesome: move out of asciidoc

Package: awesome Version: 4.2-5 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the

Bug#894700: autorevision: move out of asciidoc

Package: autorevision Version: 1.21-1 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the

Bug#894698: apgdiff: wrong home page - proposed patch

Control: tags -1 + patch Proposed patch: https://salsa.debian.org/postgresql/apgdiff/merge_requests/2

Bug#894698: apgdiff: wrong home page

Package: apgdiff Version: 2.5.0~alpha.2-75-gcaaaed9-1 Severity: wishlist Dear Maintainer, The current home page of apgdiff defined in the package (http://apgdiff.startnet.biz/) does not exist anymore. This one has been migrated to https://www.apgdiff.com/. Regards, Joseph

Bug#894697: apgdiff: move out of asciidoc - patch

Control: tags -1 + patch Proposed patch: https://salsa.debian.org/postgresql/apgdiff/merge_requests/1

Bug#894697: apgdiff: move out of asciidoc

Package: apgdiff Version: 2.5.0~alpha.2-75-gcaaaed9-1 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for

Bug#894224: pylint: dpkg-source complains about missing .eggs folder when building from source

Control: tags -1 +patch Hi, The proposed patch is: https://salsa.debian.org/python-team/applications/pylint/merge_requests/1 Best, Joseph

Bug#894224: pylint: dpkg-source complains about missing .eggs folder when building from source

Package: pylint Version: 1.8.1-1 Severity: wishlist Hi, When I try to build the package from the git repo it fails with the following error (even if I can't find it in the orig tarball or in the one built from the pristine-tar tarball: dpkg-source: warning: file

Bug#894194: anet: move out of asciidoc

Package: anet Version: 0.3.4-1 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the

Bug#894192: altos: move out of asciidoc

Package: altos Version: 1.8.5-1 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the

Bug#894188: ansible: Move out of asciidoc

Package: ansible Version: 2.5.0+dfsg-1 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages packages that depend on it and their upstream to get its EOL go smooth. A patch has been merged by upstream to get rid of it. It

  1   2   3   4   >