Package: geeqie-common
Version: 1:1.5.1-3
Severity: serious
The changelogs in this package are not compressed:
,
| $ ls /usr/share/doc/geeqie-common/changelog*
| /usr/share/doc/geeqie-common/changelog
/usr/share/doc/geeqie-common/changelog.Debian
`
Looking at debian/rules, apparently
Package: geeqie
Version: 1:1.5.1-3
Severity: serious
There was a problem when updating your package (sorry for the German):
,
| Vorbereitung zum Entpacken von .../6-geeqie_1%3a1.5.1-3_amd64.deb ...
| Entpacken von geeqie (1:1.5.1-3) über (1:1.5.1-2) ...
| dpkg: Fehler beim Bearbeiten des
Dear Paul, thanks for your report. I can reproduce the issue on my box.
I am working on it. Cheers, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B
signature.asc
Description:
Processing control commands:
> tags -1 - moreinfo
Bug #942428 [release.debian.org] transition: gssdp/gupnp
Removed tag(s) moreinfo.
> tags -1 confirmed
Bug #942428 [release.debian.org] transition: gssdp/gupnp
Added tag(s) confirmed.
> block -1 by 947805
Bug #942428 [release.debian.org]
Processing commands for cont...@bugs.debian.org:
> block 947486 with 947617
Bug #947486 [src:golang-github-containers-image]
golang-github-containers-image: FTBFS with test failures
947486 was not blocked by any bugs.
947486 was not blocking any bugs.
Added blocking bug(s) of 947486: 947617
>
Package: geoipupdate
Severity: serious
Hello maintainer,
Unfortunately, it seems that MaxMind have changed their policies on GeoLite2
databases such that they now require a license key. In addition (and more
critically), they are no longer licensed under a Creative Commons BY-SA
license, and
Your message dated Tue, 31 Dec 2019 04:19:14 +
with message-id
and subject line Bug#936508: fixed in fdb 2.0.0-1.1
has caused the Debian Bug report #936508,
regarding fdb: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tags 936508 + patch
Dear maintainer,
I've prepared an NMU for fdb (versioned as 2.0.0-1.1). The diff
is attached to this message.
Regards.
diff -Nru fdb-2.0.0/debian/changelog fdb-2.0.0/debian/changelog
--- fdb-2.0.0/debian/changelog 2019-02-07 05:43:34.0 -0500
+++
Processing control commands:
> tags 936508 + patch
Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye
Added tag(s) patch.
--
936508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: python3-socksipychain
Version: 2.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Your message dated Tue, 31 Dec 2019 01:38:40 +
with message-id
and subject line Bug#946415: fixed in rust-cargo 0.41.0-1
has caused the Debian Bug report #946415,
regarding rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which
doesn't exist
to be marked as done.
This means
Source: gvm-libs
Version: 11.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
gvm-libs/experimental FTBFS during the indep-only build:
[...]
dh_auto_test -i
cd obj-x86_64-linux-gnu && make -j3 test ARGS\+=-j3
make[1]: Entering directory
Processing commands for cont...@bugs.debian.org:
> found 934687 0.5.4-1
Bug #934687 {Done: Debian FTP Masters }
[heudiconv] heudiconv, indirectly build-depends on cruft package, needs to
migrate to python 3
Marked as found in versions heudiconv/0.5.4-1 and reopened.
> tags 947712 + sid bullseye
Package: upnp-router-control
Version: 0.2-1.2
Severity: serious
Tags: sid buster
Forwarded: https://bugs.launchpad.net/upnp-router-control/+bug/1857942
Hello,
We are planning to upload gupnp/gssdp 1.2 to debian unstable.
Unfortunately upnp-router-control FTBFS with this version and needs to
be
Processing commands for cont...@bugs.debian.org:
> forwarded 947237 https://gitlab.gnome.org/GNOME/gnome-software/issues/880
Bug #947237 [gnome-software-plugin-snap] gnome-software: Crashes on click over
any software icon
Set Bug forwarded-to-address to
Your message dated Mon, 30 Dec 2019 23:34:15 +
with message-id
and subject line Bug#937794: fixed in python-gnupg 0.4.5-2
has caused the Debian Bug report #937794,
regarding python-gnupg: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 30 Dec 2019 23:05:07 +
with message-id
and subject line Bug#947058: fixed in pygalmesh 0.5.0-3
has caused the Debian Bug report #947058,
regarding pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)
to be marked as done.
This means that you claim that the
The first link is mine and the original fork but its basically abandoned. I
haven’t looked at any of the forks so unsure which are popular or being
kept up-to-date.
On Mon, Dec 30, 2019 at 12:56 PM Andreas Tille wrote:
> Hi Abhik,
>
> thanks for the quick reply.
>
> On Sun, Dec 29, 2019 at
Marco d'Itri dixit:
>> a new source-only upload and piuparts fails testing, though
>> the latter might be due to the glibc issue maybe?
>No, this is an unrelated piuparts bug which was fixed yesterday.
Ah okay.
In the meantime, a new glibc was uploaded and just needs to
finish building on
Processing control commands:
> tag -1 pending
Bug #937794 [src:python-gnupg] python-gnupg: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #937794 to the same tags previously set
--
937794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937794
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #937794 in python-gnupg reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Dec 30, Thorsten Glaser wrote:
> ① it won’t migrate as-is currently anyway, because it needs
> a new source-only upload and piuparts fails testing, though
> the latter might be due to the glibc issue maybe?
No, this is an unrelated piuparts bug which was fixed yesterday.
--
ciao,
Marco
Control: reassign -1 tk-mpeg
Control: found -1 1.0.7-1
On Lu, 30 dec 19, 21:14:12, Ole Streicher wrote:
> Package: tk-mpeg 1.0.7-1
> Severity: serious
>
> Tkmpeg does not work and causes saods9 to fail:
>
> Error in startup script: couldn't load file
>
Processing control commands:
> reassign -1 tk-mpeg
Bug #947793 [tk-mpeg 1.0.7-1] tkmpeg not working
Warning: Unknown package '1.0.7-1'
Bug reassigned from package 'tk-mpeg 1.0.7-1' to 'tk-mpeg'.
Ignoring request to alter found versions of bug #947793 to the same values
previously set
Ignoring
Alright, here's a revised process to compile Chromium locally with tracing re-
enabled:
1. First, download the patch and save it as "enable-tracing.patch"
2. Run the following:
$ wget
Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to
libkate-tools removal
has caused the Debian Bug report #946632,
regarding libkate: autopkgtest failures due to
Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to
libkate-tools removal
has caused the Debian Bug report #947293,
regarding libkate: autopkgtest failures due to
Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to
libkate-tools removal
has caused the Debian Bug report #947293,
regarding libkate: autopkgtest regression: tests
Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to
libkate-tools removal
has caused the Debian Bug report #946632,
regarding libkate: autopkgtest regression: tests
Hi Abhik,
thanks for the quick reply.
On Sun, Dec 29, 2019 at 05:55:35PM -0800, Abhik Shah wrote:
> I haven’t made a py3 port and actually haven’t worked on Pebl in years.
> There are some forks though (on github) and they may have py3 versions.
This one looks official
Processing control commands:
> affects -1 src:python3-defaults
Bug #947794 [src:python-apt] python-apt: autopkgtest fails on deprecation
*warnings* to stderr
Added indication that 947794 affects src:python3-defaults
--
947794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947794
Debian Bug
Source: python-apt
Version: 1.8.4
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
Dear maintainers,
With a recent upload of python3-defaults the autopkgtest of python-apt
fails in testing when that autopkgtest
Package: tk-mpeg 1.0.7-1
Severity: serious
Tkmpeg does not work and causes saods9 to fail:
Error in startup script: couldn't load file
"/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so":
/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so: undefined symbol:
Source: dh-python
Version: 4.20191017
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
[X-Debbugs-CC: debian...@lists.debian.org,
python3-defau...@packages.debian.org]
Dear maintainers,
With a recent upload of
Processing control commands:
> affects -1 src:python3-defaults
Bug #947789 [src:dh-python] dh-python: autopkgtest needs update for new version
of python3-defaults: doesn't depend on itself
Added indication that 947789 affects src:python3-defaults
--
947789:
Your message dated Mon, 30 Dec 2019 18:49:42 +
with message-id
and subject line Bug#945648: fixed in goldeneye 1.2.0+git20191230-1
has caused the Debian Bug report #945648,
regarding goldeneye: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 30 Dec 2019 18:35:20 +
with message-id
and subject line Bug#947778: fixed in glibc 2.29-7
has caused the Debian Bug report #947778,
regarding libc6-dev: please change dependency on libcrypt1-dev to libcrypt-dev
to be marked as done.
This means that you claim that the
Your message dated Mon, 30 Dec 2019 18:34:17 +
with message-id
and subject line Bug#942957: fixed in dfdatetime 20190116-1.1
has caused the Debian Bug report #942957,
regarding dfdatetime: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #945648 [src:goldeneye] goldeneye: Python2 removal in sid/bullseye
Added tag(s) pending.
--
945648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #945648 in goldeneye reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #947778 in glibc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags 936387 + patch
Control: tags 942957 + patch
Dear maintainer,
I've prepared an NMU for dfdatetime (versioned as 20190116-1.1). The diff
is attached to this message.
Regards.
diff -Nru dfdatetime-20190116/debian/changelog dfdatetime-20190116/debian/changelog
---
Processing control commands:
> tags 936387 + patch
Bug #936387 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 942957 + patch
Bug #942957 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Added tag(s) patch.
--
936387:
Processing control commands:
> tag -1 pending
Bug #947778 [libc6-dev] libc6-dev: please change dependency on libcrypt1-dev to
libcrypt-dev
Added tag(s) pending.
--
947778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> tags 936387 + patch
Bug #936387 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #936387 to the same tags previously set
> tags 942957 + patch
Bug #942957 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Your message dated Mon, 30 Dec 2019 18:07:26 +
with message-id
and subject line Bug#937323: fixed in prettytable 0.7.2-5
has caused the Debian Bug report #937323,
regarding prettytable: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #937323 [src:prettytable] prettytable: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Eloston,
Thanks for figuring out the cause of these random crashes! However, I was
unable to recompile chromium from source following your instructions. I got
the following error message at step 4b:
jj@telos:~/src/chromium-79.0.3945.79$ debian/rules get-orig-source
wget -nv
Control: tag -1 pending
Hello,
Bug #937323 in prettytable reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Your message dated Mon, 30 Dec 2019 17:20:12 +
with message-id
and subject line Bug#946850: fixed in last-align 1044-2
has caused the Debian Bug report #946850,
regarding last-align ftbfs on non-x86 architectures
to be marked as done.
This means that you claim that the problem has been dealt
Just to follow-up here: As upstream for Rcpp, I just ran another reverse
dependency check againt 1700+ packages on a machine I get to use for that,
and had S4Vectors and IRanges issues pop up for three packages. It looks like
an issue with S4Vectors.
But still: Three. Out of 1700+.
Holding
Processing commands for cont...@bugs.debian.org:
> forwarded 936299 https://chirp.danplanet.com/issues/495
Bug #936299 [src:chirp] chirp: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://chirp.danplanet.com/issues/495'.
> thanks
Stopping processing here.
Please contact me
Package: libcrypt1
Version: 1:4.4.10-7
Severity: grave
Justification: renders package unusable
Sorry, the migration to testing¹ needs to be postposed a bit,
at least until #947778 is fixed (due to the -dev renaming).
① it won’t migrate as-is currently anyway, because it needs
a new source-only
Le 29/12/2019 à 13:30, Paul Gevers a écrit :
Source: rust-goblin
Version: 0.1.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
error: couldn't read examples/../assets/dotnet_executable_example.dll:
No such file or directory
Package: libc6-dev
Version: 2.29-6
Severity: grave
Justification: renders package unusable
The libcrypt1-dev package got renamed, so the dependencies must match,
or libc6-dev becomes uninstallable or libcrypt1 unupgradable. AIUI both
glibc and libxcrypt must migrate to testing together this time,
severity 946599 important
thanks
Marco d'Itri dixit:
>Since nobody else managed to reproduce this so far I am inclined to
>demote the bug to "important" to allow the migration to testing.
Agreed, it’s probably a tricky package relationship combination that
it takes to trigger this, and perhaps
Processing commands for cont...@bugs.debian.org:
> severity 946599 important
Bug #946599 [libcrypt1] libcrypt1: failure to switch from libc6 to libcrypt1
hoses the whole system
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Mon, 30 Dec 2019 15:05:29 +
with message-id
and subject line Bug#947428: fixed in tigervnc 1.10.1+dfsg-1
has caused the Debian Bug report #947428,
regarding tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694
CVE-2019-15695
to be marked as done.
This
Processing control commands:
> reopen -1
Bug #947058 {Done: Drew Parsons } [src:pygalmesh]
pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Control: reopen -1
Hi Drew
The test gets a little further [1], and now fails at:
___ test_inr ___
def test_inr():
this_dir = os.path.dirname(os.path.abspath(__file__))
mesh = pygalmesh.generate_from_inr(
Dear Maintainer,
the given valgrind backtrace should translate to something
like below (which did not crash for me).
The crashing instruction tries to read memory pointed by register $rdi,
that held in my test the address in parameters "v" / "key" / "name".
So I assume for some reason this
Hello,
full patch attached to this email!
G.
diff -Nru pyside2-5.13.2/debian/changelog pyside2-5.13.2/debian/changelog
--- pyside2-5.13.2/debian/changelog 2019-11-22 10:28:55.0 +0100
+++ pyside2-5.13.2/debian/changelog 2019-12-29 22:44:55.0 +0100
@@ -1,3 +1,19 @@
+pyside2
Processing control commands:
> tag -1 pending
Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692
CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Added tag(s) pending.
--
947428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947428
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #947428 in tigervnc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #947428 in tigervnc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692
CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Ignoring request to alter tags of bug #947428 to the same tags previously set
--
947428:
Control: tag -1 pending
Hello,
Bug #943608 in beancount reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #942791 [src:pymssql] fix pymssql for python 3.8
Added tag(s) pending.
--
942791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch pending
Bug #945314 [src:freecad] freecad: FTBFS on several architectures
Added tag(s) pending and patch.
--
945314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
I looked further and found this:
https://github.com/acassen/keepalived/issues/1071
However I don't think it's the same bug , since it doesn't restart endlessly
when it happens. So it's probable a separate bug than the initial one reported.
All in all I think the provided version doesn't seem
control: tags -1 patch pending
in deferred/1 there is a version that should now build with the new pyside.
I'm pushing on git my changes
cheers, and thanks for the help
Gianfranco
On Wed, 18 Dec 2019 11:45:06 +0100 Tommaso Colombo wrote:
> Package: freecad
> Version: 0.18.4+dfsg1-1
>
Control: tag -1 pending
Hello,
Bug #942791 in pymssql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #943608 [src:beancount] tests segfault when run with Python 3.8
Added tag(s) pending.
--
943608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 30 Dec 2019 13:49:47 +
with message-id
and subject line Bug#947546: fixed in libtexttools 2.1.0-15
has caused the Debian Bug report #947546,
regarding libtexttools: FTBFS during indep-only build: clean calls gprclean but
gprbuild is in B-D-Arch
to be marked as done.
On 29/12/2019 13:40, Michael Biebl wrote:
Can you provide a full, verbose debug log:
https://wiki.gnome.org/Projects/NetworkManager/Debugging
Which dhcp client do you use: internal, isc-dhcp-client, ...?
I made more tests and noticed that when I upgrade from 1.22.0-2 to
1.22.2-1, the IPv4
We see more problems with this package, possibly/probably related error now on
another machine:
Dec 29 00:00:01 .xxx.com keepalived[28830]: double free or corruption
(fasttop)
And service crashed, never came back. Seems it's not very stable atm on Buster
:/
Hi,
Juhani Numminen kirjoitti 25.12.2019 klo 15.45:
> I propose that we stop shipping the python2 file which in fact is
> part of build system for a PDF, and ship the actual PDF book in
> the package instead. How do you find this approach?
>
> An NMU patch is attached and I've tested it using
Since nobody else managed to reproduce this so far I am inclined to
demote the bug to "important" to allow the migration to testing.
--
ciao,
Marco
signature.asc
Description: PGP signature
Your message dated Mon, 30 Dec 2019 12:21:51 +0100
with message-id <20191230112151.ga24...@land.credativ.lan>
and subject line Re: Bug#946198: Since upgrading to 1.25.13 no remote printer
is made available anymore
has caused the Debian Bug report #946198,
regarding Since upgrading to 1.25.13 no
Your message dated Mon, 30 Dec 2019 11:04:49 +
with message-id
and subject line Bug#946937: fixed in python-django 2:3.0.1-1
has caused the Debian Bug report #946937,
regarding python-django: CVE-2019-19844: Potential account hijack via password
reset form
to be marked as done.
This means
Your message dated Mon, 30 Dec 2019 10:04:34 +
with message-id
and subject line Bug#925830: fixed in sip-tester 1:3.6.0-1
has caused the Debian Bug report #925830,
regarding sip-tester: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> fixed 937543 1.0~a6-1
Bug #937543 {Done: Antonio Valentino }
[src:pysph] pysph: Python2 removal in sid/bullseye
Marked as fixed in versions pysph/1.0~a6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937543:
Am 29.12.2019 um 13:24 schrieb John Paul Adrian Glaubitz:
> On 12/29/19 1:11 PM, John Paul Adrian Glaubitz wrote:
>> I think it's more related to recent changes in libglvnd, see:
>>
>>> https://packages.qa.debian.org/libg/libglvnd/news/20191220T191934Z.html
>> I'll try a give-back on one of the
Are there any objections to dropping this build-dependency? if not I may NMU
this package.
I have gone ahead and uploaded a NMU to delayed/5 . The debdiff is attached.
diff -Nru routes-2.4.1/debian/changelog routes-2.4.1/debian/changelog
--- routes-2.4.1/debian/changelog 2017-07-20
85 matches
Mail list logo
