Bug#423587: marked as done (referencer: should not overwrite user-supplied metadata with data from online sources)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #423587, regarding referencer: should not overwrite user-supplied metadata with data from online sources to be marked as done. This me

Bug#470302: marked as done (referencer: Referencer could use bibutils already in Debian)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #470302, regarding referencer: Referencer could use bibutils already in Debian to be marked as done. This means that you claim that the

Bug#531711: marked as done (referencer: Allow directories as "paper files")

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #531711, regarding referencer: Allow directories as "paper files" to be marked as done. This means that you claim that the problem has

Bug#531713: marked as done (referencer: .reflib files are locale dependent)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #531713, regarding referencer: .reflib files are locale dependent to be marked as done. This means that you claim that the problem has

Bug#423586: marked as done (referencer: PDF-scraping for DOIs sometimes cuts them off in the middle)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #423586, regarding referencer: PDF-scraping for DOIs sometimes cuts them off in the middle to be marked as done. This means that you c

Bug#597811: marked as done (referencer: DOI metadata look-up failes)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #597811, regarding referencer: DOI metadata look-up failes to be marked as done. This means that you claim that the problem has been de

Bug#780916: marked as done (referencer: File association icon too large)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #780916, regarding referencer: File association icon too large to be marked as done. This means that you claim that the problem has bee

Bug#585349: marked as done (referencer: Python string exceptions no more allowed in Python 2.6)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #585349, regarding referencer: Python string exceptions no more allowed in Python 2.6 to be marked as done. This means that you claim t

Bug#739689: marked as done (PubMed ID metadata loop-up fails)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #739689, regarding PubMed ID metadata loop-up fails to be marked as done. This means that you claim that the problem has been dealt wit

Bug#633632: marked as done ([referencer] Clean target fails after build while unapplying patches)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #633632, regarding [referencer] Clean target fails after build while unapplying patches to be marked as done. This means that you claim

Bug#761235: marked as done (referencer not cleaning up the bibtex entries makes the library unusable)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #761235, regarding referencer not cleaning up the bibtex entries makes the library unusable to be marked as done. This means that you

Bug#780918: marked as done (referencer: Menu icon not vector-based)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #780918, regarding referencer: Menu icon not vector-based to be marked as done. This means that you claim that the problem has been dea

Bug#588703: marked as done (referencer: online help (DE) not usable, because all links on startpage are broken)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #588703, regarding referencer: online help (DE) not usable, because all links on startpage are broken to be marked as done. This means

Bug#722680: marked as done (fails to import a directory structure)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #722680, regarding fails to import a directory structure to be marked as done. This means that you claim that the problem has been deal

Bug#633631: marked as done ([referencer] Cleanup for referencer.desktop)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #633631, regarding [referencer] Cleanup for referencer.desktop to be marked as done. This means that you claim that the problem has bee

Bug#829771: marked as done (referencer: Uses deprecated gnome-common macros/variables)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #829771, regarding referencer: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that the p

Bug#885039: marked as done (referencer: Please don't (Build-)Depend on gconfmm2.6)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #885039, regarding referencer: Please don't (Build-)Depend on gconfmm2.6 to be marked as done. This means that you claim that the probl

Bug#820618: marked as done (referencer: please enable parallel building)

Your message dated Sat, 03 Mar 2018 10:05:45 + with message-id and subject line Bug#891699: Removed package(s) from unstable has caused the Debian Bug report #820618, regarding referencer: please enable parallel building to be marked as done. This means that you claim that the problem has bee

Bug#891699: Removed package(s) from unstable

Version: 1.2.2-2+rm Dear submitter, as the package referencer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/891699 Th

Bug#891699: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: referencer |1.2.2-2 | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x --- Reason --

Accepted xchain 1.0.1-9~deb9u1 (source) into proposed-updates->stable-new, proposed-updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 Mar 2018 20:03:17 +0100 Source: xchain Binary: xchain Architecture: source Version: 1.0.1-9~deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Description: xchain - s

Bug#878090: marked as done (xchain: Couldn't execute /usr/bin/wish)

