Your message dated Fri, 11 Aug 2017 12:44:51 -0700 with message-id <87o9rlx51o.fsf@iris.silentflame.com> and subject line Closing inactive Policy bugs has caused the Debian Bug report #610298, regarding phasing out tar-in-tar in source 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.debian.org immediately.) -- 610298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610298 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: phasing out tar-in-tar in source packages
- From: Stefano Zacchiroli <zack@debian.org>
- Date: Mon, 17 Jan 2011 11:49:49 +0100
- Message-id: <20110117104949.20850.90034.reportbug@usha.takhisis.invalid>
Package: debian-policy Version: 3.9.1.0 Severity: wishlist tar-in-tar source packages, i.e. Debian source packages which contains upstream sources in compressed form and uncompress them on the fly during the build process, are a bit of a PITA. They are particularly so for tools who want to do source code analyses on the code shipped by debian (e.g. the recently started DACA project) but, more generally, violate a good faith assumption that "apt-get source" will deliver an unpacked source package where the user can grep through upstream source code. I haven't conducted an analyses of the amount of tar-in-tar source packages in the Debian archive (sorry about that), but per folklore it seems that there are very few such packages remaining in the archive. I guess this is so because tar-in-tar was mostly used to circumvent the lack of support for non-gzip compression in source packages, feature which is now provided by 3.0 source formats. Considering all the above, it would be nice if policy could start to discourage tar-in-tar, at least with a "should" (not) requirement. A potentially appropriate place where to mention that seems to be §4.8 "Restrictions on objects in source packages". Thanks for considering and many thanks in advance, Cheers. PS en passant: appendix §C.3 seems to be out of date wrt source formats 3.0, but it's not normative, so it's not a big deal -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash debian-policy depends on no packages. debian-policy recommends no packages. Versions of packages debian-policy suggests: ii doc-base 0.9.5 utilities to manage online documen -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 617938-close@bugs.debian.org, 688363-close@bugs.debian.org, 821363-close@bugs.debian.org, 192571-close@bugs.debian.org, 215549-close@bugs.debian.org, 263448-close@bugs.debian.org, 276160-close@bugs.debian.org, 408500-close@bugs.debian.org, 562863-close@bugs.debian.org, 587377-close@bugs.debian.org, 592564-close@bugs.debian.org, 656569-close@bugs.debian.org, 663917-close@bugs.debian.org, 683570-close@bugs.debian.org, 684673-close@bugs.debian.org, 697134-close@bugs.debian.org, 704233-close@bugs.debian.org, 727754-close@bugs.debian.org, 737559-close@bugs.debian.org, 795783-close@bugs.debian.org, 832654-close@bugs.debian.org, 71621-close@bugs.debian.org, 120418-close@bugs.debian.org, 267142-close@bugs.debian.org, 291631-close@bugs.debian.org, 338219-close@bugs.debian.org, 375502-close@bugs.debian.org, 391240-close@bugs.debian.org, 397939-close@bugs.debian.org, 400112-close@bugs.debian.org, 412668-close@bugs.debian.org, 431109-close@bugs.debian.org, 457364-close@bugs.debian.org, 458824-close@bugs.debian.org, 462996-close@bugs.debian.org, 465140-close@bugs.debian.org, 466550-close@bugs.debian.org, 485559-close@bugs.debian.org, 491055-close@bugs.debian.org, 492144-close@bugs.debian.org, 521810-close@bugs.debian.org, 525843-close@bugs.debian.org, 528453-close@bugs.debian.org, 535577-close@bugs.debian.org, 541872-close@bugs.debian.org, 543417-close@bugs.debian.org, 549910-close@bugs.debian.org, 554194-close@bugs.debian.org, 570141-close@bugs.debian.org, 572571-close@bugs.debian.org, 580135-close@bugs.debian.org, 593177-close@bugs.debian.org, 610298-close@bugs.debian.org, 633994-close@bugs.debian.org, 660705-close@bugs.debian.org, 642914-close@bugs.debian.org, 663762-close@bugs.debian.org, 671503-close@bugs.debian.org, 681289-close@bugs.debian.org, 685992-close@bugs.debian.org, 690495-close@bugs.debian.org, 694384-close@bugs.debian.org, 775318-close@bugs.debian.org, 798714-close@bugs.debian.org, 524461-close@bugs.debian.org, 555981-close@bugs.debian.org, 682282-close@bugs.debian.org, 686143-close@bugs.debian.org, 515837-close@bugs.debian.org, 779506-close@bugs.debian.org, 628174-close@bugs.debian.org, 661417-close@bugs.debian.org, 681562-close@bugs.debian.org, 490605-close@bugs.debian.org, 647570-close@bugs.debian.org
- Subject: Closing inactive Policy bugs
- From: Sean Whitton <spwhitton@spwhitton.name>
- Date: Fri, 11 Aug 2017 12:44:51 -0700
- Message-id: <87o9rlx51o.fsf@iris.silentflame.com>
control: user debian-policy@packages.debian.org control: usertag -1 +obsolete control: tag -1 +wontfix Russ Allbery and I did a round of in-person bug triage at DebConf17 and we are closing this bug as inactive. The reasons for closing fall into the following categories, from most frequent to least frequent: - issue is appropriate for Policy, there is a consensus on how to fix the problem, but preparing the patch is very time-consuming and no-one has volunteered to do it, and we do not judge the issue to be important enough to keep an open bug around; - issue is appropriate for Policy but there does not yet exist a consensus on what should change, and no recent discussion. A fresh discussion might allow us to reach consensus, and the messages in the old bug are unlikely to help very much; or - issue is not appropriate for Policy. If you feel this bug is still relevant and want to restart the discussion, you can re-open the bug. However, please consider instead opening a new bug with a message that summarises and condenses the previous discussion, updates the report for the current state of Debian, and makes clear exactly what you think should change. A lot of these old bugs have long side tangents and numerous messages, and that old discussion is not necessarily helpful for figuring out what Debian Policy should say today. -- Sean WhittonAttachment: signature.asc
Description: PGP signature
--- End Message ---