On 2017-07-21 19:06, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> > On 2017-07-22 00:23, Ralph Ronnquist wrote:
> > > Boruch Baum wrote on 21/07/17 23:50:
> > > > Where else should I be looking?
> > >
> > > Perhaps you've set "APT::Default-Release "jessie";" ?
>
On Fri, 21 Jul 2017 22:21:53 -0400, Hendrik wrote in message
<20170722022153.gb8...@topoi.pooq.com>:
> On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
>
> > The bad news is that if this is the only step I take, "apt-get" will
> > want to upgrade 1248 packages (it looks more
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> The bad news is that if this is the only step I take, "apt-get" will
> want to upgrade 1248 packages (it looks more impressive when I write it
> out . . One Thousand, Two Hundred and Forty Eight packages) with a
> download size of 608
I wrote:
> All the time, a lot of people we stood on the sidelines willing them to fail.
Oops, s/we/were/
Personally I was watching and thinking "that's one hell of a task, I'm a bit
sceptical* but I sure as heck hope they manage it".
* Not knowing who these veterans were, and their level of
Boruch Baum wrote:
> The bad news is that if this is the only step I take, "apt-get" will
> want to upgrade 1248 packages (it looks more impressive when I write it
> out . . One Thousand, Two Hundred and Forty Eight packages) with a
> download size of 608 Mb.
What if,
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote:
> On 2017-07-22 00:23, Ralph Ronnquist wrote:
> > Boruch Baum wrote on 21/07/17 23:50:
> > > Where else should I be looking?
> >
> > Perhaps you've set "APT::Default-Release "jessie";" ?
> >
> > Without that, you'll get the more balanced
On 2017-07-22 00:23, Ralph Ronnquist wrote:
> Boruch Baum wrote on 21/07/17 23:50:
> > Where else should I be looking?
>
> Perhaps you've set "APT::Default-Release "jessie";" ?
>
> Without that, you'll get the more balanced pinning of 500 and 100.
> I think I saw some Debian bug report (on apt?)
Boruch Baum wrote on 21/07/17 23:50:
On 2017-07-21 14:14, KatolaZ wrote:
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
Just to clarify, and since you are talking about "default" pin levels:
the default pin level of standard Devuan repositories is 500. The
default for backports
On Fri, Jul 21, 2017 at 09:40:27AM -0400, Boruch Baum wrote:
[cut]
>
> 2] Isn't it a legitimate devuan package from a legitimate currently
>supported devuan repository?
if you are not using the 6.6.3+devuan1.3 version, then it's not a
package in a legitimate currently supported devuna
On 2017-07-21 14:14, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
>
> Just to clarify, and since you are talking about "default" pin levels:
> the default pin level of standard Devuan repositories is 500. The
> default for backports and experimental is 100. So I
On 2017-07-21 14:01, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote:
> > On 2017-07-21 13:24, KatolaZ wrote:
> > > Please check this first, since dozens of people are using reportbug
> > > from jessie, and their bugs are correctly reported to bugs.devuan.org.
> >
> >
On 2017-07-21 13:57, KatolaZ wrote:
> On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
> > Thanks for a quick response.
> >
> >
> > On 2017-07-21 13:24, KatolaZ wrote:
> > > Which version of reportbug are you using?
> >
> > The offending version was 6.6.6~bpo8+1, and the upgraded
On Fri, Jul 21, 2017 at 02:01:46PM +0100, KatolaZ wrote:
[cut]
>
> Hi,
>
> You should exercise some patience, please :) The bug reports are
> processed in batches. Your emails arrived on the server aroun 11:40,
> 11:50, 12:30 UTC time, and have been processed. You should have
> received
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
[cut]
>
> That version does show up on my apt-cache policy output, pinned to the
> default 990 from http://auto.mirrors.devuan.org/merged jessie/main.
>
> However, version 6.6.6~bpo8+1 was likewise pinned to the default 990
> from
On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote:
> On 2017-07-21 13:24, KatolaZ wrote:
> > Please check this first, since dozens of people are using reportbug
> > from jessie, and their bugs are correctly reported to bugs.devuan.org.
>
> Enzo, I should add that though I manually
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote:
> Thanks for a quick response.
>
>
> On 2017-07-21 13:24, KatolaZ wrote:
> > Which version of reportbug are you using?
>
> The offending version was 6.6.6~bpo8+1, and the upgraded (current)
> version is 7.1.6+devuan2.1.
So it was not
On 2017-07-21 13:24, KatolaZ wrote:
> Please check this first, since dozens of people are using reportbug
> from jessie, and their bugs are correctly reported to bugs.devuan.org.
Enzo, I should add that though I manually submitted THREE bug reports to
devuan this morning, I have received neither
Thanks for a quick response.
On 2017-07-21 13:24, KatolaZ wrote:
> Which version of reportbug are you using?
The offending version was 6.6.6~bpo8+1, and the upgraded (current)
version is 7.1.6+devuan2.1.
> jessie has 6.6.3+devuan1.3,
That version does show up on my apt-cache policy output,
On Fri, Jul 21, 2017 at 08:15:59AM -0400, Boruch Baum wrote:
>
> Earlier today, I filed a bug report against the devuan testing version
> of 'mutt', but because I was using the stable version of devuan, and the
> stable version of reportbug, the report went to debian.
>
> Now, that was
Earlier today, I filed a bug report against the devuan testing version
of 'mutt', but because I was using the stable version of devuan, and the
stable version of reportbug, the report went to debian.
Now, that was incompetent. Was it incompetent of me or of devuan or
both?
Updating a recipient
20 matches
Mail list logo