Bug#859554: pidgin-openfetion: Please migrate to openssl1.1 in buster

X-Debbugs-CC: a...@debian.org sebast...@breakpoint.cc 在 2017年10月12日星期四 CST 下午11:44:37，Sebastian Andrzej Siewior 写道： > Hi, > > this is a remainder about the openssl transition [0]. We really want to > remove libssl1.0-dev from unstable for Buster. I will raise the severity > of this bug to

Bug#859791: wvstreams: Please migrate to openssl1.1 in Buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#870775: boxbackup: Please migrate to openssl1.1 in Buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#870779: pev: Please migrate to openssl1.1 in Buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859786: vtun: Please migrate to openssl1.1 in Buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859783: turnserver: Please migrate to openssl1.1 in Buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859556: polygraph: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859554: pidgin-openfetion: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859228: mod-authn-webid: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#859146: linuxdcpp: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#858929: ike: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

Bug#851081: ekg2: Please migrate to openssl1.1 in buster

Hi, this is a remainder about the openssl transition [0]. We really want to remove libssl1.0-dev from unstable for Buster. I will raise the severity of this bug to serious in a month. Please react before that happens. [0] https://bugs.debian.org/871056#55 Sebastian

gnome-mime-data_2.18.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Oct 2017 22:38:08 +0200 Source: gnome-mime-data Binary: gnome-mime-data Architecture: source all Version: 2.18.0-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group

Processing of gnome-mime-data_2.18.0-2_amd64.changes

gnome-mime-data_2.18.0-2_amd64.changes uploaded successfully to localhost along with the files: gnome-mime-data_2.18.0-2.dsc gnome-mime-data_2.18.0-2.diff.gz gnome-mime-data_2.18.0-2_all.deb gnome-mime-data_2.18.0-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on

xchain_1.0.1-9_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Oct 2017 20:12:24 +0200 Source: xchain Binary: xchain Architecture: source Version: 1.0.1-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski

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

Your message dated Thu, 12 Oct 2017 18:48:47 + with message-id and subject line Bug#878090: fixed in xchain 1.0.1-9 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

Processing of xchain_1.0.1-9_source.changes

xchain_1.0.1-9_source.changes uploaded successfully to localhost along with the files: xchain_1.0.1-9.dsc xchain_1.0.1-9.debian.tar.xz xchain_1.0.1-9_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#878090: xchain: Couldn't execute /usr/bin/wish

Control: reopen -1 On Thu, Oct 12, 2017 at 06:58:04PM +0200, Andreas Ronnquist wrote: > After updating xchain to 1.0.1-8 in unstable, I cannot run it - it says > > "Couldn't execute /usr/bin/wish8.5" > > - Before the update it worked just fine. > > I believe this is because I had the wish

Processed: Re: xchain: Couldn't execute /usr/bin/wish

Processing control commands: > reopen -1 Bug #878090 {Done: Adam Borowski } [xchain] xchain: Couldn't execute /usr/bin/wish '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. Bug

Bug#878090: xchain: Couldn't execute /usr/bin/wish

After updating xchain to 1.0.1-8 in unstable, I cannot run it - it says "Couldn't execute /usr/bin/wish8.5" - Before the update it worked just fine. I believe this is because I had the wish which is provided by the tk package wish provide a /usr/bin/wish, and xchain is depending on either

xchain_1.0.1-8_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Oct 2017 09:14:07 +0200 Source: xchain Binary: xchain Architecture: source Version: 1.0.1-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski

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

Your message dated Thu, 12 Oct 2017 07:52:03 + with message-id and subject line Bug#878090: fixed in xchain 1.0.1-8 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

Processing of xchain_1.0.1-8_source.changes

xchain_1.0.1-8_source.changes uploaded successfully to localhost along with the files: xchain_1.0.1-8.dsc xchain_1.0.1-8.debian.tar.xz xchain_1.0.1-8_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

moon-lander_1.0-6_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Oct 2017 07:57:17 +0200 Source: moon-lander Binary: moon-lander moon-lander-data Architecture: source Version: 1:1.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group

Processing of moon-lander_1.0-6_source.changes

moon-lander_1.0-6_source.changes uploaded successfully to localhost along with the files: moon-lander_1.0-6.dsc moon-lander_1.0-6.debian.tar.xz moon-lander_1.0-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)