Léon Keijser wrote:
> You're probably on a different branch. Do a
>
> $ git branch -a
>
> to see on which branch you're working [1]. Then switch to the f14
> branch if you're not already on it:
It's also worth considering adding the current git branch to your
shell prompt. For bash:
https://fedo
Karel Zak wrote:
> On Tue, Aug 03, 2010 at 12:56:37PM +0530, Rahul Sundaram wrote:
>> On 08/03/2010 12:53 PM, Peter Hutterer wrote:
>>> correct, git will share objects between branches, so by storing in different
>>> directories you'll loose that advantage.
>>>
>>> I've got a shell prompt that sho
Adam Williamson wrote:
>> http://blog.vagmim.com/2009/04/git-branch-on-command-prompt.html
>
> Would it be nice to stick this customization into fedora-packager, or
> would it just confuse/surprise people?
Please no. In addition to being ugly to add directly to anyone's
prompt, the method outline
Roland McGrath wrote:
>> Here is what I'm doing:
>>
>> fedpkg clone kernel
>> fedpkg switch-branch f14
>> git checkout -b pnfs-all-2.6.35-2010-08-05
>
> Make that 'git checkout --track -b pnfs-blah-blah origin/f14/master'.
> Or, equivalently, after the fact, do:
> git config branch.pnfs-blah-
Neal Becker wrote:
> Michael Cronenworth wrote:
>
>> Neal Becker wrote:
>>> No idea what this means.
>>
>> It means it has been 10 commits since you have pushed ("synced")
>> with the git repo living on pkgs.fedoraproject.org. Remember that
>> you have your own unique git repository living on your
Mike McGrath wrote:
> All you can do is trust RH to do the right thing, know we'll make
> mistakes from time to time
And bear in mind how long Red Hat has been doing this and how often
they've chosen to stay on the side of free software versus trying to
close things off for short-term financial ga
Neal Becker wrote:
> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
>
>> fedpkg switch-branch f13
> Branch f13 set up to track remote branch f13/master from origin.
>
>> git merge master
> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
> in m
Kevin Fenzi wrote:
> Would the libgpod update require rebuilding or changing anything
> else? How many other packages depend on that?
The libgpod update should be safe. Though if it was up to me I'd wait
for libgpod to reach 0.8.0. Upstream is treating 0.7.95 like a
release candidate. I don't
Tim Niemueller wrote:
> Recently I wanted to modify a package. Since we now use git for
> packages, the following work flow feels natural:
>
> git clone package-repo
> make changes in package repo
> commit
> push repo somewhere
> send pull request to package maintainer
>
> Is that the anticipated w
yersinia wrote:
> Beware also that git 1.7 by default enforce that it is not possible
> to push to a repository git "not bare", and, from my experience,
> many EPEL users don't haven't read the advice on this of the git
> manual - just an example of another possible "incompatibility"
Yep, but that
Jesse Keating wrote:
> On Oct 7, 2011, at 8:21 AM, Till Maas wrote:
>> On Fri, Oct 07, 2011 at 07:53:25AM -0700, Jesse Keating wrote:
>>
>>> Might have gone quicker if you pull via git:// and then only push
>>> via ssh:// reducing your ssh handshakes by half.
>>
>> How do you ensure the integrity o
Toshio Kuratomi wrote:
> Due to the requirement for contributors to sign the FPCA by Thursday
> of last week, certain package owners who haven't yet signed will be
> removed from the packager group soon. When that happens, the
> packages that they own will be orphaned.
I presume that any packages
Till Maas wrote:
> On Mon, Feb 15, 2010 at 11:38:40AM -0600, Bruno Wolff III wrote:
>
>> I don't control the remote repository. That would be fedorahosted
>> in the case I am asking about.
>
> I am pretty sure that the repositories on fedorahosted are bare so
> that the changes here do not apply or
Matthew Garrett wrote:
> We need to work on making it easier for users to see that there are
> available testing updates and give feedback on them. This is clearly
> going to take a while, and there'd undoubtedly going to be some
> difficulty in getting updates for more niche packages through as a
Bernie Innocenti wrote:
> In Debian & Ubuntu, this can be done by setting XKBOPTIONS=ctrl:nocaps
> in /etc/default/console-setup.
[...]
> So, what's the moral equivalent of this in Fedora?
I have something like this in my puppet configuration:
zcat /lib/kbd/keymaps/i386/qwerty/us.map.gz | \
Jesse Keating wrote:
> At most, we could warn about your status compared to the local
> index, a simple "git status" would show that. We cannot warn about
> your stats compared to upstream without fetching new data.
For folks with recent git (anything in Fedora will do, EPEL, not so
much), there'
Hi,
I've built puppet-2.6.6 for Fedora and EPEL. The 0.25.x branch is not
actively maintained. As mentioned in the subject, the license has
changed from GPLv2+ to GPLv2. The reason for this is that upstream is
considering a move to a different license (an ASL or MIT style license
is what has be
Jonathan MERCIER wrote:
> why default bahrc do not contain all file in /etc/bash_completion.d ?
> me i add in bashrc:
> for file in /etc/bash_completion.d/*; do . $file; done
>
> instead . /etc/bash_compeltion => because do not works file do not
> exist!
This question is probably better suited the
Jonathan Ryshpan wrote:
> On Thu, 2010-07-15 at 21:42 -0400, Todd Zullinger wrote:
>> Jonathan MERCIER wrote:
>>> why default bahrc do not contain all file in /etc/bash_completion.d ?
>>> me i add in bashrc:
>>> for file in /etc/bash_completion.d/*; do
Rahul Sundaram wrote:
> FYI, git-svn is for users who want to continue to use Subversion on
> the server but interact using Git from clients. It is not a tool
> for conversion. It is a common mistake.
Not so much. Many folks use git-svn to convert from svn to git. Once
you have cloned an svn
Josh Boyer wrote:
On Wed, Jun 3, 2015 at 9:19 AM, Petr Stodulka wrote:
On 3.6.2015 13:56, Pierre-Yves Chibon wrote:
[...]
What about adopting something similar to what has been done for
the R package, There is R-core, R-java R-devel and R. If you
yum/dnf install R you get all of them and you
Hi,
Zdenek Dohnal wrote:
> To be honest, I'm sad about the change.
It is just a default though, and I'll certainly change it on
my systems. But like many others, I too can still recall
(decades ago) being dumped into vi and having no clue how to
do anything -- including just exiting.
> I'm not
I wrote:
> Zdenek Dohnal wrote:
>> CCing Git maintainer to see whether it can be implemented or not.
I somehow forgot to say that I'm just one of several
maintainers for the git package. :)
I've Cc'd the git-maintainers alias to include the other
folks.
--
Todd
signature.asc
Description: PGP
Kevin Fenzi wrote:
Please fix any packages you maintain that failed to rebuild.
I orphaned gtkpod. Hopefully chkr can pick that up. He's been
effectively maintaining it for a while now. I don't use an iPod or
Apple stuff anymore, so I have no need for gtkpod and nor time and
ability to te
Adam Williamson wrote:
Hey folks - just in case you haven't all figured this out yet, if
you're using the neat little trick of putting a few lines in your
~/.bashrc so that when you're in a directory containing a git repo,
the prompt will display what branch you're in, it'll stop working
when
I wrote:
This is definitely planned. I mailed Adam (the other Adam) today to
point out that this was broken by the 1.7.12 update. I don't have
time to work on a fix though. But certainly, git-prompt.sh should be
placed in a more permanent location in the next build.
I placed git-prompt.sh
Enrico Scholz wrote:
Todd Zullinger writes:
I placed git-prompt.sh in /etc/profile.d where it should be sourced
for normal login shells.
As I wrote in the update comment, please revert it. It pollutes the
environment of every user with functions which are probably never be
used.
As
Enrico Scholz wrote:
Todd Zullinger writes:
Doing this would break current users that have already configured
their system to use __git_ps1().
What are "current users"? Those who installed your just released rawhide
changes?
No, it breaks anyone that's currently using __gi
Ken Dreyer wrote:
On Fri, Oct 19, 2012 at 5:35 PM, Matthew Miller
wrote:
I'm not opposed to putting puppet 3 in, but it'd really be helpful if it
went in as "puppet3" or something, and left the stable version as is,
happily getting security-only updates.
My biggest concern is that 2.6 will n
I have just orphaned libid3tag. I picked this up a long-time back
because it was needed by gtkpod. I don't maintain gtkpod anymore and
I don't even know if gtkpod requires libid3tag still.
There isn't any upstream that I am aware of for libid3tag.
If anyone wants it, feel free to claim it:
Eugene Pivnev wrote:
11.05.2013 23:22, Adam Williamson:
qgit -> git -> libgnome_keyring
...like this one, for instance. libgnome-keyring's dependencies are
pretty modest:
As I found in git.spec - git's gnome-keyring suff is optional.
Is it possible to move them into separate package (for gnome
Eugene Pivnev wrote:
13.05.2013 02:31, Todd Zullinger:
Eugene Pivnev wrote:
[...]
As I found in git.spec - git's gnome-keyring suff is optional. Is
it possible to move them into separate package (for gnome users)?
This doesn't sound too unreasonable at first (and wasn't
Eugene Pivnev wrote:
libgnome-keyring is minimal problem (ok - is _not_ problem at all;
although I'm surprised that _console_ git depends on DE-specific
library).
I just recently made use of libgnome-keyring via python-keyring for a
console application I wrote. I thought it was quite handy
Hi Petr,
Petr Stodulka wrote:
Hi folks,
I am looking at the #1357438 BZ about broken links to "How to*" doc files and I am thinking,
about the best solution of this. Problem is with using of %doc macro, which moves/copies
doc files to specific directories of each subpackage. However the Make
Hi all,
[I posted this to the packaging list a few days ago, but haven't
gotten any responses, so I want to open this to a wider audience in
the hope of getting some pointers to what I'm missing.]
I'm trying to fix a problem with the git-svn package that causes it to
not pull in the proper p
Jan Kaluža wrote:
On 01/15/2014 01:56 AM, Todd Zullinger wrote:
[root@f20-64 /]# /usr/lib/rpm/find-requires <<<
/builddir/build/BUILD/git-1.8.4.2/git-svn
This fails because find-requires only passes the file to perl.req if
it's either a .pm file or it's in the script lis
Panu Matilainen wrote:
Also FYI, /usr/lib/rpm/find-requires (or -provides) is not what's
used during rpmbuild unless specifically overridden to use that
legacy mechanism.
Thanks Panu. Is there a way to get rpmbuild to be more verbose about
the finding requires stage? I tried using -vv with
Petr Pisar wrote:
Despite there is incompatibility between updated file and rpmbuild,
which could be fixed probably on rpmbuild side to scan modules and scripts
for requires, the basic problem is git.spec uses old, obsoleted,
and broken manual generators:
Thanks Petr. I knew that was the old
Panu Matilainen wrote:
On 01/15/2014 05:31 PM, Todd Zullinger wrote:
Thanks Panu. Is there a way to get rpmbuild to be more verbose about
the finding requires stage? I tried using -vv with rpmbuild and didn't
notice any additional output.
Just added this:
http://rpm.org/wiki/Package
Hi Ivan.
Ivan Chavero wrote:
> Are there any plans to upgrade the spec file of rubygem-asciidoctor for
> Fedora 31 to the 2.0.10 version?
Unfortunately, I don't think it would be an appropriate
update for Fedora 31. And update from 1.5.6 to 2.0.10 would
cause some package builds to break and tha
Hi,
clime wrote:
> Hello,
>
> I very much appreciate the git-core package but there seems to be some
> change under f32 which makes it download many more deps during
> installation.
>
> This is f32:
>
> $ mock -r fedora-32-x86_64 install git-core
> ...
> =
> Package
> ==
I wrote:
> clime wrote:
>> It seems the f32's git-core got many more deps for some reason, even
>> such as dbus-broker or systemd.
[...]
> I'll try to poke a bit in the next few days as I can make
> some time. I had not noticed the inflated depchain. Thank
> you for pointing it out.
I was curiou
Markus Larsson wrote:
> While I'm fine with spending 2500€ of company money on a
> work machine, I'm rather hesitant to spend that kind of
> money on laptops for the kids :)
Isn't that where some good, old-fashioned nepotism comes in?
The kids get a title, a valuable first entry on their CV,
and a
Hi,
E.N. virgo wrote:
>> Why are replying from there instead of using your email client normally?
> I set this list to send digests instead of individual messages;
> so, I was using other means to get to the in-reply-to field.
If you're using the "Plain Text Digests" delivery mode, you
might try
Dridi Boukelmoune wrote:
> On Sat, Nov 2, 2019 at 2:21 AM Orion Poplawski wrote:
>>
>> On 11/1/19 1:47 PM, Daniel Walsh wrote:
>>> Flat pack should be doing a requires(post): selinux-policy-base
>>>
>>> To make sure it is installed before flatpack.
>>
>> Thanks. The proper incantation actually th
Fabio Valentini wrote:
> On Mon, Dec 23, 2019, 17:45 J. Scheurich wrote:
>> $ git commit
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>>
>> Same problem 8-(
>>
> Looks like you have the option to sign your git commits turned on globally,
> probably in ~/.gitconfig
Hi,
Pavel Cahyna wrote:
> On Mon, Jul 29, 2019 at 12:59:22PM +0200, Miro Hrončok wrote:
>> On 29. 07. 19 12:37, Miro Hrončok wrote:
>>> The following packages are orphaned and will be retired when they
>>> are orphaned for six weeks, unless someone adopts them. If you know for sure
>>> that the pa
Miro Hrončok wrote:
> Note that jgit is not (yet) orphaned nor retired, and its dependencies might
> be picked up by somebody. I suggest to remove the dep in rawhide temporarily
> (to make the next weeks reports more readable and shorter to calculate (the
> present one took 2 days)). Once the dust
Hi all,
I'm planning to push asciidoctor-2.0.10 to rawhide in the
next few days. This is a major bump from our current 1.5.8,
but upstream has worked hard to fix regressions found since
the initial 2.0.0 release back in March.
The 2.0.0 release notes can be found at:
https://github.com/asci
Hi Vit,
Vít Ondruch wrote:
> Dne 24. 09. 19 v 17:47 Todd Zullinger napsal(a):
>> These srpm's require asciidoctor or rubygems-asciidoctor:
>>
>> awesome
>> booth
>> hugo
>> ipmctl
>> js8call
>> mod_auth_mell
Hi Miro,
Miro Hrončok wrote:
> On 25. 09. 19 17:10, Todd Zullinger wrote:
>> dnf repoquery -q --qf '%{name}' --archlist=src --releasever=rawhide \
>> --disablerepo='*' --enablerepo=rawhide-source \
>> --whatrequires asciidoctor --whatrequire
Hi Robert-André,
Robert-André Mauchin wrote:
> Using Igor's whatrequires script
> (https://gist.github.com/ignatenkobrain/a2b21a4db497a2a4b441e3957fcc8483), we
> get:
Nice. I didn't know about that one either.
> PACKAGE DEPENDENT
>
Hi Fabio,
Fabio Valentini wrote:
> I'm the maintainer of rubygem-jekyll-asciidoc, and I think there
> shouldn't be issues with it when updating rubygem-asciidoctor.
> The Jekyll AsciiDoc plugin is published by the asciidoctor project
> themselves, so I just hope they know what they're doing :)
He
Hi,
I wrote:
> I'm planning to push asciidoctor-2.0.10 to rawhide in the
> next few days.
This has now been built and should show up in the next
rawhide compose.
> This is a major bump from our current 1.5.8, but upstream
> has worked hard to fix regressions found since the initial
> 2.0.0 relea
Jakub Jelinek wrote:
> On Sat, Mar 14, 2020 at 11:54:54PM +0100, Dominik 'Rathann' Mierzejewski
> wrote:
>>> Known issue?
>>
>> The above was with gcc-10.0.1-0.9.fc32 and annobin-9.06-1.fc32.
>>
>> Looks like it was fixed in the meantime as another build gets
>> gcc-10.0.1-0.8.fc32 and the same
Stephen Gallagher wrote:
> On Fri, Jan 18, 2019 at 11:18 AM John Harris wrote:
>>
>> On Friday, January 18, 2019 8:14:32 AM EST Stephen Gallagher wrote:
>>> Note: Adding the Signed-off-by: line to a patch should be a conscious
>>> act and means that you certify you have the rights to submit this w
Hi,
Richard Shaw wrote:
> Out of curiosity I took a look at abipkgdiff that's provided by the
> libabigail package and it's a python wrapper around abipkgdiff. I'm a
> little rusty on Python but I could probably use that as a very nice
> starting point...
>
> The next question is what package wou
Hi,
Mohan Boddu wrote:
> Fedora 30 has now been branched,
Thanks, to you and the releng team. :)
> please be sure to do a git pull --rebase to pick up the
> new branch
A simple 'git fetch' should suffice to pick up the f30
branch. Depending on the state of one's repository, the
'git pull --reb
Orion Poplawski wrote:
> With current koji buildroot I end up with:
>
> + ls -l /usr/bin/ld /usr/bin/ld.bfd /usr/bin/ld.gold /usr/bin/ldd
> --w---. 1 root root 3814880 Feb 27 04:00 /usr/bin/ld
> -rwxr-xr-x. 1 root root 1841608 Feb 26 15:02 /usr/bin/ld.bfd
> -rwxr-xr-x. 1 root root 3814880 Feb
Hi,
[BTW, something is wrong with your mail client's quoting.
It is very hard to read your replies when your reply and the
text to which you are replying to are at the same quote
level.]
Globe Trotter wrote:
> Thanks! I see. Actually, I am not that keen on packaging
> fetchmailconf. I think that
Hi,
Globe Trotter wrote:
> Here is my fetchmail.spec:
[...]
> %build
> autoreconf -if
> %configure PYTHON-: --enable-POP3 --enable-IMAP
[...]
You want "PYTHON=:", not "PYTHON-:". The goal is to set the
PYTHON variable. I tend to put such definitions before the
configure call, e.g.:
%build
Hi,
Globe Trotter wrote:
> Thanks, and that takes care of it.
Glad that helped.
> Thanks also for letting me know of preferred options. I am
> quite new to this and so any advice is always helpful.
>
> I will see if the copr maintainer wants to host my build.
> fetchmail 7.0.0 alpha has suppo
Richard W.M. Jones wrote:
> On Tue, Mar 12, 2019 at 11:38:47AM +0100, Miro Hrončok wrote:
>> rjones: apache-ivy, maven-jar-plugin, maven-javadoc-plugin, gradle,
>> xmvn, plexus-utils
>
> I'm unclear what if anything I could do (apart from maintaining loads
> of Java packages which isn't going to h
Antonio Trande wrote:
> On 09/04/19 22:29, Kevin Fenzi wrote:
>> Can any of you folks seeing this:
>>
>> Run this script:
>> https://paste.fedoraproject.org/paste/tWt5LBT13-~d22wBpo38uQ/raw
>>
>> and send me the output?
>
> Sorry,
>
> how this script works?
You can download the script (using P
Neal Gompa wrote:
> If devtoolset is available for EPEL6 (which I think it is?)
I don't believe devtoolset was enabled for el6 in koji.
When it was added to the mock configs for el6/el7, the
consensus on the epel list was that it would be added to el6
if there was sufficient demand. I've only see
Daniel P. Berrangé wrote:
> On Fri, Aug 10, 2018 at 11:27:43AM +0200, Pierre-Yves Chibon wrote:
>> On Fri, Aug 10, 2018 at 10:16:13AM +0100, Daniel P. Berrangé wrote:
>>> ability to write to git, but there are a variety of ways to deal with that.
>>
>> I'm pretty sure we used to do this at one poi
Chris Murphy wrote:
> Semi-related to the "Attention Gmail users, please turn off HTML"
> thread; anyone *not* using gmail (e.g. all Yahoo email users) are
> having their emails put into spam by google mail.
>
>
>>This message has a from address in yahoo.co.uk but has failed yahoo.co.uk's
>>requ
Hi,
Florian Weimer wrote:
> * Todd Zullinger:
>
>> On the users list we enabled Mailman's DMARC mitigations
>> several months ago. That has allowed posts from users
>> @yahoo and other domains with strict DMARC settings to reach
>> list subscribers @gmail
Brian (bex) Exelbierd wrote:
> On Mon, Oct 1, 2018 at 11:03 PM Björn Persson wrote:
>
>> Jason L Tibbitts III wrote:
>>> Indeed, asciidoctor works a bit better than asciidoc does but still
>>> converts quickly. It's actually in the "rubygem-asciidoctor" package.
>>
>> Maybe I'll try that next t
Máirín Duffy wrote:
> So our Hyperkitty version is old here. I can't reporduce the issue on
> mailman3.org's HK, which is newer. I suspect this is a bug that's been fixed.
Indeed it was. An infrastructure ticket was filed ~7 months
back¹ and the issue was addressed upstream in 7558682 ("Fix
quot
Jonathan Dieter wrote:
> On Fri, 2018-10-19 at 21:37 -0700, Josh Stone wrote:
>> On 10/19/18 6:19 PM, Robert-André Mauchin wrote:
>>> On samedi 20 octobre 2018 00:31:50 CEST Jonathan Dieter wrote:
I'm trying to build duperemove[1] for epel7[2], and it's building on
all the arches except a
Sérgio Basto wrote:
> I had checked mock-core-config [1] , which are in use in copr (I guess)
> and can't enable developer tools .
> But on koji runs well , can you review this ? please .
>
> I could build azureus [4] on koji [2] which need eclipse-swt , but not
> on copr `Error: No Package found
Hi Zbigniew,
Zbigniew Jędrzejewski-Szmek wrote:
> I'll do a mass update to use C.UTF-8 for the packages in the list that
> follows, next week. I'll do test builds locally, and I'll only push to
> dist-git if the local builds succeed. Let me know if you want your
> package to be excluded.
> git
Florian Festi wrote:
> On 3/29/23 10:31, Michael J Gruber wrote:
>> Has `%patchN` been deprecated in favour of `%patch N`?
>
> Yes, see %patch section on
> https://rpm-software-management.github.io/rpm/manual/spec.html
Quoting that:
%patch is used to apply patches on top of the just unpacked
Chris Murphy wrote:
> I've implemented the suggested two line change to
> .bash_profile:
>
> # User specific environment and startup programs
> shopt -s histappend
> PROMPT_COMMAND="history -a;$PROMPT_COMMAND"
>
[...]
> Any thoughts?
As others have said, enabling this by default has
consequences
Chris Adams wrote:
> Once upon a time, Michael Catanzaro said:
>> On Tue, Apr 11 2023 at 12:18:58 PM -0500, Chris Adams
>> wrote:
>>>I wouldn't do that part; that's additional disk I/O for every prompt.
>>>Especially when the system might be having issues, users (especially
>>>root) don't need so
TLDR; I'm in the "please, not a web forum" camp, but I also
feel like this is effectively a foregone conclusion,
unfortunately.
As a maintainer of a small number of packages, I follow
devel to keep up with changes affecting the distribution and
occasionally chime in or find areas where I can help
Chris Adams wrote:
> Kind of a random thing, but... I would like to write up how to use GRUB2
> to do BIOS-PXE+UEFI-PXE+UEFI-HTTP boot. I asked for the Fedora packages
> to include the needed PXE bit, and it does now (thanks!), so I feel I
> owe a good explanation on how to use it. :)
>
> I don't
Hi,
Michal Domonkos wrote:
> We're currently preparing an update to RPM 4.19 ALPHA for Rawhide in a
> side-tag. The new version features a soname bump:
Is there a porting guide for rpm python users? The rpmlint
package has a number of test failures and quite likely other
breakages which may not
I wrote:
> I may attempt to resolve some of the issues, but if there's
> some documentation on the changes it would make it a lot
> easier. :)
I filed an upstream PR with a couple of commits:
https://github.com/rpm-software-management/rpmlint/pull/1066
This fixes the test suite and works in
Stephen Gallagher wrote:
> On Fri, Jun 16, 2023 at 11:53 AM Miro Hrončok wrote:
>>
>> On 16. 06. 23 15:39, Stephen Gallagher wrote:
>>> This leads me to my next schedule announcement: we will be performing
>>> the initial CentOS Stream 10 branch creation in Gitlab for all
>>> packages in the Fedor
Carlos O'Donell wrote:
> On 6/26/23 18:47, Jeff Law wrote:
>> What Red Hat has done may be technically legal and perhaps good for
>> its business. However, to me it's ethically unconscionable. Those
>> who know me know I'm not an zealot, but I do have a baseline set of
>> ethical values and Red
Hi,
Luya Tshimbalanga wrote:
> Hello team,
>
> While building opensubdiv, the failure[1] occurred on doc subpackage with
> the following line:
>
> BuildError: The following noarch package built differently on different
> architectures: opensubdiv-doc-3.5.0-1.fc38.noarch.rpm
> rpmdiff output was
Zbigniew Jędrzejewski-Szmek wrote:
> Yes, this is what I was talking about too. Because rpmbuild does not set
> %_sourcedir, it may fail to load some files. Even worse, it may load *wrong*
> versions, e.g. when some old version is present in the ~/rpmbuild/SOURCES/.
> Personally, I have dozens of s
Christopher Klooz wrote:
> A fresh installation of Fedora 37 has by default the "--supervised" option
> active in its gpg-agent systemd file
> (/usr/lib/systemd/user/gpg-agent.service).
>
> According to GnuPG Docs [1], this option is deprecated. Once gpg-agent is
> invoked, the log of "systemctl -
Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
>> 'git pull --rebase' is a strange command to suggest. I does the job,
>> but almost by accident, and it's confusing things by mixing in rebasing.
>> Can we make this just say 'git fetch' or 'git fetch -v' ?
>
> The thing is, you
Hi,
Globe Trotter via devel wrote:
> I have been trying to package slim again. The package does not come with a
> signature or a gpg key.
>
> From
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verification
> I don't see an option of what to do if there is no signat
Alexander Ploumistos wrote:
> On Mon, Feb 27, 2023 at 4:15 AM Globe Trotter via devel
> wrote:
>> I wonder if anyone has any suggestions on how to get
>> around this problem. I create my local repo using
>>
>> createrepo .
>>
>> inside my RPMS/x86_64 directory.
>
> Is there a specific reason you
Kenneth Goldman wrote:
> https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
> GNU_Hello/
>
> ~~~
>
> when running that tutorial (Fedora 37, x86), I get this error:
>
> ERROR: Exception(/home/kgold/hello/hello-2.10-1.fc37.src.rpm)
> Config(fedora-37-x
Petr Pisar wrote:
> [...] Either turn that directory into a git repository (git
> init-db . && git add hello.spec && git commit -a) ...
Just a minor, tangential nit, `git init` is the preferred
and documented command. The `git init-db` command is an
ancient name for it. The documentation for `gi
Tomas Korbar wrote:
> Extending the question here.
>
> -- Forwarded message -
> From: Tomas Korbar
> Date: Thu, Mar 9, 2023 at 9:51 AM
> Subject: License: GPL-3.0-or-later AND GPL-2.0-or-later
> To:
>
>
> Hi guys,
> I am doing the conversion of license tags in my projects and i
Hi,
Chris Kelley wrote:
> TL;DR dogtag-pki is not installable on F38/Rawhide because
> it fails the GPG check (F37 and prior are fine), even if
> --nogpgcheck is specified, and I don't understand why.
>
> 1) Why does the key not work?
> 2) Why does --nogpgcheck not work?
It seems like it must be
these additional packages:
asciidoc
git-filter-repo
rpmlint
Thanks,
--
Todd Zullinger
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://doc
Hi,
Michael J Gruber wrote:
> Thank you for all the effort you have put into maintaining these
> packages so far, for the benefit of all of Fedora, and consequently
> its downstream!
Thanks!
> Your reasons resonate with me, though I'm not taking the same
> conclusions. Have you arranged "success
Sérgio Basto wrote:
> On Tue, 2023-10-03 at 10:25 -0400, Todd Zullinger wrote:
>> a project
>> where the primary sponsor and downstream no longer provides
>> source code freely and openly
>
> what you are talking about ? all RHEL Source are freely available on
> Cent
Kevin Fenzi wrote:
> On Fri, Sep 16, 2022 at 10:03:35AM +0200, Vít Ondruch wrote:
>> Isn't peer review much better and easier solution over all? We could also
>> require signed commits I guess.
>
> I think it would slow things down quite a lot to require peer review of
> every commit.
>
> I'd pe
Miro Hrončok wrote:
> On 03. 10. 22 12:09, Vít Ondruch wrote:
>> And how is this change related to:
>>
>> https://src.fedoraproject.org/rpms/rpmlint/c/2beb19345e6644cb1b5ee8092b8533c8984cd21c?branch=rawhide
>
> I was unaware of this change at all.
>
> Tom, should rpmlint ditch that file instead
Hi,
Sergey Mende wrote:
>> Mildly related, I've been working on getting rpmlint updated
>> to 2.3.0 and now 2.4.0. I filed a PR to get comments from
>> other rpmlint maintainers and (hopefully) catch any bugs I
>> may have introduced:
>>
>> https://src.fedoraproject.org/rpms/rpmlint/pull-req
Hi,
Richard W.M. Jones wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=2042147#c2
> https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr
> https://bugzilla.redhat.com/2042099
>
> The RPM database is supposed to move from /var/lib/rpm to
> /usr/lib/sysimage/rpm. This was supposed to happe
Ian Laurie wrote:
> On 11/2/22 04:22, Dmitry Belyavskiy wrote:
>
> Dear colleagues,
>
> I've just pushed the updates for OpenSSL fixing 2 CVEs evaluated as HIGH.
> Could you please check the freshly pushed builds to get necessary karma
> ASAP?
>
> Are we not fixing Fedora 35? It
1 - 100 of 146 matches
Mail list logo
