[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1063650: marked as done (reportbug: add menu to select port/arch usertags)

Your message dated Sun, 16 Feb 2025 11:11:08 +0000
with message-id <E1tjcYG-00BYLA-B9@fasolo.debian.org>
and subject line Bug#1063650: fixed in reportbug 13.0.3
has caused the Debian Bug report #1063650,
regarding reportbug: add menu to select port/arch usertags
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.debian.org
immediately.)


-- 
1063650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063650
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Severity: wishlist

I have been working on an enhancement[1] to reportbug that would allow
interactive selection of port/arch usertags[2] and automatically set
them in code paths that currently already ask for an architecture.

I could use some design advice around the data for this.

Currently the canonical definitions of the tags is the wiki page. The
reportbug patchset has a function to convert the wiki page to Python
objects. Then the reportbug code has a copy of the autogenerated Python
objects. However, in keeping with the spirit of what I wrote on [3],
I intend to switch that to storing a full copy of the raw source for
the wiki page in the reportbug source and then doing the conversion
at build time. There is similar data needed from [4] and [5].

Since the copy of the data in reportbug would get outdated, I was
thinking to download new copies when in online mode, cache them locally
and then use them in preference to the copy in the reportbug package.
This would happen only for code paths that do arch selection of course.

Does this feature and approach to data caching sound reasonable?

   1. https://salsa.debian.org/pabs/reportbug/-
      /compare?from=master&to=arch-usertags
   2. https://wiki.debian.org/Teams/Debbugs/ArchitectureTags
   3. https://wiki.debian.org/AutoGeneratedFiles
   4. https://salsa.debian.org/webmaster-team/webwml/-
      /raw/master/english/releases/arches.data
   5. The 'vancouvered' column in the buildd database, currently only
      at postgresql://udd-mirror:udd-mirror@udd-mirror.debian.net/udd

-- 
bye, pabs https://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Source: reportbug
Source-Version: 13.0.3
Done: Nis Martensen <nis.martensen@web.de>

We believe that the bug you reported is fixed in the latest version of
reportbug, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063650@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nis Martensen <nis.martensen@web.de> (supplier of updated reportbug package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 16 Feb 2025 11:31:05 +0100
Source: reportbug
Architecture: source
Version: 13.0.3
Distribution: unstable
Urgency: medium
Maintainer: Reportbug Maintainers <debian-reportbug@lists.debian.org>
Changed-By: Nis Martensen <nis.martensen@web.de>
Closes: 1063650
Changes:
 reportbug (13.0.3) unstable; urgency=medium
 .
   [ Paul Wise ]
   * Add support for removing tags when editing the tags
   * Add ftbfs tag to more FTBFS bugs based on bug subject
   * Add debian-boot to X-Debbugs-CC for d-i tagged bugs
   * Add menu for setting architecture User/Usertags/X-Debbugs-CC (Closes: #1063650)
   * Use arch menu for ftp/release arch-specific removals/binNMUs
   * Switch to all-arches binNMU for Multi-Arch: same packages
 .
   [ Nis Martensen ]
   * Makefile, reportbug/debbugs.py: add some comments
Checksums-Sha1:
 6dc0d0d4808ff97cb1f00800b5ba3e4d628c5e58 1888 reportbug_13.0.3.dsc
 dbda5f3c91a6b251dbbde6d4559613c5ce132087 220152 reportbug_13.0.3.tar.xz
 dba90aee1ae2c69f01f269536879065769f143c2 7930 reportbug_13.0.3_amd64.buildinfo
Checksums-Sha256:
 dfa1de5638ac7d84b50e150021564e72b6f1046b1f9f6d50c2205040eec8dff0 1888 reportbug_13.0.3.dsc
 9bfa3a981d51f9d27cfa5b8542e8739edfdc4eec39f7845a47df3e11caed6d71 220152 reportbug_13.0.3.tar.xz
 8e762e2d60715f1171a39b11ae4722e42cb4d4ecc81aff2b6dab563a41226d55 7930 reportbug_13.0.3_amd64.buildinfo
Files:
 792022a09fe589dd322408fc2fb6415e 1888 utils standard reportbug_13.0.3.dsc
 424143397ac5d6bf71ff9727ed135111 220152 utils standard reportbug_13.0.3.tar.xz
 cf270825a368b40e8c349a7b4238f5d9 7930 utils standard reportbug_13.0.3_amd64.buildinfo

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

iQIzBAEBCAAdFiEElwagcOR0bw2C8YAgINUE/crqn1AFAmexv6sACgkQINUE/crq
n1CcGg/9E/ktmF2ClHTG4xma0cOkopkSBXLRfkKeMqTzh0/GEDiInzTUfeMqJWf6
87D7+2dV+hpvwPMLViV2jJzYoJTYOp0bGWuT5mkaqQPCp2Y2kDtoOCNZN0Tc8ezJ
zbZGX3iZ7eXxmJy2aA9w+XmlySufAeUtmgBFU6twarDMNAVeoOfVSMPryyqytUhK
p6J4ofoSbfVPISHZTZumqxk17U40BGggdM7SRZQ2e3PE8Sydp5zW1WNskU+AHSSb
NoniPDa85XrjdS5KIT3NNFFa3h+QVZJi1U20sT0ZF1hiS8l9dkWowlHyalVEEuPU
l4g07SikHUgfVoWmC6ip2S6uQWQvNQMRmMirdttFJPdt3Ms0XfrMl/V9JcAdp1Ug
+y8rx4n0wy1VaPu6wUWpI9tTjACk8plaWYk8gVRh4zpeo0Z3ddgWZsSK0sz/m1uY
ihIrKun4L0+r7cEHD9MhaVaAnDWTeGcrMCMETDCJvzF4d0/t1qH51N26NturE1HJ
APopiBSLPX+NZhJE/lBNwOMYN7zCr/Es3D2TACGTJpJTHL4wGEdNATCh2m5dXvmt
iriKdvu+u0aZSzxleN8fPBIJk74hFa98U7RVHKOhn3wa2EBzu20B00D9oolXScFV
HxQl2mRjpfVGcm8v3VQCNF2AAdcSuv0gywIofcihY3L8AVRpObA=
=lJjg
-----END PGP SIGNATURE-----

Attachment: pgpz5s0dc4nk4.pgp
Description: PGP signature


--- End Message ---
Reply to: