Am 26.10.19 um 15:47 schrieb Fabio Valentini:
You should always be able to create the update "manually" by not using the
search entry, but pasting the build NVR (and bugs, if you have any) manually.
Thanks - I was able to create the update by doing that.
Felix
Hi,
somehow I'm unable to create a new update for my new package
"python-cssselect2" (F31) and I'd like to know why.
When I go to https://bodhi.fedoraproject.org/updates/new and I enter
"python-cssselect2" in the "packages" field, bodhi says "unable to find any
package…".
Bodhi only shows
Am 20.10.19 um 13:30 schrieb Felix Schwarz:
Am 19.10.19 um 19:38 schrieb Jamie Nguyen:
jasmine: 1
I can take jasmine. FAS user "fschwarz".
Felix
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
Am 20.10.19 um 14:21 schrieb J. Scheurich:
$ fedpkg request-repo vcglib 1677989
Could not execute request_repo: The Bugzilla bug's review was approved
over 60 days ago
What to do ?
A need a "new" review. This can be pretty simple if the original reviewer just
resets the "fedora-review" flag
Am 19.10.19 um 19:38 schrieb Jamie Nguyen:
jasmine: 1
I'll check if I can take jasmine (this is quite a bit behind so I want to know
if the latest version needs new dependencies or so).
Felix
___
devel mailing list --
Am 01.10.19 um 16:55 schrieb Stephen John Smoogen:
Then there are problems with budgets and figuring out what exactly it
would cost. We fall outside of many of the 'caveats' that would allow
us to get free.
IIRC at the time when Fedora evaluated its options the open source version of
Gitlab
Am 23.09.19 um 19:06 schrieb Kevin Fenzi:
Well, except that someone needs to rebuild borgbackup?
Thank you for the reminder. I meant to do this but somehow I forgot to
actually trigger a new build. New rawhide build in progress...
Felix
___
devel
Am 19.09.19 um 19:59 schrieb Antonio Trande:
libb2-0.98.1 built
Thanks - test suite for borgbackup still passes so I think we're fine :-)
Felix
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Am 09.09.19 um 18:39 schrieb Antonio Trande:
> New `libb2-0.98.1` will be released by 10 days on Rawhide.
> Packages currently involved:
>
> $ repoquery --release rawhide --disablerepo=* --enablerepo=fedora-source
> --enablerepo=updates-source --whatrequires libb2-devel
>
> Last metadata
Am 05.09.19 um 22:43 schrieb Richard Shaw:
> From a quick look (F30) there are not many dependent packages in F30:
> - yubikey-piv-manage
> dead upstream, no longer being maintained
> maintainer: orion
>
> I can take a stab at it but if it needs significant porting it may be
Am 05.09.19 um 14:57 schrieb Richard Shaw:
> [python-pyside/shiboken]
> - AFAICT these were only designed to work with Python 2, Pyside2 brought
> compatibility with Python 3.
> - My opinion: All consumers of Pyside need to attempt to move over to Pyside2
> then Pyside/Shiboken can be retired.
+1
Am 26.08.19 um 10:20 schrieb Miro Hrončok:
> python-cairosvg orphan, ralph 3 weeks ago
I can take python-cairosvg as I need it for weasyprint (which I hope to update
in the next weeks).
releng ticket: https://pagure.io/releng/issue/8716
Felix
Am 22.07.19 um 21:52 schrieb David Airlie:
>> On Mon, Jul 22, 2019 at 02:51:27PM -0400, Ben Cotton wrote:
>>> After preliminary discussions with CPU vendors, we propose AVX2 as the
>>> new baseline. AVX2 support was introduced into CPUs from 2013 to
>>> 2015. See
>>>
Am 19.07.19 um 19:17 schrieb Miro Hrončok:
> space...@gmail.com brouhaha
> https://bugzilla.redhat.com/show_bug.cgi?id=1731545
> https://bugzilla.redhat.com/show_bug.cgi?id=1706066
>
> Anyone knows how to contact the maintainers? ;)
cc Eric Smith (brouhaha)
I did exchange some mails with him a
+1 to prevent broken dependencies to be pushed into stable. If Fedora aims to
be a "polished"/"user friendly" distro users should never have to deal with
broken dependencies.
Also packages with broken dependencies should not be part of a release (maybe
not auto-retired if they are still ok for
A few weeks ago I noticed that borgbackup bundles some libraries and copied
some external code effectively changing the license of the final executable
code.
This change was not announced upstream so it went unnoticed when updated
versions of borgbackup were pushed to Fedora's git.
I just
Am 03.06.19 um 22:33 schrieb Richard Shaw:
> I did some cursory searching with dnf repoquery and I can't find any consumers
> of the python2 side of pyside and shiboken in Rawhide. I recently moved over
> the largest consumer (FreeCAD) to the python3 pyside bindings.
+1
thanks for taking care
Am 19.05.19 um 17:23 schrieb Yaakov Selkowitz:
> Based on your example, yes:
>
> https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/
>
> "The License: field refers to the licenses of the contents of the
> *binary* rpm."
Thank you - somehow I missed that part.
Felix
I have a question regarding license tags in spec files for software under
multiple licenses (bundled libraries):
- The main software is licensed under a 3-clause BSD.
- The software bundles a library under ASL 2 in subfolder /foo
As far as I know the correct license tag for the Fedora package is
Am 19.05.19 um 10:26 schrieb Miro Hrončok:
>> I have a question about declaring bundled libraries in spec files:
>>
>> I think I need to add a "Provides: bundled(...)" tag in my spec file even for
>> libraries which are not part of Fedora. Is that corrent?
>
> Yes, it's correct.
Thanks for the
Hi,
I have a question about declaring bundled libraries in spec files:
I think I need to add a "Provides: bundled(...)" tag in my spec file even for
libraries which are not part of Fedora. Is that corrent?
This interpretation was derived from:
Am 12.05.19 um 00:25 schrieb Jerry James:
> Execution is getting stuck in this test:
>
> build/lib.linux-s390x-3.7/borg/testsuite/archiver.py::RemoteArchiverTestCase::test_extract_hardlinks
>
> The outer while loop in call_many(), src/borg/remote.py, lines 769
> through 894, never exits. On
Am 11.05.19 um 10:56 schrieb Dan Horák:
> looks like a bug (data endianness?) in borgbackup or its test-suite. I can
> look more or give you access to a s390x machine for debugging after the
> weekend.
That would be great - I don't have any experience with s390x so I'm glad for
any help.
Just
Hi,
I'm trying to create a new build borgbackup for rawhide/F30 (borgbackup is
currently broken on F30).
However it seems like the s390x build just hangs:
https://koji.fedoraproject.org/koji/taskinfo?taskID=34771060
The problem seems to be reproducible as a previous Koji scratch build for F30
Am 14.03.19 um 13:08 schrieb Fabio Valentini:
> I think there is (or at least, there used to be) a section in the packaging
> guidelines which explicitly mentions that including both .c and .h files in
> non-devel packages is fine (and indeed, expected) for compilers and build
> tools which need
Am 07.03.19 um 19:49 schrieb Michael Zhang:
> So after tinkering around, I can incorporate the building of the
> openliberty.zip into the Travis CI build but I cannot directly add it into the
> %install phase of the rpm spec file. Would that be fine?
To the best of my knowledge all building from
Hi,
I am wondering about the state of the "fedora-review" package. It seems to be
a pretty important package to ensure new stuff adhers to the latest Fedora
packaging policy.
When I ran "fedora-review" I noticed that it was clearly not updated for some
time: There where outdated points about
Am 14.02.19 um 23:15 schrieb Ken Dreyer:
> In that case, we can retire python3-cherrypy and move all development
> to python-cherrypy, right?
We could, sure. But why bother?
I don't have strong feelings about either solution but I don't really see the
point. (We will have more and more "python3-"
Hi,
Am 12.02.19 um 18:35 schrieb Ken Dreyer:
> Could someone please help me understand why we have python-cherrypy
> and python3-cherrypy as two separate Fedora packages?
That reason is recorded in the review request for python3-cherrypy:
"Upstream are releasing separate tarballs for Python 2
Am 12.02.19 um 02:35 schrieb Richard Shaw:
> Currently apiextractor is FTBFS[1] because all the test fail.
>
> It looking to see if there is a newer version that better supports gcc 9.0.x I
> found this[2] which states that apiextrator was merged into shiboken.
>
> So can someone with more
Am 21.01.19 um 09:11 schrieb Ian Kent:
> As much as I would like to help I need to get an additional SSD
> for my NUC8i7HNK (Radeon™ RX Vega M GL graphics) for that (I hope
> fairly soon).
>
> And I think the Vega needs a later version of ROCm as well.
Yes, AFAIK Vega M is not (yet?) supported
Am 09.01.19 um 11:50 schrieb Germano Massullo:
> AMD ROCm - Open Source Platform for HPC and Ultrascale GPU Computing[1]
> is packaged by upstream only for RHEL/CentOS and Ubuntu.
> Is anybody working on packaging it for Fedora? If not, is anybody
> interested in setting up a team to work on it?
Am 10.01.19 um 03:28 schrieb Tom Stellard:
> hsakmt and the rocm-runtime are currently packaged in Fedora, but aren't
> up-to-date with upstream. I've wanted to package hip as well, but I've
> been waiting for hip to drop the hcc dependency since it is so hard to
> package.
Do you know when
Am 03.11.2017 um 16:09 schrieb Stephen John Smoogen:
> OK how can we better explain this in the future?
I don't think there is an easy solution with "just another mail to -announce"
or so. Personally I don't find it really practical scanning a mailing list for
relevant packages (and filtering
Am 11.10.2017 um 21:08 schrieb Martin Stransky:
> I believed that the update-testing repository is intended for testing and it's
> used by power users who can handle that, exclude the package from testing if
> needed, downgrade broken package and so on.
>
> I'm surprised that people use
Am 19.02.2016 um 16:53 schrieb Dave Johansen:
> But as was also mentioned, a lot of packages have jumped on the Chrome
> bandwagon with crazy release cycles and maintaining security fixes in those
> cases is basically impossible for a volunteer effort. From my perspective,
> having a policy that
Hey,
Am 25.01.2015 um 21:10 schrieb Till Maas:
Now it seems as if I have to do something to save a part of EPEL5's Python
stack from removal.
You can also just maintain the python packages. AFAIK nobody is really
forcing that python26 is removed from EPEL5, it is just a lack of
interest in
Am 20.01.2015 um 13:16 schrieb drago01:
On Tue, Jan 20, 2015 at 1:07 PM, Felix Schwarz
fschw...@fedoraproject.org wrote:
Is there any plan to force an X-based login session? For example on my old
Intel (gen4) laptop I can not open a wayland session in F21 (I'm taken back
to
the login
Am 20.01.2015 um 12:32 schrieb Jaroslav Reznik:
** Come up with some answer for proprietary Nvidia driver users, since that
stack doesn't yet support Wayland. One idea is to force the login session to
use software-based mesa if the proprietary Nvidia driver is detected.
Is there any plan
Am 20.01.2015 um 13:34 schrieb drago01:
On Tue, Jan 20, 2015 at 1:27 PM, Felix Schwarz
fschw...@fedoraproject.org wrote:
component is currently gnome-shell but it seems to be hardware-dependent as
it works on r600g.
Doesn't look like it ... xwayland crashes but the logs in the bug
Am 14.01.2015 um 19:39 schrieb Chris Adams:
MX-CNAME is against RFCs but in common enough real-world usage that
anything that doesn't handle it is generally considered broken.
Well, one of the biggest German freemailers refused to send emails for
recipient domains using MX is CNAME when using
Am 08.01.2015 um 00:17 schrieb Rahul Sundaram:
That is kind of a basic requirement. We need to do more. We need to inform
people when their release is going EOL and we also need to automatically
prompt users to upgrade whenever there is a new release (ie) some integration
between GNOME
Am 22.12.2014 um 00:34 schrieb Sérgio Basto:
I don't maintain flumotion , I'm Awaiting Review (to have commit
rights), because I'd like update it to flumotion-0.10.1 or git master
version (pre 0.11.0), on rawhide we have flumotion-0.10.0 (released on
2011-10-10 )
The same thing applies for
Am 15.12.2014 um 14:29 schrieb Richard Hughes:
At the moment the PK front-ends only download when on wifi or wired.
Do you have an actual use-case for per-network configuration?
Well I think the whole idea of wifi === unmetered is flawed. For example I
use a UMTS/Wifi router so I can use
Am 29.11.2014 um 19:11 schrieb Matthias Runge:
Interesting, although I believe, we had more than 35 contributors in
September or 39 in October.
For example, I made am listed with 78 commits all time[1]. I believe, based
on badges.fp.o[2], I have more than 400 SCM commits.
One thing to keep
A while ago I noticed that a Debian package has some useful patches for some
package and some of these patches are required to update the Fedora package. I
was wondering if there is a summary about licensing of Debian patches and if
it is acceptable just to copy Debian's patches into Fedora (with
Am 22.11.2014 um 09:24 schrieb P J P:
So far the consensus seem that it is okay to reverse the current default and
set PermitRootLogin=no. I'll talk to the upstream maintainer -
plautrba(https://fedoraproject.org/wiki/User:Plautrba).
Sorry for being late to the party.
I'm ok with no root
Am 18.06.2010 15:08, schrieb Robin 'cheese' Lee:
And I hope for the co-maintainership of following packages, which are
required by Zope2:
(...)
https://admin.fedoraproject.org/pkgdb/acls/name/python-zope-interface
I'm happy to grant you these :-)
fs
--
devel mailing list
Hi,
I'm concerned about bz 579023 [1] which is a Thunderbird crasher bug.
This bug was fixed upstream [2] for about 3-4 weeks. I ran a thunderbird
koji build version [3] with an adapted version of that patch since then
without any problems. Other users confirmed that this patch fixes their
Hi *,
since the last stable kernel update in Fedora 12, a lot of Dell machines
do not boot anymore due to a kernel oops... Of course bugzilla has a
couple of bug reports (e.g. #578217, #579118, #578663, #578590).
There is a known fix/workaround which is already present in CVS
201 - 250 of 250 matches
Mail list logo
