On Sat, 2016-11-26 at 06:09 +0100, Ralf Corsepius wrote:
>
> I do not understand. I feel, we still are talking about different subjects.
>
> AFAICT, this did not happen with fc25.
There was a 0-day update push well before F25 was released. Any
remaining upgrade path issues aren't caused by the f
On Sat, 2016-11-26 at 06:26 +0100, Ralf Corsepius wrote:
> I have been trying to push a package chain consisting of 2 new
> packages,
> which are required to update a 3 package, to Fedora:
>
> The first package hit "the freeze". It took ~3 weeks to make it to
> fc25
> stable. The second package
On 11/25/2016 09:44 PM, Adam Williamson wrote:
On Fri, 2016-11-25 at 18:38 +0100, Ralf Corsepius wrote:
On 11/25/2016 05:51 PM, Peter Robinson wrote:
So we already do pretty much what you outline above. I started the
first push to f25-updates on the Friday before the release.
I think, we are
On 11/25/2016 06:55 PM, Peter Robinson wrote:
So we already do pretty much what you outline above. I started the
first push to f25-updates on the Friday before the release.
I think, we are talking past each other.
You seem to be referring to "the freeze" in terms of the final release push,
whi
On Sat, 2016-11-26 at 02:24 +, Sérgio Basto wrote:
> Every release we got always tones of updates in day 0, on upgrades and
> non-live versions everyone will update the computer , if we use
> netinstall iso already include updates, only live versions could have
> breaks , but shouldn't be a bet
On Sex, 2016-11-25 at 17:55 +, Peter Robinson wrote:
> >
> > >
> > > So we already do pretty much what you outline above. I started
> > > the
> > > first push to f25-updates on the Friday before the release.
> > I think, we are talking past each other.
> >
> > You seem to be referring to "th
On Fri, 2016-11-25 at 15:17 -0700, Chris Murphy wrote:
> On Fri, Nov 25, 2016 at 3:12 PM, Adam Williamson
> wrote:
> > On Fri, 2016-11-25 at 15:07 -0700, Chris Murphy wrote:
> > > I know the installation tests are
> > > dual boot, following a restore of macOS.
> >
> > Um. But *you* are the person
On 25 November 2016 at 17:17, Chris Murphy wrote:
> On Fri, Nov 25, 2016 at 3:12 PM, Adam Williamson
> wrote:
>> On Fri, 2016-11-25 at 15:07 -0700, Chris Murphy wrote:
>>> I know the installation tests are
>>> dual boot, following a restore of macOS.
>>
>> Um. But *you* are the person who wrote:
On Fri, Nov 25, 2016 at 3:12 PM, Adam Williamson
wrote:
> On Fri, 2016-11-25 at 15:07 -0700, Chris Murphy wrote:
>> I know the installation tests are
>> dual boot, following a restore of macOS.
>
> Um. But *you* are the person who wrote:
>
> "2. The Fedora QA group has 1 mac mini which is very old
On Fri, 2016-11-25 at 15:07 -0700, Chris Murphy wrote:
> I know the installation tests are
> dual boot, following a restore of macOS.
Um. But *you* are the person who wrote:
"2. The Fedora QA group has 1 mac mini which is very old and is only
used for total install and not dual boot. It would not
On Fri, Nov 25, 2016 at 1:59 PM, Adam Williamson
wrote:
> On Fri, 2016-11-25 at 13:53 -0700, Chris Murphy wrote:
>> On Fri, Nov 25, 2016 at 7:26 AM, Bastien Nocera wrote:
>>
>> >
>> > But if the installer is (completely) broken, it might as well be dropped.
>> > Alas, it's not completely broken.
7;t rely quite as much
> on manual testing, through regression testing on "mock" hardware (a hacked
> up VM with a test disk image), comparing the partition types after
> installation
> against a working setup, comparing the file lists in the boot partition,
> etc.
We do ra
On Fri, 2016-11-25 at 09:26 -0500, Bastien Nocera wrote:
>
> > 2. The Fedora QA group has 1 mac mini which is very old and is only
> > used for total install and not dual boot. It would not have found this
> > issue.
>
> The testing should be switched to be a dual-boot test, as it's what
> Mac us
On Fri, 2016-11-25 at 13:53 -0700, Chris Murphy wrote:
> On Fri, Nov 25, 2016 at 7:26 AM, Bastien Nocera wrote:
>
> >
> > But if the installer is (completely) broken, it might as well be dropped.
> > Alas, it's not completely broken.
>
> Unwieldy, perhaps. It's kinda hard to argue that the inst
On Fri, Nov 25, 2016 at 7:26 AM, Bastien Nocera wrote:
>
> But if the installer is (completely) broken, it might as well be dropped.
> Alas, it's not completely broken.
Unwieldy, perhaps. It's kinda hard to argue that the installer needs
to be this complicated, that Fedora (mainly QA) has to put
On Fri, 2016-11-25 at 21:09 +0100, Kevin Kofler wrote:
>
> If people were ensuring that manual pushes are actually workable again, and
> if we would then start strongly discouraging (or ideally outright banning)
> autokarma, we would NOT have as many broken upgrade paths.
It's worth remembering
On Fri, 2016-11-25 at 18:38 +0100, Ralf Corsepius wrote:
> On 11/25/2016 05:51 PM, Peter Robinson wrote:
>
> > So we already do pretty much what you outline above. I started the
> > first push to f25-updates on the Friday before the release.
>
> I think, we are talking past each other.
>
> You s
James Hogarth wrote:
> This is an unfortunate downside of the present freeze process to an extent
> ...
Another main source of this issue is autokarma. IMHO, autokarma should NEVER
be used (and should be dropped from Bodhi entirely), because it inherently
breaks upgrade paths. (The solution for
Hi Sandro,
I've contacted him via Facebook and told him that you're trying to
contact him. I think he'll response soon.
Greetings,
Christian
On 11/25/2016 01:00 PM, Sandro Mani wrote:
> I've seen that the mails to shogun-ow...@fedoraproject.org aka
> fed...@besser82.io are bouncing back becaus
Il 20/11/2016 21:38, Nico Kadel-Garcia ha scritto:
>> I think it would be nice to make a discussion even for non Python
>> packages, so we can elaborate a sort of vademecum that a packager
>> could show to upstreams when there is a collaboration between them.
>>
>> Have a nice day
> Most upstream d
2016-11-25 17:37 GMT+01:00 Stephen John Smoogen :
> On 25 November 2016 at 09:27, Bastien Nocera wrote:
>>
>>
>> - Original Message -
>>> On 2016-11-17 07:43 AM, Stephen John Smoogen wrote:
>>> > 2. The Fedora QA group has 1 mac mini which is very old and is only
>>> > used for total insta
On Friday, 25 November 2016 at 12:58, Sandro Mani wrote:
>
>
> On 25.11.2016 03:44, Kevin Kofler wrote:
> > Sandro Mani wrote:
> > > AFAICS avogadro can still be built against eigen2, so sure, that would
> > > also be a plan. Not sure if reviving the package is better than bundling
> > > though,
Hello, Fabio.
Welcome to Fedora community!
On Thursday, 24 November 2016 at 22:34, Fabio Valentini wrote:
> Here goes my introduction as a new (or aspiring) package maintainer for
> fedora.
>
> I have been using fedora as my daily driver OS for some years now (I
> think starting with f18 or f19)
>> So we already do pretty much what you outline above. I started the
>> first push to f25-updates on the Friday before the release.
>
> I think, we are talking past each other.
>
> You seem to be referring to "the freeze" in terms of the final release push,
> while I am talking about what you'd pr
On Fri, 25 Nov 2016 03:19:49 +0100
Kevin Kofler wrote:
> Peter Robinson wrote:
> > Well the koji web interface itself doesn't use authentication
> > anymore, from a fedpkg PoV there's a lot of complexity with http(s)
> > because it could be proxied or NATed (worst is CG-NAT) so the same
> > conne
On 11/25/2016 05:51 PM, Peter Robinson wrote:
So we already do pretty much what you outline above. I started the
first push to f25-updates on the Friday before the release.
I think, we are talking past each other.
You seem to be referring to "the freeze" in terms of the final release
push, wh
For the release of F25, has nobody run the upgrade path violations
checker
to warn packagers about any downgrades the dist update would perform?
A missing zero day update [only available in updates-testing] for Claws
Mail has hit users. Not great. And I hear there are
On 25 November 2016 at 09:27, Bastien Nocera wrote:
>
>
> - Original Message -
>> On 2016-11-17 07:43 AM, Stephen John Smoogen wrote:
>> > 2. The Fedora QA group has 1 mac mini which is very old and is only
>> > used for total install and not dual boot. It would not have found this
>> > is
On 11/25/2016 04:36 PM, James Hogarth wrote:
On 25 November 2016 at 14:15, Matthew Miller wrote:
On Fri, Nov 25, 2016 at 12:24:40PM +0100, Michael Schwendt wrote:
For the release of F25, has nobody run the upgrade path violations checker
to warn packagers about any downgrades the dist update w
On Fri, 2016-11-25 at 01:46 +0100, Lars Seipel wrote:
> What does that mean, exactly? Does it pass the downloaded file to
> xdg-open or equivalent?
"or equivalent" -- it uses Gio and not xdg-open
> Just because you clicked on a link on some
> website, no matter the file type and association invo
Missing expected images:
Workstation live i386
Kde live x86_64
Kde raw-xz armhfp
Workstation live x86_64
Kde live i386
Failed openQA tests: 12/79 (x86_64), 3/15 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20161124.n.0):
ID: 49751 Test: x86_64 Everything-boot-iso inst
On 25 November 2016 at 14:15, Matthew Miller wrote:
> On Fri, Nov 25, 2016 at 12:24:40PM +0100, Michael Schwendt wrote:
>> For the release of F25, has nobody run the upgrade path violations checker
>> to warn packagers about any downgrades the dist update would perform?
>>
>> A missing zero day up
On Sex, 2016-11-25 at 14:14 +0100, Igor Gnatenko wrote:
> On Fri, Nov 25, 2016 at 1:17 PM, Michael Schwendt m> wrote:
> >
> > The root.log of F25 build jobs prints this late:
> >
> > DEBUG util.py:421: Running transaction
> > DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 1: udevadm:
> > com
OLD: Fedora-Rawhide-20161124.n.0
NEW: Fedora-Rawhide-20161125.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 1
Dropped packages:0
Upgraded packages: 81
Downgraded packages: 0
Size of added packages: 727.01 KiB
Size of dropped packages
sorry about that.
Could you please report the bug at bugzilla.gnome.org/
Thanks.
On Fri, Nov 25, 2016 at 1:53 PM, Michael Schwendt wrote:
> WTF?
>
> Noticed one notification about "File operations" in GNOME Shell, clicked
> on it, and the entire machine was frozen for maybe ten seconds. Mouse
>
- Original Message -
> For that sort of comparison then comparing Macs to any other consumer
> desktop is not possible and is its own category of hardware. I can buy
> 2-3 equivalent memory/cpu/video ASUS systems for a Macbook.
Coo, we might need new computers for the GNOME events box.
- Original Message -
> The reality is that QA is thinly spread in general. Making this
> blocker "about Macs" is a misleading conclusion, there's a grain of
> truth in it, but it's mistaking the forest for the trees. Next time
> there's a release blocking bug, it'll just be something els
- Original Message -
> On 17 November 2016 at 10:22, Bastien Nocera wrote:
> >
> >
> > - Original Message -
> >
> >> No I am not asking for continuous testing. I am asking that if people
> >> really care about the hardware support they get in the muck and do
> >> just a little o
- Original Message -
> On 2016-11-17 07:43 AM, Stephen John Smoogen wrote:
> > 2. The Fedora QA group has 1 mac mini which is very old and is only
> > used for total install and not dual boot. It would not have found this
> > issue. The Fedora QA group also has no one using Mac hardware d
On Fri, Nov 25, 2016 at 12:24:40PM +0100, Michael Schwendt wrote:
> For the release of F25, has nobody run the upgrade path violations checker
> to warn packagers about any downgrades the dist update would perform?
>
> A missing zero day update [only available in updates-testing] for Claws
> Mail
On Fri, Nov 25, 2016 at 1:17 PM, Michael Schwendt wrote:
> The root.log of F25 build jobs prints this late:
>
> DEBUG util.py:421: Running transaction
> DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 1: udevadm: command not
> found
> DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 2: udevad
On 11/25/2016 01:17 PM, Michael Schwendt wrote:
The root.log of F25 build jobs prints this late:
DEBUG util.py:421: Running transaction
DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 1: udevadm: command not found
DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 2: udevadm: command not found
WTF?
Noticed one notification about "File operations" in GNOME Shell, clicked
on it, and the entire machine was frozen for maybe ten seconds. Mouse
pointer couldn't be moved, keyboard input didn't work, couldn't switch
to virtual console either.
___
deve
The root.log of F25 build jobs prints this late:
DEBUG util.py:421: Running transaction
DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 1: udevadm: command not found
DEBUG util.py:421: /var/tmp/rpm-tmp.W2zvnF: line 2: udevadm: command not found
DEBUG util.py:421: Running in chroot, ignoring r
I've seen that the mails to shogun-ow...@fedoraproject.org aka
fed...@besser82.io are bouncing back because the besser82.io domain
isn't valid anymore. Does anyone know another way to contact him?
___
devel mailing list -- devel@lists.fedoraproject.org
On 25.11.2016 03:44, Kevin Kofler wrote:
Sandro Mani wrote:
AFAICS avogadro can still be built against eigen2, so sure, that would
also be a plan. Not sure if reviving the package is better than bundling
though, since eigen2 is completely unsupported upstream and its use not
recommended [1]. I
For the release of F25, has nobody run the upgrade path violations checker
to warn packagers about any downgrades the dist update would perform?
A missing zero day update [only available in updates-testing] for Claws
Mail has hit users. Not great. And I hear there are other packages that
get downg
> On Thu, Nov 24, 2016 at 11:02:19AM -, Carlos Garnacho wrote:
>
> It doesn't seem to be -- I see Screen Lock, Location Services, Usage &
> History, Purge Trash, and Problem Reporting. I have to to install
> tracker-preferences to get a GUI for these settings, as far as I can
> see.
Oh, I sai
48 matches
Mail list logo
