Jeff Johnson:
> This simply is not true.
What is not true? Could you please include sentence you are referring to?
> Whatever "rpm format" means, historically RPM itself has always gone to some
> lengths not to expose E: to users to simplify the endless fog of dependency
> hell clutter.
Rpm
Neal Gompa:
> > Regarding these two questions:
> >
> >>> Are there any concerns about such change?
> >>> I believe that >90% users wouldn't notice anything as it's related to the
> >>> history database only.
> >
> >> On Wed, Jul 18, 2018 at 10:01 AM Igor Gnatenko
> >> wrote:
> >> Since we've
Sandro Mani:
>
>
> On 11.05.2017 16:58, Michael Mraka wrote:
> >Sandro Mani:
> >>Hi
> >>
> >>I've tried a couple of times to build mingw-qt5-qtquick1 [1], but
> >>the task consistently fails after the actual build succeded [2],
>
Sandro Mani:
> Hi
>
> I've tried a couple of times to build mingw-qt5-qtquick1 [1], but
> the task consistently fails after the actual build succeded [2],
> seemingly when moving the rpms or tagging the build, with the
> following message:
>
> Traceback (most recent call last):
...
>
Felix Miata:
> [mc-4.8.18 has been broken since release, so I locked 4.8.17]
>
> # grep RETT /etc/os-release
> PRETTY_NAME="Fedora 26 (Twenty Six)"
> # dnf versionlock list
> Last metadata expiration check: 1:33:30 ago on Thu Mar 23 16:44:17 2017 EDT.
> mc-1:4.8.17-2.fc25.*
> # dnf list mc
> Last
Przemek Klosowski:
> Easy access to debug information is very well done in Fedora, and is
> one of its most empowering features. It's very easy to trace
...
> Once the debuginfo is installed, however, we have a little bit of a
> stalemate, because the regular updates do not update the debuginfo
>
DNF 2.0.0 and DNF-PLUGINS-CORE 1.0.0 has been released. [1]
This major version update of DNF brings many user experience
improvements and underlying code changes. This release has been focused
on improving yum compatibility and fixes over 60 bugs. Because this
release is not fully compatible with
Rex Dieter wrote:
% yum includes arch/release subdirs under /var/cache/yum, the important part
% is the "release" part. So, it is theoretically easy to identify which parts
% are worth keeping and which ones are not (ie, does the release/ subdir match
% the current release or not). ie,
% $ ls
Brian C. Lane wrote:
%
% This code was in a top level module and was not marked with _ as is
% the python convention for private methods. Whether or not you document
% the api is immaterial. If you expose a method it is going to eventually
% get used by someone.
What exactly mean "top level
Neal Becker wrote:
% I'm stuck on this (again). According to advice here:
%
% https://lists.fedoraproject.org/pipermail/devel/2015-June/211666.html
%
% I just needed to use
% Requires: /usr/bin/python
%
% But I tried changing
%
% Requires: python
%
% to
%
% Requires: /usr/bin/python
%
%
Hi developers,
I'm trying to finish port of yum-utils scritps to DNF and I came across
couple of scripts I'm not sure whether they are just legacy stuff or
someone still uses them. Do you need them? If so raise your voice and
tell us your use case so we can find the best way to support it.
I'm
The unsigned tag 'perl-Net-IPv4Addr-0.10-19.el7' was created.
Tagger: Michael Mraka michael.mr...@redhat.com
Date: Wed Sep 3 10:38:02 2014 +0200
Perl 5.20 rebuild
Changes since the last tag 'perl-Net-IPv4Addr-0_10-8_fc14':
Dennis Gilmore (6):
- Rebuilt for https://fedoraproject.org
12 matches
Mail list logo
