On Sat, Jun 15, 2019 at 09:01:46PM +0800, Paul Wise wrote:
> On Thu, 2019-06-06 at 10:20 +, Holger Levsen wrote:
> > - new upstream version only available in experimental (yes, because
> > buster is frozen)
> Do you have an example of a package where this should be hidden?
> I'd like to see t
On Thu, 2019-06-06 at 10:20 +, Holger Levsen wrote:
> - new upstream version only available in experimental (yes, because
> buster is frozen)
Do you have an example of a package where this should be hidden?
I'd like to see the issue in context to understand it more clearly.
--
bye,
pabs
On Sat, 2019-06-15 at 13:06 +0100, Jonathan Wiltshire wrote:
> Here's a draft of what it could look like, does this satisfy the
> requirements?
I think I would put the planned_release into the stages.
I wonder if the set of stages and their meaning will be the same for
every release, i.e. should
On Sat, Jun 15, 2019 at 01:17:51AM +0800, Paul Wise wrote:
> In order to implement the request below (hide some suggestions from
> tracker.d.o during the freeze (and possibly other things)), we need a
> machine-readable information source about the current stage of the
> freeze and what that means
On Sat, 15 Jun 2019, Raphael Hertzog wrote:
> I also don't know why you picked this bug report to start your journey
> into distro-tracker. It's not a trivial issue to fix and the added value
> is relatively low compared to other missing features.
>
> I took the time to highlight easy bugs with th
On Sat, 15 Jun 2019, Paul Wise wrote:
> On Fri, 2019-06-14 at 16:13 -0300, Herbert Fortes wrote:
>
> > Should dm.txt file be downloaded and read once a day?
> > (to update/save new info)
>
> I note there is already code in RetrieveDebianMaintainersTask that
> downloads and processes dm.txt so per
6 matches
Mail list logo
