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
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
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
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
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 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
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 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 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 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 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 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
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.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,
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 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-"
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 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
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
+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
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 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
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
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:
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 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 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 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 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 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 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
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 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 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 08.11.19 um 20:24 schrieb Ankur Sinha:
Sure, but what does one do here? Unset and reset the review flag? Can I
do that given that Petr reviewed and approved it already?
Yes. (both questions)
Felix
___
devel mailing list --
Hi,
(repost as I forgot to cc Eric)
I'm trying to contact Eric Smith (FAS: brohaha).
I have started the nonresponsive maintainer process because I'm trying to
update the WeasyPrint package which requires updating/fixing a few other
packages maintained by Eric.
This is mostly about:
-
Hey,
thunderbird-enigmail was retired in rawhide after being orphaned for more than
6 weeks. However F30+F31 still have the RPM but it does not work at all due to
Thunderbird changes.
I'm not interested in taking over the master branch but I'd like to ensure
that F31 ships working software.
Am 07.11.19 um 13:31 schrieb Miro Hrončok:
> "[2 months for RCs instead of 1] allows for synchronizing the schedule of
> Python release management with Fedora. They've been historically very helpful
> in early finding regressions not only in core Python but also in third-party
> libraries,
Am 07.11.19 um 14:47 schrieb Miro Hrončok:
> On 07. 11. 19 14:41, Felix Schwarz wrote:
>> However the wiki page says:
>> "All packages depending on any python2 package will be removed."
>
> All "binary" packages.
(...)
>> So maybe I just misundersto
Am 07.11.19 um 14:57 schrieb Felix Schwarz:
> Is there some automation to remove "python2-" subpackages or do you plan some
> "single hero"-style changes? If neither what is the plan for maintainers who
> just don't do anything?
I should do more reading before r
Hi Miro,
Am 07.11.19 um 14:34 schrieb Miro Hrončok:
> We actually are wiping out the entire Python 2 ecosystem here, that is the
> point.
Ok, maybe I misunderstood the change.
Just to be clear: I'm fine with the Python 2 package removal (though I expect
I'll continue to develop Python 2 code
Am 07.11.19 um 13:01 schrieb Petr Viktorin:
> If this took you by surprise, don't panic. It's possible to change the
> default. Let us know and we'll work things out.
Somehow I feel like I don't understand the report – or we are approaching an
(almost) unmitigated disaster here: There are so
Am 13.11.19 um 00:52 schrieb Kevin Kofler:
> Felix Schwarz wrote:
>> Currently I have these lines in thunderbird-enigmail's .spec file:
>> ,-
>> BuildArch: noarch
>> # Thunderbird is not available on all supported platfo
Hi Fabio,
Am 12.11.19 um 13:37 schrieb Fabio Valentini:
> There's a specific section about this issue in the Packaging Guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unported_dependencies
>
> So, in your case, I think you'd have to use something like this:
Hi,
recently I took thunderbird-enigmail to fix some CVEs + unbreak the package.
With the help of two Fedora users I updated the package + improved the spec
file (I hope :-).
Now I wanted to push out an update but taskotron complains:
> dist.rpmdeplint FAILED for
Am 12.11.19 um 14:49 schrieb Fabio Valentini:
On Tue, Nov 12, 2019 at 1:44 PM Felix Schwarz wrote:
Am 12.11.19 um 13:37 schrieb Fabio Valentini:
There's a specific section about this issue in the Packaging Guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines
Hi,
I noticed that the latest update for scribus-generator (pushed to stable F30)
now provides + obsoletes python2-tkinter. This removes python2-tkinter (from
Fedora's "python2" package) and will install scribus+dependencies instead.
I don't understand why this change was done so asking here.
Am 05.11.19 um 10:05 schrieb Zbigniew Jędrzejewski-Szmek:
That seems to be a bug.
Ok, I filed https://bugzilla.redhat.com/show_bug.cgi?id=1768831
(Hopefully we can get this fixed asap because we won't be able to fix this
automatically once python2-tkinter was removed in existing installs.)
Hi,
I'm trying to contact Eric Smith (FAS: brohaha).
I have started the nonresponsive maintainer process because I'm trying to
update the WeasyPrint package which requires updating/fixing a few other
packages maintained by Eric.
This is mostly about:
- python-cairocffi
- python-pyphen
Eric: I suspect you are still interested in participating in Fedora and I
appreciate that. May I suggest that you give full "admin" co-maintainership
much faster. That would enable me an others to resolve many of the bugs. :-)
Felix
___
devel mailing
Am 04.12.19 um 16:46 schrieb Fabio Valentini:
The process for joining the group of package maintainers in the first
place is outlined on this aptly named wiki page:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
It should pretty much cover everything you need to know.
Am 06.12.19 um 23:45 schrieb Charalampos Stratakis:
I get there might be some quirks here and there, but having that done on a
stable fedora due to eclipse moving into a module so late in the release cycle
is just unacceptable. I don't know what a good solution would be here, maybe
have
Am 13.12.19 um 07:29 schrieb Frank R Dana Jr.:
> As a follow-up to RHBZ 1779063 and in accordance with the non-responsive
> maintainer policy[1],
You should also cc Chris - maybe he is no longer actively following
fedora-devel.
Felix
___
devel
Hi,
following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact moezroy (Moez Roy).
Moez, if you're still interested in maintaining your packages, please respond.
There several open bugs without response [1], including bug 1762083 [2] where
a
Am 07.12.19 um 12:17 schrieb Miro Hrončok:
And disallow all the current default modular streams. Ship defaults as
traditional RPMs. Keep modularity for alternate versions.
+1
With the current tooling modularity must be optional as it requires manual
steps to fix packaging problems. With
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 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 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
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 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
I recently became co-maintainer for python-pyphen and noticed that the package
had an incomplete license tag.
python-pyphen.spec
-License:LGPLv2+
+License:GPLv2+ or LGPLv2+ or MPLv1.1
Felix
___
devel mailing list --
Hi,
following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact jhogarth (James Hogarth).
James, if you're still interested in maintaining your packages, please respond.
python-pyrfc3339 did not get an update to 1.1. Release monitoring filed
Am 30.11.19 um 07:27 schrieb Chris Adams:
> I think the problem is that unmaintained packages are still
> unmaintained; drive-by changes by provenpackagers are not actual
> maintenance, because that's not a scalable organization (expecting
> provenpackagers to do all maintenance on random
PS: forgot to add the link to my bug report as required by the policy:
https://bugzilla.redhat.com/show_bug.cgi?id=1774667
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Am 30.11.19 um 01:42 schrieb Kevin Kofler:
> Fabio Valentini wrote:
>> I'm not really sure what you want to say here. There's a pretty strict
>> policy about what changes provenpackagers are "allowed" to make to
>> "foreign" packages, and it doesn't include pushing minor improvements.
>
> Well,
Hi Artur,
Am 29.11.19 um 12:35 schrieb Artur Iwicki:
> Some time ago I adopted blueman, as it has been orphaned and I, being a user,
> wanted to keep it around.
>
> Unfortunately I know very little Python (which blueman is written in) and
> even less about the Bluetooth stack on Linux, and as
Am 29.11.19 um 11:18 schrieb Miro Hrončok:
> My effort is to raise the awareness about he failure. Despite my large effort,
> I cannot possibly fix all the build failures in Fedora.
I just wanted to mention that I appreciate your efforts.
I think the "fallout" from retired packages may be a
Am 14.11.19 um 10:43 schrieb Josef Ridky:
> I am hitting issue with my GIMP module in F30+. Most of users reporting the
> issue with missing module(platform:{30,31}) during update to newer Fedora
> /removing of some packages.
> And honestly, I don't know, how is possible, that F30 user is able
Am 22.12.19 um 02:49 schrieb John M. Harris Jr:
> Unfortunately, this package will eventually be hurt by this new FESCo policy
> to remove Python2. It is unfortunate, but cannot really be avoided. If it
> doesn't get a FESCo exception (and FESCo has denied several exceptions,
> regardless of
I recently became co-maintainer for davfs2 and noticed that the package
featured an outdated license tag (davfs2 switched to the GPLv3 10 years ago)
-License:GPLv2+
+License:GPLv3+
Felix
___
devel mailing list --
Am 23.12.19 um 01:23 schrieb John M. Harris Jr:
> So long as Python2 remains installable, I don't see why you feel the need to
> rip it out of the distro.
Also imho I expect that Fedora packages will receive security fixes and
serious bugs will be fixed (of course still considering that Fedora
Hi Erich,
Am 02.03.20 um 21:24 schrieb Erich Eickmeyer:
> As these attempts were over a week ago, I guess my next step is to submit a
> FESCo issue with the bug links. However, since this is my first post
> specifically looking for bsjones unlike my previous post, perhaps I should
> give it
Am 02.03.20 um 04:43 schrieb J. Scheurich:
> What is wrong ?
Bugzilla + the build system are not magically linked. You need to close the
bug manually after building the package in rawhide and F32.
Just from a quick glance I think your rebuilds were successful so you can
close the bug report.
Am 26.01.20 um 01:10 schrieb Bill Chatfield via devel:
> That's a very sad story. I had no idea. So it sounds like you mainly need
> maintainers for Java packages. I have worked on building RPMs but I have
> never been a package maintainer. However I have 20 years of experience as a
> Java
Hi Bill,
Am 30.01.20 um 07:25 schrieb Bill Chatfield via devel:
> According the procedure for retired packages, I'm announcing my intention to
> take ownership of checkstyle, checkstyle-maven-plugin, and
> google-http-java-client. They are all retired as far as I can tell.
Welcome to Fedora -
Am 31.01.20 um 03:01 schrieb Kevin Fenzi:
> I am with you on open source, but I don't understand the 'self-hosted'
> requirement. I guess I agree that self hosting should be possible, in
> case someone wants to fork our distro and use our tools, but if we can
> convince a open source project to
Am 31.01.20 um 15:06 schrieb Julen Landa Alustiza:
> We don't have any problem to retire open source packages that works because
> they don't move to python 3 for example, but at the same time we hold dead old
> libraries due to proprietary software.
>
> It looks unfair at least
The main
Am 31.01.20 um 15:22 schrieb Felix Schwarz:
> (Also you should not presume that shipping gstreamer 0.10 in Fedora is a
> given, see Dominik's answer and Miro's attempt to clarify the security
> policy.)
^^^ Michael's answer of cour
Am 05.02.20 um 09:55 schrieb Code Zombie:
> What do you mean? The source code built successfully on my Fedora 31 system
> with JDK 11 (using ant).
I don't know the Netbeans code but in Fedora we need to build each package
from source (no precompiled jars). That means we also need to ship *all*
Am 15.01.20 um 23:11 schrieb Victor Stinner:
> This solution is well supported by unmodified Python: it's part of the
> default sys.path search path:
>
> $ python3
> Python 3.7.6 (default, Dec 19 2019, 22:52:49)
import sys; sys.path
> ['', '/usr/lib64/python37.zip', ...]
>
> It's the
Am 16.01.20 um 13:37 schrieb Nicolas Mailhot via devel:
> If we start messing with the Python tree it would be nice to put each shared
> python component in a separate zip/xz/whatever, and allow versioning those
> archives
>
> (ie use the highest semver zip present unless the code explicitely
Am 13.01.20 um 14:05 schrieb Vít Ondruch:
> While I like the annotated tag proposal, I would really appreciate if
> the first step was replacing the:
(..:)
> %changelog
>
> %include changelog
>
> ~~~
>
> where the `changelog` file would be either available with the original
> changelog content
Am 22.01.20 um 11:00 schrieb Neal Gompa:
> Yes, but neither of those communities actually have terribly special
> requirements. In fact, those communities either had *nothing* in terms
> of infrastructure (FreeDesktop/Xorg) or were willing to throw
> everything away for GitLab (GNOME). We would
Am 16.01.20 um 21:15 schrieb Zbigniew Jędrzejewski-Szmek:
>> Accommodating component versioning would mean deploying
>>
>> /usr/lib/pythonxx/site-packages/something-semver.zip
>
> This path includes xx, which contains the major and minor numbers. So
> adding "semver" would only allow
Am 21.01.20 um 22:31 schrieb Michael Catanzaro:
> Well since we have a request for requirements: I propose requirements #1 and
> #2 are to be self-hosted and open source.
+1
Felix
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
Am 21.01.20 um 21:48 schrieb Guido Aulisi:
> I totally agree with Fabio, I can’t think of a single reason we should dismiss
> pagure.
Gitlab is used by many free software communities like Freedesktop, Gnome,
Debian. Using the same tools could help to facilitate
inter-process/inter-distro
Am 06.01.20 um 20:48 schrieb Robbie Harwood:
To actually get removed from your package in Fedora typically takes at
least three months during which you have to be mostly non-responsive. I
only package a few things in Fedora, but it's far more frustrating to me
as a maintainer when a
Hi,
I just tried to push some changes to git but was unable to do.
$ git push
Please visit
Am 16.04.20 um 20:05 schrieb Göran Uddeborg:
> As the suggestion was sent off list, I didn't want to say that.
No reason to keep it secret :-)
Until now I did not realize I sent you a private message (just wondered about
the privat reply ;-)
Felix
___
Am 24.03.20 um 12:04 schrieb Felix Schwarz:
> If I have some spare cycles I'll try to run the upstream test suite with
> msgpack 1.0.
just fyi: borgbackup upstream was not compatible with python-msgpack 1.0 but
upstream was (again) very helpful so the next version of borgbackup will also
s
Hi,
following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact elyscape (Eli Young).
Eli, if you're still interested in maintaining your packages, please respond.
Open bugs:
- python-digitalocean-1.15.0 is available
Am 14.03.20 um 10:35 schrieb Felix Schwarz:
> I just tried to push some changes to git but was unable to do.
...
>
> What I can do to get this fixed?
I tried again and somehow it worked the second time.
Felix
___
devel mailing list
Am 31.03.20 um 12:42 schrieb Kevin Kofler:
> I think that using anything other than Free Software as the hosting platform
> for Fedora should be an absolute no go. In other words, self-hosted GitLab
> CE or Pagure, no other options.
+1 with one minor(?) exception:
I'm ok with using a hosted
1 - 100 of 246 matches
Mail list logo
