Bug#758234: Raising priority of Debian packages
- To: debian-devel@lists.debian.org, 758234@bugs.debian.org
- Subject: Bug#758234: Raising priority of Debian packages
- From: Jakub Wilk <jwilk@debian.org>
- Date: Thu, 4 Sep 2014 21:35:55 +0200
- Message-id: <[🔎] 20140904193554.GA3046@jwilk.net>
- Reply-to: Jakub Wilk <jwilk@debian.org>, 758234@bugs.debian.org
- In-reply-to: <87tx4sy73x.fsf@hope.eyrie.org>
- References: <53EE30EC.7000102@debian.org> <53EE35EB.4060601@debian.org> <20140815165144.GB27464@yellowpig> <20140815172731.2308.qmail@581c3f36e438e4.315fe32.mid.smarden.org> <20140830073110.28052.qmail@353a9a2a72ded5.315fe32.mid.smarden.org> <87vbpadjom.fsf@hope.eyrie.org> <20140831074322.30727.qmail@da21230e36abc3.315fe32.mid.smarden.org> <8738cczmoo.fsf@hope.eyrie.org> <CAKTje6GZfiSnis__cex-rqqSzNUViT6oBugd3_Xq4iNH-_SVBQ@mail.gmail.com> <87tx4sy73x.fsf@hope.eyrie.org>
* Russ Allbery <rra@debian.org>, 2014-08-31, 09:08:
If we want, as a project, to monitor the size of the required,
important, and standard sets, I feel like we should do that directly:
run a cron job somewhere that remembers the previous size, calculates
the new transitive closure, and mails out a report once a week or month
or something listing which packages were added or removed and their
sizes, as well as the total installed size of each of those sets. I
think that would be more effective and more directly on point than
mucking about with trying to monitor priority changes.
Yes, that would be a good idea.
We should probably also monitor package conflicts. We made a big fuss
about node vs nodejs (and rightly so); but I bet that we have lots of
other package pairs in the archive that can't be co-installed for no
good reason.
--
Jakub Wilk
Reply to: