Fabio Valentini writes:
> On Sat, Dec 7, 2019, 17:30 Mattia Verga via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Il 06/12/19 21:51, Johannes Lips ha scritto:
>> >> "Johannes Lips" > >>
>> >>
>> >> We already have a tool for reporting issues and problems, and it's not
>> >> bodhi. If
On Sun, 2019-12-08 at 08:51 +, Mattia Verga via devel wrote:
> Il 07/12/19 19:32, Adam Williamson ha scritto:
> > But we already explained this. Comments on stable updates are not
> > primarily for the maintainer, they are for *users*. Users tend to refer
> > to Bodhi notes, if anything, more
Il 07/12/19 19:32, Adam Williamson ha scritto:
> But we already explained this. Comments on stable updates are not
> primarily for the maintainer, they are for *users*. Users tend to refer
> to Bodhi notes, if anything, more than maintainers do.
>
...and that's exactly the behavior that the change
On Sat, 2019-12-07 at 10:46 -0700, Jerry James wrote:
> On Sat, Dec 7, 2019 at 9:50 AM Fabio Valentini wrote:
>
> > I'm curious about this. I do get email notifications for all changes and
> > comments for all my own bodhi updates plus for every update that I
> > commented on. Have you turned
On Sat, 2019-12-07 at 10:46 -0700, Jerry James wrote:
> On Sat, Dec 7, 2019 at 9:50 AM Fabio Valentini wrote:
>
> > I'm curious about this. I do get email notifications for all changes and
> > comments for all my own bodhi updates plus for every update that I
> > commented on. Have you turned
On Sat, Dec 7, 2019 at 9:50 AM Fabio Valentini wrote:
> I'm curious about this. I do get email notifications for all changes and
> comments for all my own bodhi updates plus for every update that I
> commented on. Have you turned this off, or do you mean to say you're going
> to ignore bodhi
Il 07/12/19 17:49, Fabio Valentini ha scritto:
> I'm curious about this. I do get email notifications for all changes and
> comments for all my own bodhi updates plus for every update that I commented
> on. Have you turned this off, or do you mean to say you're going to ignore
> bodhi emails?
On Sat, Dec 7, 2019, 17:30 Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:
> Il 06/12/19 21:51, Johannes Lips ha scritto:
> >> "Johannes Lips" >>
> >>
> >> We already have a tool for reporting issues and problems, and it's not
> >> bodhi. If there's a problem with an already
Il 06/12/19 21:51, Johannes Lips ha scritto:
>> "Johannes Lips" >
>>
>> We already have a tool for reporting issues and problems, and it's not
>> bodhi. If there's a problem with an already pushed update, it needs to
>> be in bugzilla - where it's actually discoverable - not in bodhi, where
>> it
Fabio Valentini wrote:
> Right. So should the default of -3/+3 be changed for "critpath" packages?
> They already need 14 days in testing, but they also get orders of
> magnitude more feedback, so raising the karma limits to -2/+6 or something
> like that sounds reasonable to me.
>
> On the other
On Fri, 2019-12-06 at 20:51 +, Johannes Lips wrote:
> > "Johannes Lips" >
> >
> > We already have a tool for reporting issues and problems, and it's not
> > bodhi. If there's a problem with an already pushed update, it needs to
> > be in bugzilla - where it's actually discoverable - not in
> "Johannes Lips"
>
> We already have a tool for reporting issues and problems, and it's not
> bodhi. If there's a problem with an already pushed update, it needs to
> be in bugzilla - where it's actually discoverable - not in bodhi, where
> it will go nowhere.
I am not intending to use bodhi
"Johannes Lips" writes:
> What I found weird is that you can't comment on an update, which is
> already pushed to stable. A lot of users are only hit by a bug, once
> it reaches stable and then you don't have any possibility to highlight
> a bug report or an issue with this update. I would like
On Fri, 2019-12-06 at 06:34 +, Johannes Lips wrote:
> Hi all,
>
> I was recently bit by a bug, which was caused by a mismatch between
> texlive-biblatex and biber. The technical side is not so important,
> only so much that they need each other in a pretty specific version,
> which is not
On Friday, 06 December 2019 at 10:57, Petr Pisar wrote:
[...]
> Maybe DNF could support setting a prefered mirror while still checking
> for the latest metadata because in my experience the automatic mirror
> selection does not always provide the best performance. (E.g. when
> I connected an IPv6
On 2019-12-06, Johannes Lips wrote:
> It really depends which mirrors you are using and if you are unlucky
> the updates get pushed to stable, before it reaches updates-testing
> for you and then again there's nothing to add, once it's pushed.
>
If you use metalink in your repository
On Fri, Dec 06, 2019 at 07:51:40AM +0100, Fabio Valentini wrote:
>On Fri, Dec 6, 2019, 07:35 Johannes Lips <[1]johannes.l...@gmail.com>
>wrote:
>
> Hi all,
>
> I was recently bit by a bug, which was caused by a mismatch between
> texlive-biblatex and biber. The technical
On Fri, Dec 6, 2019, 08:46 Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:
> Il 06/12/19 07:34, Johannes Lips ha scritto:
> > Hi all,
> >
> > I was recently bit by a bug, which was caused by a mismatch between
> texlive-biblatex and biber. The technical side is not so important,
Il 06/12/19 07:34, Johannes Lips ha scritto:
> Hi all,
>
> I was recently bit by a bug, which was caused by a mismatch between
> texlive-biblatex and biber. The technical side is not so important, only so
> much that they need each other in a pretty specific version, which is not
> reflected on
On Fri, Dec 6, 2019, 07:35 Johannes Lips wrote:
> Hi all,
>
> I was recently bit by a bug, which was caused by a mismatch between
> texlive-biblatex and biber. The technical side is not so important, only so
> much that they need each other in a pretty specific version, which is not
> reflected
Hi all,
I was recently bit by a bug, which was caused by a mismatch between
texlive-biblatex and biber. The technical side is not so important, only so
much that they need each other in a pretty specific version, which is not
reflected on the rpm level.
What I found weird is that you can't
21 matches
Mail list logo