Your message dated Sat, 03 Mar 2018 11:02:19 + with message-id and subject line Bug#878090: fixed in xchain 1.0.1-9~deb9u1 has caused the Debian Bug report #878090, regarding xchain: Couldn't execute /usr/bin/wish to be marked as done. This means that you claim that the problem has been dealt

xchain_1.0.1-9~deb9u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 Mar 2018 20:03:17 +0100 Source: xchain Binary: xchain Architecture: source Version: 1.0.1-9~deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Description: x

Accepted boxbackup 0.13~~git20180303.g6178fd34-1 (amd64 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 03 Mar 2018 14:08:09 -0500 Source: boxbackup Binary: boxbackup-server boxbackup-client Architecture: amd64 source Version: 0.13~~git20180303.g6178fd34-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Change

Processing of boxbackup_0.13~~git20180303.g6178fd34-1_multi.changes

boxbackup_0.13~~git20180303.g6178fd34-1_multi.changes uploaded successfully to localhost along with the files: boxbackup_0.13~~git20180303.g6178fd34-1.dsc boxbackup_0.13~~git20180303.g6178fd34.orig.tar.gz boxbackup_0.13~~git20180303.g6178fd34-1.debian.tar.xz boxbackup-client-dbgsym_0.13~~g

Bug#870775: marked as done (boxbackup: Please migrate to openssl1.1 in Buster)

Your message dated Sat, 03 Mar 2018 19:34:43 + with message-id and subject line Bug#870775: fixed in boxbackup 0.13~~git20180303.g6178fd34-1 has caused the Debian Bug report #870775, regarding boxbackup: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim th

boxbackup_0.13~~git20180303.g6178fd34-1_multi.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 03 Mar 2018 14:08:09 -0500 Source: boxbackup Binary: boxbackup-server boxbackup-client Architecture: amd64 source Version: 0.13~~git20180303.g6178fd34-1 Distribution: unstable Urgency: medium Maintainer: Debian QA

golang-github-gopherjs-gopherjs is marked for autoremoval from testing

golang-github-gopherjs-gopherjs 0.0~git20170927.0.4152256-5 is marked for autoremoval from testing on 2018-03-21 It is affected by these RC bugs: 890931: golang-github-gopherjs-gopherjs: golang-github-gopherjs-gopherjs FTBFS with golang-1.10-go: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_9___

golang-github-go-macaron-csrf is marked for autoremoval from testing

golang-github-go-macaron-csrf 0.0~git20170207.0.428b7c6-4 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

golang-gopkg-editorconfig-editorconfig-core-go.v1 is marked for autoremoval from testing

golang-gopkg-editorconfig-editorconfig-core-go.v1 1.2.0-4 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

premail is marked for autoremoval from testing

premail 0.46-10 is marked for autoremoval from testing on 2018-03-20 It (build-)depends on packages with these RC bugs: 889534: libaddresses0: Missing dependencies 889536: libaddressview0: Missing dependencies

golang-github-go-macaron-toolbox is marked for autoremoval from testing

golang-github-go-macaron-toolbox 0.0~git20170220.0.6766b8f-5 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

golang-github-unknwon-i18n is marked for autoremoval from testing

golang-github-unknwon-i18n 0.0~git20170218.0.8372b90-7 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

golang-github-go-macaron-i18n is marked for autoremoval from testing

golang-github-go-macaron-i18n 0.0~git20160612.0.ef57533-6 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

golang-github-go-macaron-bindata is marked for autoremoval from testing

golang-github-go-macaron-bindata 0.0~git20161222.0.85786f5-4 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

abiword is marked for autoremoval from testing

abiword 3.0.2-5 is marked for autoremoval from testing on 2018-04-08 It (build-)depends on packages with these RC bugs: 891258: wv: wvSummary Segmentation fault (core dumped) when ran on any supported file format.

golang-github-go-macaron-captcha is marked for autoremoval from testing

golang-github-go-macaron-captcha 0.0~git20170330.0.cbfb9d9-4 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go

golang-github-go-macaron-cache is marked for autoremoval from testing

golang-github-go-macaron-cache 0.0~git20151013.0.5617353-4 is marked for autoremoval from testing on 2018-04-05 It (build-)depends on packages with these RC bugs: 890936: golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go