On 20.7.2018 19:56, Kevin Fenzi wrote:
On 07/20/2018 03:55 AM, Michal Novotny wrote:
I actually already filed the respective bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1591225
There is even PR:
https://github.com/rpm-software-management/dnf/pull/1109
that got blocked for an unknown
Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
see anything urgent to discuss, so let's take the time off.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
--
Adam Williamson
Fedo
Package renaming using Obsoletes/Provides will be a problem *ONLY* if
applications confuse the version of the package with the CRDB format version:
these are intrinsically different versions even if there is a single package
renaming event that is coincident with the CRDB format change.
Persona
A mostly "behind the scenes" aspect of the Linux wireless LAN
(IEEE802.11) subsystem has changed upstream with some system-level
effects. Replacing an existing package with a cleaner but functionally
equivalent package is an attractive option, but there are questions
regarding the update path, how
Yes i am already a packager,i can do this then
On Fri, 20 Jul 2018, 21:30 Christian Dersch,
wrote:
> Hi,
>
> are you already a packager? The work is mostly updating packages, besides
> that one important part is the theming of LXQt (usage of Fedora wallpaper
> etc.) and finally maintaining the l
On 07/20/2018 03:55 AM, Michal Novotny wrote:
>
> I actually already filed the respective bugs:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1591225
>
> There is even PR:
>
> https://github.com/rpm-software-management/dnf/pull/1109
>
> that got blocked for an unknown reason and mainly unkn
On 07/19/2018 02:59 AM, Paul Howarth wrote:
> On Wed, 18 Jul 2018 12:41:53 -0700
> Kevin Fenzi wrote:
>
>> Hey all.
>>
>> I have:
>>
>> trac-bazaar-plugin
>> trac-git-plugin
>> trac-iniadmin-plugin
>> trac-mercurial-plugin
>> trac-ticketdelete-plugin
>
> I took a look at trac
I'm going to be retiring StarCluster and its dependency python-iptools
shortly. Upstream is dead and I'm not using it.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...
Hi,
are you already a packager? The work is mostly updating packages,
besides that one important part is the theming of LXQt (usage of Fedora
wallpaper etc.) and finally maintaining the live spin. Packaging is the
most important topic.
Greetings,
Christian
On 07/20/2018 04:44 PM, Manas Mangaonk
I can give this a shot,My name is Manas i am a Computer Engineering
undergrad. I dont know if i have the skills require for this. Can you give
some more information regarding the job.
I started contributing recently to withing the past month or so,as of today
i am the creator and maintainer for int
Use headerFormat() with a configurable format string to extract the package
identifier item in the list that is check summed and have it both ways.
Why anyone wishes to preserve compatibility with yum's bloated history database
in order to flip between two depsolvers is left to RH TAM's to expla
On Fri, Jul 20, 2018, 15:27 Kevin Kofler wrote:
> Igor Gnatenko wrote:
> > No one promised that I'm going to fix 100% of packages, I've fixed around
> > 2k packages. What my regex couldn't catch -- please send me list of
> > packages, I will analyze them and try to fix as much as possible.
>
> IM
On Thu, Jul 19, 2018 at 05:48:24PM +0200, Miro Hrončok wrote:
> >
> > If the FTBFS script has ran too early, all the FTBFS bugs need to be
> > closed and the FTBFS script has to be run again later.
> >
> > If the automatic BuildRequires fixing script missed all these, then
> > I suggest that:
> >
Hi all,
as some of you might have recognized, Fedora's LXQt is quite outdated
(we have 0.11, current one for some weeks now is 0.13) and also needs
some rework with respect to theming and the package set (upstream
restructured packaging a bit with respect to common files). When I
joined the F
A user in darktable mailing list [1] said
"If you are using -specs=/usr/lib/rpm/redhat/redhat-hardened-ld at link
time, you also need to use
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 at compile time, and as
you are compiling and linking at the same time, you need either both, or
drop the -spe
Igor Gnatenko wrote:
> No one promised that I'm going to fix 100% of packages, I've fixed around
> 2k packages. What my regex couldn't catch -- please send me list of
> packages, I will analyze them and try to fix as much as possible.
IMHO, it is unacceptable that you make a change breaking thousa
Miro Hrončok wrote:
> I know it is not comfortable, yet at this point reverting the change and
> doing another mass rebuild is IMHO more work than fixing the packages.
It may be more work for 1 or 2 rel-eng people, but it would save work for
hundreds of affected maintainers and hence result in mu
Germano Massullo wrote:
> If upstream is no longer maintaining it, in my opinion you should
> evaluate to remove it from Fedora repository:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
That will happen automatically if nobody picks it up.
For a library such as audiofile
On Sun, Jul 8, 2018 at 1:46 PM, Igor Gnatenko
wrote:
As per Changes/Remove GCC from BuildRoot, I'm going to automatically
add BuildRequires: gcc and/or BuildRequires: gcc-c++ to packages
which fail to build with common messages (like gcc: command not
found, also autotools/cmake/meson are suppo
On Fri, Jul 20, 2018 at 10:45 AM Kamil Paral wrote:
> On Fri, Jul 20, 2018 at 9:37 AM, Miro Hrončok wrote:
>
>> On 20.7.2018 06:25, Michal Novotny wrote:
>>
>>> Hello,
>>>
>>> I am occasionally experiencing the following error in my day-to-day dnf
>>> use:
>>>
>>> Failed to synchronize cach
On Thu, Jul 19, 2018, 17:48 Rex Dieter wrote:
> Christian Dersch wrote:
>
> > Hi all,
> >
> > please announce your so-name bumps *before* you push them. This time
> > LibRaw bumped its version
>
> I added explicit soname tracking there so hopefully it won't happen again
> (at least not by surpris
Good numbers to provide, thanks. I've one thought for you.
On Wed, Jul 18, 2018 at 2:24 PM, R P Herrold wrote:
> I did not try to structure and run a report to try to
> enumerate and count by dependencies. Looking at the
> problem with such a statistic, as to 'upstream' 'keystone'
> packages wi
On Fri, Jul 20, 2018 at 11:02:19AM +0200, Vít Ondruch wrote:
> Honestly, I think Koschei should be mandatory for every package or at
> least opt-out by default at this point.
+1
That said, we should be working to reduce false positives as much as possible.
Zbyszek
___
On Thu, Jul 19, 2018 at 12:52 PM Manas Mangaonkar
wrote:
> Can you give some more details as those would help Investigate the problem
> better.
>
What additional information would you like to know?
[P.S.: please avoid top-posting.]
--
Rajeesh
___
de
On Thu, Jul 19, 2018 at 12:06 AM, Neal Gompa wrote:
> On Wed, Jul 18, 2018 at 6:02 PM Daniel P. Berrangé
> wrote:
> >
> > On Wed, Jul 18, 2018 at 03:24:54PM +0200, Daniel Mach wrote:
> > > Hi everyone,
> > > The DNF team is currently reviewing DNF compatibility with YUM 3 and
> we'd
> > > like t
On Wed, Jul 18, 2018 at 5:13 PM, Ben Cotton wrote:
> On Wed, Jul 18, 2018 at 11:02 AM Daniel Mach wrote:
>
> > If a user migrates from RHEL 7 to the next version of RHEL (or CentOS),
> > there will be continuity in used algorithm and history db checksums.
> > It's important to some enterprise cu
On Thu, Jul 19, 2018 at 6:40 PM, Justin Forbes wrote:
>
>
> On Wed, Jul 18, 2018 at 4:26 PM, Ben Cotton wrote:
>>
>> == Summary ==
>> A number of devices like Xilinx ZYNQ based devices such as the
>> 96boards Ultra96 and the Intel based UP² have onboard FPGAs. FPGA
>> manager is a vendor-neutral
Honestly, I think Koschei should be mandatory for every package or at
least opt-out by default at this point.
Vít
Dne 20.7.2018 v 03:56 Dan Callaghan napsal(a):
> Excerpts from Miro Hrončok's message of 2018-07-19 17:48 +02:00:
>> I know it is not comfortable, yet at this point reverting the c
On Fri, Jul 20, 2018 at 9:37 AM, Miro Hrončok wrote:
> On 20.7.2018 06:25, Michal Novotny wrote:
>
>> Hello,
>>
>> I am occasionally experiencing the following error in my day-to-day dnf
>> use:
>>
>> Failed to synchronize cache for repo 'fedora'
>>
>> or
>>
>> Failed to synchronize cac
On Fri, Jul 20, 2018 at 6:27 AM Michal Novotny wrote:
>
> Hello,
>
> I am occasionally experiencing the following error in my day-to-day dnf use:
>
> Failed to synchronize cache for repo 'fedora'
>
> or
>
> Failed to synchronize cache for repo 'updates'
>
> I've had that happened even in l
On 20.7.2018 06:25, Michal Novotny wrote:
Hello,
I am occasionally experiencing the following error in my day-to-day dnf use:
Failed to synchronize cache for repo 'fedora'
or
Failed to synchronize cache for repo 'updates'
I've had that happened even in local mock builds.
Do you al
If upstream is no longer maintaining it, in my opinion you should
evaluate to remove it from Fedora repository:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe se
On 7/19/18 10:15 PM, Fabio Valentini wrote:
> I used to get these errors too for some of my packages. It turned out
> that upstream made some mistakes in their CMakeLists.txt files:
> The errors were usually caused by some CMakeLists.txt file overriding
> the system-provided CFLAGS with something e
33 matches
Mail list logo
