Hi Lucas,
Thanks for the report and apologies for not picking this earlier.
On Wed, 2 May 2018 22:00:16 +0200 Lucas Nussbaum wrote:
[...]
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > /usr/bin/x86_64-linux-gnu-ld:
Your message dated Mon, 23 Jul 2018 01:50:32 +
with message-id
and subject line Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5
has caused the Debian Bug report #897767,
regarding highwayhash: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 23 Jul 2018 01:35:48 +
with message-id
and subject line Bug#897843: fixed in qtmpris 0.1.0-2
has caused the Debian Bug report #897843,
regarding qtmpris: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 23 Jul 2018 01:06:10 +
with message-id
and subject line Bug#897763: fixed in gsettings-qt 0.1+17.10.20170824-5
has caused the Debian Bug report #897763,
regarding gsettings-qt: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been
On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo wrote:
>
> On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> > thanks for ignoring the next paragraph in that email, so let me re-add it
> > here:
>
> I didn't ignore it, I explicitly picked on your first, fairly taunting,
> and
On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> thanks for ignoring the next paragraph in that email, so let me re-add it
> here:
I didn't ignore it, I explicitly picked on your first, fairly taunting,
and inappropriately passive-aggressive sentence (like this one).
> since
Thanks Gregor. I'll upload a new version with this patch.
On Fri, Jul 20, 2018 at 8:09 PM gregor herrmann wrote:
> Control: tag -1 + patch
>
> On Thu, 19 Apr 2018 18:08:40 +, Ari Pollak wrote:
>
> > Sorry, I haven't had time to do anything about it yet and I won't be able
> > to look at it
Your message dated Mon, 23 Jul 2018 00:04:15 +
with message-id
and subject line Bug#862678: fixed in pidgin 2.13.0-2
has caused the Debian Bug report #862678,
regarding Switch from network-manager-dev to libnm-dev
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 22 Jul 2018 22:04:05 +
with message-id
and subject line Bug#903412: fixed in asterisk 1:13.22.0~dfsg-1
has caused the Debian Bug report #903412,
regarding asterisk: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
to be marked as done.
This means that you
> What do you mean with "support"? Astroid 2.0 is working properly with py3.7
> according to upstream.
i mean that pylint/astroid 2.0 do not work with python 2 at all, but
only with python 3.4 onwards (so yes, also 3.7 in that regards).
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
> Upstream README seems to indicate that there is no release that supports
> *both* python 2.7 and 3.7
i know, that's exactly my point
> so this is not a choice between 2.0 and 1.9.
well it is: it can be decided to ignore the 2.x branch and stick with
1.9 for buster (which support python 2 and
Le 22 juillet 2018 21:52:04 GMT+02:00, Sandro Tosi a écrit :
>On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo
>wrote:
>>
>> On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote:
>> > no need, i can upgrade the package myself when needed, but thanks
>for the offer.
>>
>> Then can you pretty
The package is available via stretch-proposed-updates. Just add that one to
your sources.list until the next point release or linux security update.
HTH,
Sven
Am 22. Juli 2018 22:48:35 MESZ schrieb Jered Floyd :
>
>It appears that this ticket has been closed, noting a fix in
>linux-4.9.110-2
Your message dated Sun, 22 Jul 2018 21:19:34 +
with message-id
and subject line Bug#896797: fixed in botch 0.21-6
has caused the Debian Bug report #896797,
regarding botch: missing build dependency on dh-python
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 22 Jul 2018 21:03:49 +
with message-id
and subject line Bug#897714: fixed in bzrtp 1.0.6-3
has caused the Debian Bug report #897714,
regarding bzrtp: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> tags 875035 + pending
Bug #875035 [src:libqaccessibilityclient] [libqaccessibilityclient] Future Qt4
removal from Buster
Added tag(s) pending.
> tags 897792 + pending
Bug #897792 [src:libqaccessibilityclient] libqaccessibilityclient: ftbfs with
Processing control commands:
> severity -1 important
Bug #903607 [src:pjproject] pjproject: FTBFS due to d-devlibdeps errors
Severity set to 'important' from 'serious'
--
903607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903607
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: severity -1 important
> I cannot reproduce this locally (using sbuild) and -3 just uploaded
> built fine on the autobuilders.
Downgrading severity as it has built fine on all architectures, feel
free to reopen/upgrade if you still see this.
Bernhard
It appears that this ticket has been closed, noting a fix in linux-4.9.110-2
(source pkg). Will this replace the current linux-image-4.9.0-7-amd64 in
stretch soon? It's currently making stretch unusable with Xen.
--Jered
- On Jul 17, 2018, at 6:23 AM, Hans van Kranenburg
Your message dated Sun, 22 Jul 2018 20:35:21 +
with message-id
and subject line Bug#881205: fixed in backintime 1.1.24-0.1
has caused the Debian Bug report #881205,
regarding backintime: CVE-2017-16667: shell injection in notify-send
to be marked as done.
This means that you claim that the
Hi Sandro,
Upstream README seems to indicate that there is no release that supports
*both* python 2.7 and 3.7 so this is not a choice between 2.0 and 1.9.
More likely, two source packages are required for buster. Alternatively one of
Python 2 / Python 3 must be dropped from pylint (presumably
Processing control commands:
> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules
broken by 3.7
902788 was blocked by: 902761 903145 902650 902757 903218 903528 902631 902900
903529 903784 903016 903525 903423 903826 902766 902715 903388 902794 903031
Package: python3-tango
Version: 9.2.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a
Package: dms-core
Version: 1.0.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo wrote:
>
> On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote:
> > no need, i can upgrade the package myself when needed, but thanks for the
> > offer.
>
> Then can you pretty please do it? It is neeeded.
thanks for ignoring the next
Upstream commit is:
https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=fef089a6610f94a847541069f3008a5708044015
Processing commands for cont...@bugs.debian.org:
> notfound 897775 4.12.2-dfsg1-2
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
No longer marked as found in versions insighttoolkit4/4.12.2-dfsg1-2.
> fixed 897775 4.12.2-dfsg1-2
Bug #897775 {Done: Andreas
Processing commands for cont...@bugs.debian.org:
> close 897775
Bug #897775 [src:insighttoolkit4] itksnap: ftbfs with GCC-8
Marked Bug as done
> affects 897899 + src:itksnap src:fw4spl
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Added
Processing commands for cont...@bugs.debian.org:
> notfixed 858302 1.13.0~ds1-3
Bug #858302 {Done: Dmitry Smirnov }
[golang-github-docker-docker-dev] Should ship api source subdirectory
No longer marked as fixed in versions
golang-github-docker-docker-dev/1.13.0~ds1-3.
> fixed 858302
Processing commands for cont...@bugs.debian.org:
> unarchive 897899
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Unarchived Bug 897899
> severity 897899 serious
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8
Your message dated Sun, 22 Jul 2018 17:34:22 +
with message-id
and subject line Bug#897852: fixed in rsbackup 5.0-2
has caused the Debian Bug report #897852,
regarding rsbackup: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sun, 22 Jul 2018 17:18:55 +
with message-id
and subject line Bug#904104: fixed in aiscm 0.15.5-1
has caused the Debian Bug report #904104,
regarding aiscm: FTBFS with ffmpeg 4.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing control commands:
> tags -1 patch fixed-upstream
Bug #897800 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-8
Added tag(s) patch and fixed-upstream.
--
897800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 patch fixed-upstream
On 2018-07-22 Juhani Numminen wrote:
> Control: forwarded -1 https://github.com/ukoethe/vigra/issues/414
> On Fri, 04 May 2018 12:22:30 + Matthias Klose wrote:
> > Package: src:libvigraimpex
> > Version: 1.10.0+git20160211.167be93+dfsg-5
[...]
> >
Your message dated Sun, 22 Jul 2018 16:18:55 +
with message-id
and subject line Bug#904091: fixed in arpack 3.6.2-1
has caused the Debian Bug report #904091,
regarding arpack ftbfs on armel, mips64el, ppc64el
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 22 Jul 2018 16:03:54 +
with message-id
and subject line Bug#903349: fixed in codespell 1.13.0-3
has caused the Debian Bug report #903349,
regarding codespell: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS")
to be marked as done.
This means that you claim that
Recently Debian Stretch introduced the most annoying bug ever:
https://bugs.debian.org/900533 ("chromium 67.0.3396.62-1: youtube video, gif's,
html5, and movies no longer work"). It affects a very very lot of Debian users.
It renders entire system completely unusable. Because ability of viewing
Processing commands for cont...@bugs.debian.org:
> forwarded 897770 https://github.com/PurpleI2P/i2pd/issues/1085
Bug #897770 [src:i2pd] i2pd: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/PurpleI2P/i2pd/issues/1085'.
> stop
Stopping processing here.
Please contact me if
Your message dated Sun, 22 Jul 2018 15:49:08 +
with message-id
and subject line Bug#900652: fixed in guile-2.2 2.2.3+1-6
has caused the Debian Bug report #900652,
regarding guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets
called
to be marked as done.
This means that you
Hi,
20.07.2018 14:38, Matthias Klose пишет:
> the package ftbfs at least on armel, and mips* in Debian
It failed to build due to a missing linker option, -latomic. The fix is
already available[1], but an issue is that the option may add an
unneeded dependency.
> Did you make any measurements
Processing commands for cont...@bugs.debian.org:
> retitle 904133 telegram-desktop: FTBFS with memory exhaustion on many targets
Bug #904133 [src:telegram-desktop] t-d ftbfs with memory exhaustion on many
targets
Changed Bug title to 'telegram-desktop: FTBFS with memory exhaustion on many
Dear maintainers,
The Fedora people have got a patch to fix FTBS (FTBFS) with gcc8.
https://src.fedoraproject.org/rpms/qaccessibilityclient/c/0bc31c52a27a4b29cffa80ee67f4186295c92cf9
Juhani
Control: forwarded -1 https://github.com/ukoethe/vigra/issues/414
On Fri, 04 May 2018 12:22:30 + Matthias Klose wrote:
> Package: src:libvigraimpex
> Version: 1.10.0+git20160211.167be93+dfsg-5
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
Processing control commands:
> forwarded -1 https://github.com/ukoethe/vigra/issues/414
Bug #897800 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/414'.
--
897800:
async is now a keyword. The module has to be renamed. Upstream seems to be a
little bit dead, looking at the ML... so maybe coordinate with other distro how
to rename it?
Your message dated Sun, 22 Jul 2018 14:40:21 +
with message-id
and subject line Bug#903074: fixed in foodcritic 13.1.1-2
has caused the Debian Bug report #903074,
regarding foodcritic FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim that the
Your message dated Sun, 22 Jul 2018 14:42:18 +
with message-id
and subject line Bug#888371: fixed in webcamoid 8.1.0+dfsg-9
has caused the Debian Bug report #888371,
regarding webcamoid: FTBFS with FFmpeg 4.0
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 897790 https://github.com/octo/liboping/issues/38
Bug #897790 [src:liboping] liboping: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/octo/liboping/issues/38'.
> stop
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> forwarded 903524 https://github.com/benji-york/manuel/issues/12
Bug #903524 [src:manuel] manuel FTBFS with Python 3.7 as supported version
Set Bug forwarded-to-address to
'https://github.com/benji-york/manuel/issues/12'.
> thanks
Stopping
Processing control commands:
> block 896893 by -1
Bug #896893 [release.debian.org] transition: ffmpeg
896893 was blocked by: 888347 896824 888352 888350 904104 888363 888357 888388
888378 888385 888330 888364 888340 888343 888362 888338 888356 888373 888346
888386 896825 888382 888381 888336
Source: zoneminder
Version: 1.30.4+dfsg1-4
Severity: serious
Tags: sid buster ftbfs
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-4.0-transition
Control: block 896893 by -1
Hi,
zoneminder FTBFS with FFmpeg 4.0 which was recently uploaded to
unstable. Unfortunately the last rebuild I
Control: tag -1 pending
Hello,
Bug #903074 in foodcritic 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 #903074 [src:foodcritic] foodcritic FTBFS: update Build-Depends: ruby-ronn
-> ronn
Added tag(s) pending.
--
903074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
patch at
http://launchpadlibrarian.net/379605236/pytools_2018.1-1_2018.1-1ubuntu1.diff.gz
Processing control commands:
> tags -1 + patch
Bug #903352 [src:pytools] pytools: FTBFS in buster/sid (dh_installdocs: Cannot
find "README")
Added tag(s) patch.
--
903352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> user debian-multime...@lists.debian.org
Setting user to debian-multime...@lists.debian.org (was jcowg...@jcowgill.uk).
> usertag 904104 ffmpeg-4.0-transition
There were no usertags set.
Usertags are now: ffmpeg-4.0-transition.
> block 896893 by
> your autopkg tests loops over all *supported* python versions, but you only
> build the extension for the *default* python3 version. Try build-depending on
> python3-all-dev instead and see that you have extensions built for both 3.6
> and
> 3.7. Building in unstable, of course.
But , I
On 22.07.2018 14:51, PICCA Frederic-Emmanuel wrote:
> Hello, Matthias,
>
> I do not understand this bug report.
>
> I use pybuild so fabio should be build for all python3 versions.
> It is now FTBFS due to a problem with the cython package already reported.
> #903909
this is unrelated.
your
Hello, Matthias,
I do not understand this bug report.
I use pybuild so fabio should be build for all python3 versions.
It is now FTBFS due to a problem with the cython package already reported.
#903909
Cheers
Frederic
Control: severity -1 important
On 2018-07-20 17:19:05, Andreas Beckmann wrote:
> Source: intel-vaapi-driver-shaders
> Version: 2.2.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Hi,
>
> intel-vaapi-driver-shaders FTBFS twice in a
Processing control commands:
> severity -1 important
Bug #904143 [src:intel-vaapi-driver-shaders] intel-vaapi-driver-shaders: make
distclean deletes src/shaders/post_processing/gen5_6/null.g6b which is not
regenerated
Severity set to 'important' from 'serious'
--
904143:
Package: src:python-fisx
Version: 1.1.4-1
Severity: serious
Tags: sid buster
python-fisx builds for the default python3 version, but tests with all
supported versions, not finding the extensions for the non-default version.
This seems to be the case for many packages packaged by this maintainer.
On Sun, Jul 22, 2018 at 01:54:47PM +0200, Salvatore Bonaccorso wrote:
> Control: tags 904255 + patch
>
>
> Dear maintainer,
>
> I've prepared an NMU for network-manager-vpnc (versioned as
> 1.2.4-7.1). It is not yet uploaded (to any delayed queue, if you want
> to do the upload yourself).
And
Package: src:python-fabio
Version: 0.6.0+dfsg-1
Severity: serious
Tags: sid buster
python-fabio builds for the default python3 version, but tests with all
supported versions, not finding the extensions for the non-default version.
Your message dated Sun, 22 Jul 2018 12:18:51 +
with message-id
and subject line Bug#897699: fixed in aeskulap 0.2.2b1+git20161206-5
has caused the Debian Bug report #897699,
regarding aeskulap: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tags 904255 + fixed-upstream
Bug #904255 [src:network-manager-vpnc] network-manager-vpnc: CVE-2018-10900:
privilege escalation
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
904255:
Control: tags 904255 + patch
Dear maintainer,
I've prepared an NMU for network-manager-vpnc (versioned as
1.2.4-7.1). It is not yet uploaded (to any delayed queue, if you want
to do the upload yourself).
Regards,
Salvatore
diff -Nru network-manager-vpnc-1.2.4/debian/changelog
Processing control commands:
> tags 904255 + patch
Bug #904255 [src:network-manager-vpnc] network-manager-vpnc: CVE-2018-10900:
privilege escalation
Ignoring request to alter tags of bug #904255 to the same tags previously set
--
904255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904255
Processing control commands:
> severity -1 serious
Bug #903923 [src:brotli] brotli: autopkgtest needs update for python3.7 in
supported versions
Severity set to 'serious' from 'normal'
--
903923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903923
Debian Bug Tracking System
Contact
Source: network-manager-vpnc
Version: 1.2.4-1
Severity: grave
Tags: patch security upstream
Hi,
The following vulnerability was published for network-manager-vpnc.
CVE-2018-10900[0]:
local privilege escalation
A user with enough privileges to create the vpnc connection entry
(group netdev for
Control: tags -1 fixed-upstream
On Fri, 04 May 2018 12:21:56 + Matthias Klose wrote:
> Package: src:hmat-oss
> Version: 1.2.0-2
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> [...]
> /<>/src/full_matrix.cpp:904:11: error: 'void*
Processing control commands:
> tags -1 fixed-upstream
Bug #897768 [src:hmat-oss] hmat-oss: ftbfs with GCC-8
Added tag(s) fixed-upstream.
--
897768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hello Andreas,
you marked these two bugs as found in insighttoolkit4/4.12.2-dfsg1-2,
but they should actually have been merged with #897899 (maybe I did
something wrong theer), a bug that was closed by exactly this version.
Could you ellaborate why do you tagged these bugs like this? I just
Processing commands for cont...@bugs.debian.org:
> forwarded 897747 https://github.com/wolfcw/libfaketime/pull/161
Bug #897747 [src:faketime] faketime: ftbfs with GCC-8
Set Bug forwarded-to-address to
'https://github.com/wolfcw/libfaketime/pull/161'.
> tags 897747 fixed-upstream
Bug #897747
Processing commands for cont...@bugs.debian.org:
> forwarded 897716 https://github.com/marbl/canu/issues/927
Bug #897716 [src:canu] canu: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/marbl/canu/issues/927'.
> tags 897716 fixed-upstream
Bug #897716 [src:canu] canu: ftbfs
On Fri, 04 May 2018 12:20:56 + Matthias Klose wrote:
> Package: src:bzrtp
> Version: 1.0.6-2
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> /<>/src/stateMachine.c: In function 'bzrtp_deriveKeysFromS0':
> /<>/src/stateMachine.c:2057:234:
Your message dated Sun, 22 Jul 2018 10:04:11 +
with message-id
and subject line Bug#903895: fixed in colord-kde 0.5.0-3
has caused the Debian Bug report #903895,
regarding colord-kde: build-depends on no longer available plasma-framework-dev
to be marked as done.
This means that you claim
Your message dated Sun, 22 Jul 2018 09:19:00 +
with message-id
and subject line Bug#903066: fixed in decopy 0.2.4.1-1
has caused the Debian Bug report #903066,
regarding decopy FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 22 Jul 2018 08:42:38 +
with message-id
and subject line Bug#897471: fixed in python-magic 2:0.4.15-2
has caused the Debian Bug report #897471,
regarding python-magic: FTBFS: dh_auto_test: pybuild --test -i python{version}
-p 2.7 returned exit code 13
to be marked as
Your message dated Sun, 22 Jul 2018 16:02:52 +0800
with message-id <20180722080251.GA20239@tx.local>
and subject line Re: ruby-bio FTBFS with ruby 2.5
has caused the Debian Bug report #890691,
regarding ruby-bio FTBFS with ruby 2.5
to be marked as done.
This means that you claim that the problem
Source: pytest-sugar
Version: 0.9.1-2
Severity: serious
Tags: ftbfs buster sid
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of pytest 3.6.2-2 to unstable, pytest-sugar's
autopkgtests have been failing [1], with
Your message dated Sun, 22 Jul 2018 06:48:48 +
with message-id
and subject line Bug#897509: fixed in git-repair 1.20151215-1.2
has caused the Debian Bug report #897509,
regarding git-repair: FTBFS: Duplicate instance declarations:
to be marked as done.
This means that you claim that the
Processing control commands:
> tags 897509 + patch
Bug #897509 [src:git-repair] git-repair: FTBFS: Duplicate instance
declarations:
Added tag(s) patch.
> tags 897509 + pending
Bug #897509 [src:git-repair] git-repair: FTBFS: Duplicate instance
declarations:
Added tag(s) pending.
--
897509:
Control: tags 897509 + patch
Control: tags 897509 + pending
Dear maintainer,
I've prepared an NMU for git-repair (versioned as 1.20151215-1.2) and
uploaded it to sid.
Regards.
--
Sean Whitton
diff -Nru git-repair-1.20151215/CHANGELOG git-repair-1.20151215/CHANGELOG
---
Am 21. Juli 2018 19:44:33 MESZ schrieb Geert Stappers :
>
>There is now an empty git repository
>at https://salsa.debian.org/electronics-team/sdcc.git
>which is intended for Debian packaging of sdcc
>
>
>Convenience links for the both bugreports in the To:
>
>
85 matches
Mail list logo
