Devuan bug report logs - #656
reportbug: Adding check for debian imported packages

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: dak@devuan.org
Subject: bug#656: marked as done (reportbug: Adding check for debian
 imported packages)
Message-ID: <handler.656.D656.164555164125078.ackdone@bugs.devuan.org>
References: <1645551573.798366.4439.nullmailer@dak.localnet.devuan.org>
 <164234718957.11783.13125556123318352941.reportbug@enous>
X-Devuan-PR-Message: closed 656
X-Devuan-PR-Package: reportbug
X-Devuan-PR-Keywords: patch
Reply-To: 656@bugs.devuan.org
Date: Tue, 22 Feb 2022 17:42:07 +0000
Content-Type: multipart/mixed; boundary="----------=_1645551727-25091-0"

[Message part 1 (text/plain, inline)]

Your message dated Tue, 22 Feb 2022 17:39:33 +0000
with message-id <1645551573.798366.4439.nullmailer@dak.localnet.devuan.org>
and subject line #656: fixed in src:reportbug version 11.4.0devuan2
has caused the Devuan bug report #656,
regarding reportbug: Adding check for debian imported packages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)


-- 
656: https://bugs.devuan.org/cgi/bugreport.cgi?bug=656
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Alexandros Prekates <aprekates@posteo.net>

To: Devuan Bug Tracking System <submit@bugs.devuan.org>

Subject: reportbug: Adding check for debian imported packages

Date: Sun, 16 Jan 2022 15:33:09 +0000

Package: reportbug
Version: 7.10.3+devuan1
Severity: normal

Dear Maintainer,

 i think it would be more user friendly :-)  reportbug to check if a package is
unforked , because now the sender must crosscheck for if the package s(he)
reports for is unforked and imported from debian and then
to launch reportbug with --bts debian


-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/chomwitt/.reportbugrc:
reportbug_version "7.10.3+devuan1"
mode standard
ui gtk
email "aprekates@posteo.net"
smtphost "posteo.de"
smtpuser "aprekates@posteo.net"
smtptls

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 4 (chimaera)
Release:	4
Codename:	n/a
Architecture: x86_64

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                2.2.4+devuan1
ii  python3            3.9.2-3
ii  python3-reportbug  7.10.3+devuan1
ii  sensible-utils     0.0.14

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail                                 3.17.8-1+b1
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
ii  emacs-bin-common                           1:27.1+1-3.1
ii  exim4-daemon-light [mail-transport-agent]  4.94.2-6
ii  file                                       1:5.39-3
ii  gnupg                                      2.2.27-2
pn  python3-urwid                              <none>
ii  reportbug-gtk                              7.10.3+devuan1
ii  xdg-utils                                  1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt                2.2.4+devuan1
ii  file               1:5.39-3
ii  python3            3.9.2-3
ii  python3-apt        2.2.1
ii  python3-debian     0.1.39
ii  python3-debianbts  3.1.0
ii  python3-requests   2.25.1+dfsg-2
ii  sensible-utils     0.0.14

python3-reportbug suggests no packages.

-- no debconf information

[Message part 3 (message/rfc822, inline)]

From: dak@devuan.org

To: 656-done@bugs.devuan.org

Subject: #656: fixed in src:reportbug version 11.4.0devuan2

Date: Tue, 22 Feb 2022 17:39:33 +0000

Version: 11.4.0devuan2

Source package reportbug (11.4.0devuan2) added to Devuan suite unstable.

This closes bug report 656.

Thanks

DAK managing the Devuan archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 21 Feb 2022 11:22:39 +0000
Source: reportbug
Architecture: source
Version: 11.4.0devuan2
Distribution: unstable
Urgency: medium
Maintainer: Mark Hindley <mark@hindley.org.uk>
Changed-By: Mark Hindley <mark@hindley.org.uk>
Closes: 381 656
Changes:
 reportbug (11.4.0devuan2) unstable; urgency=medium
 .
   * Revert "Send to Devuan BTS by default (Closes: #381)." This change is
     no longer required now lsb_release returns the correct Distributor ID.
   * Offer to send bugs in unforked packages directly to Debian, but still
     default to Devuan. (Closes: #656)
Checksums-Sha1:
 2a27ef5d2064600ef027963a747165fe90737068 1523 reportbug_11.4.0devuan2.dsc
 b7c54b1c0a50db7e59d643153e3e34ec298356fb 206416 reportbug_11.4.0devuan2.tar.xz
 adbee16e246aa010529899790ecbb267eb74ed1d 5616 reportbug_11.4.0devuan2_source.buildinfo
Checksums-Sha256:
 f78aeafe86411c5ae2a9dab723063d287c5f403feaeefc7a93261674f2ee93a0 1523 reportbug_11.4.0devuan2.dsc
 6b4d1e4bc0330bd17762989a7f5d2afa788df43ea817c84b1495b26549723e74 206416 reportbug_11.4.0devuan2.tar.xz
 1052cd0015a5da30b5454e50044d59acd9106f03cbda716005531429adbfb754 5616 reportbug_11.4.0devuan2_source.buildinfo
Files:
 061f290ea505acee8baffc6b804b8711 1523 utils standard reportbug_11.4.0devuan2.dsc
 e8deda0f0179d68a9d461d8e82696ed0 206416 utils standard reportbug_11.4.0devuan2.tar.xz
 fcfc3dee5b6dcb137d336ecfc9274d27 5616 utils standard reportbug_11.4.0devuan2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEcuPLdzMV36LkZHQ9lFMhJFQZIvsFAmIVH2MACgkQlFMhJFQZ
IvtM8wf5AZs3UpBJuUXKVXi3+4MTdZf3PlT5FpbYlg4bJrXz+pHGj5WUxyNdWHuF
xCFS8KcYhze5UV46BLnbkryQdUN/Kv+JykO9YL2lyLryjO/Hrutgooi3nyY6w0uS
ZcHb01MW8YKXhp7WEV0KsSPDvf8pqJe73xxisks6M6tgwGJ1H6am1c96UDFLtMq9
I0VgHi/NEkPMlUKHilWyzN763Vvft8otVlcLL7bDxy5Pxbi1rUeRINfNDvRoXH4F
S7P+RZ4w/66AT+h8pJhP0xPs54wygbdeeRlNiwRsiQQu2H+OvPi8fQCmXnT6WUIe
hPFdN7ldOIuEtK/l9F8ONpf/f8MUXA==
=Xp6s
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.