8:15 a.m.
Hi,
I tried the following:
$ kinit mufti11(a)FEDORAPROJECT.ORG
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
$ git commit -sm "Initial import (#1658153)"
error: gpg failed to sign the data
fatal: failed to write commit object
$ fedpkg push
Everything up-to-date
$ fedpkg build
Could not execute build: /home/home/mufti/wdune has uncommitted
changes. Use git status to see details
Try option --srpm to make scratch build from local changes.
$
I updated the gpg keys with
curl https://getfedora.org/static/fedora.gpg | gpg --import
9:20 a.m.
On Mon, Dec 23, 2019, 16:16 J. Scheurich <mufti11(a)web.de> wrote:
Hi,
I tried the following:
$ kinit mufti11(a)FEDORAPROJECT.ORG
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
$ git commit -sm "Initial import (#1658153)"
You do not need to sign your git commits.
error: gpg failed to sign the data
fatal: failed to write commit object
So the commit probably failed because git couldn't find a GPG associated
with your email address.
$ fedpkg push
Everything up-to-date
And then without a successful commit, there's nothing to push ....
$ fedpkg build
Could not execute build: /home/home/mufti/wdune has uncommitted
changes. Use git status to see details
Try option --srpm to make scratch build from local changes.
And you can't build stuff that you haven't pushed yet.
$
I updated the gpg keys with
curl https://getfedora.org/static/fedora.gpg | gpg --import
Why would you want to sign your commits with fedora GPG keys, and not your
own key? And those are the public keys, they wouldn't help you either way
...
Just skip the -s argument in "git commit".
Fabio
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
9:44 a.m.
I tried the following:
$ kinit mufti11(a)FEDORAPROJECT.ORG <mailto:mufti11@FEDORAPROJECT.ORG>
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm >
/dev/null
$ git commit -sm "Initial import (#1658153)"
You do not need to sign your git commits.
error: gpg failed to sign the data
fatal: failed to write commit object
So the commit probably failed because git couldn't find a GPG
associated with your email address.
Why would you want to sign your commits with fedora GPG keys, and
not
your own key? And those are the public keys, they wouldn't help you
either way ...
I think ,my gpg key are up to date.
How to proove it ?
Just skip the -s argument in "git commit".
$ git commit
error: gpg failed to sign the data
fatal: failed to write commit object
Same problem 8-(
so long
MUFTI
10:58 a.m.
On Mon, Dec 23, 2019, 17:45 J. Scheurich <mufti11(a)web.de> wrote:
I tried the following:
>
> $ kinit mufti11(a)FEDORAPROJECT.ORG
> rm -rf wdune
> fedpkg clone wdune
> cd wdune
> $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
>
> $ git commit -sm "Initial import (#1658153)"
>
You do not need to sign your git commits.
error: gpg failed to sign the data
> fatal: failed to write commit object
>
So the commit probably failed because git couldn't find a GPG associated
with your email address.
Why would you want to sign your commits with fedora GPG keys, and not your
own key? And those are the public keys, they wouldn't help you either way
...
I think ,my gpg key are up to date.
How to proove it ?
Just skip the -s argument in "git commit".
$ 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 or something.
so long
MUFTI
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
12:42 p.m.
Fabio Valentini wrote:
On Mon, Dec 23, 2019, 17:45 J. Scheurich <mufti11(a)web.de>
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 or something.
The --show-origin option to git config is handy for finding
where you've set the option. E.g.:
git config --show-origin --get commit.gpgSign
--
Todd
1:18 p.m.
Hi,
I tried the following:
$ kinit mufti11(a)FEDORAPROJECT.ORG
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null
$ git commit -sm "Initial import (#1658153)"
error: gpg failed to sign the data
fatal: failed to write commit object
$ fedpkg push
Everything up-to-date
$ fedpkg build
Could not execute build: /home/home/mufti/wdune has uncommitted
changes. Use git status to see details
Try option --srpm to make scratch build from local changes.
$
I updated the gpg keys with
curl https://getfedora.org/static/fedora.gpg | gpg --import
Why don't you listen to your sponsors advise?
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
If I was your sponsor I would consider withdrawing your packager status.
Try reverting your first commit as it's garbage, you never upload the unpacked source
files!
https://src.fedoraproject.org/rpms/wdune/tree/master
rm -rf wdune
fedpkg clone wdune
cd wdune
git revert -1 HEAD
git push
then do it properly
fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm
git commit -am "Initial import (#1658153)"
2:11 p.m.
On Mon, Dec 23, 2019 at 07:18:24PM -0000, Leigh Scott wrote:
Why don't you listen to your sponsors advise?
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
If I was your sponsor I would consider withdrawing your packager status.
Try reverting your first commit as it's garbage, you never upload the unpacked source
files!
https://src.fedoraproject.org/rpms/wdune/tree/master
rm -rf wdune
fedpkg clone wdune
cd wdune
git revert -1 HEAD
git push
then do it properly
fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm
git commit -am "Initial import (#1658153)"
Things can be overwealming at first. I also urge you to work with your
sponsor, they can help you get things back on track. :)
Failing that, if you need more real time help, you can drop by
#fedora-devel on irc.freenode.net (
https://fedoraproject.org/wiki/Communicating_and_getting_help#IRC_for_int...
), there's almost always someone around there who can help out.
Ask questions and be patient.
Welcome to packaging!
kevin
2:29 p.m.
Hi,
I got
$ fedpkg build
for wdune running, but what i need to publish it ?
So i can install it with
# yum install wdune
?
so long
MUFTI
3:45 p.m.
On Monday, 23 December 2019 21:29:41 CET J. Scheurich wrote:
Hi,
I got
$ fedpkg build
for wdune running, but what i need to publish it ?
So i can install it with
# yum install wdune
?
so long
MUFTI
Check the results of your build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=39898232
It failed because it depends on vcglib that you haven't build yet.
1:24 a.m.
$ fedpkg build --target f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=39903543
Result
BuildError: package wdune not in list for tag f31-updates-candidate
What has to be done, to bring wdune to fedora 31 ?
so long
MUFTI
1:45 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
Hi,
$ fedpkg build --target f32
was successfull.
# lsb_release -a | grep Release
Release: 32
# yum search wdune
Last metadata expiration check: 1:42:31 ago on Tue 24 Dec 2019 06:59:24
AM CET.
No matches found.
What is needed to add wdune to fedora 32 ?
so long
MUFTI
2:49 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
On 24/12/2019 07:45, J. Scheurich wrote:
$ fedpkg build --target f32
was successfull.
# lsb_release -a | grep Release
Release: 32
# yum search wdune
Last metadata expiration check: 1:42:31 ago on Tue 24 Dec 2019 06:59:24
AM CET.
No matches found.
What is needed to add wdune to fedora 32 ?
A successful build would be a good start.
The only build on koji at the moment is a failed one:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1424721
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
2:43 a.m.
$ fedpkg build --target f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=39903543
Result
BuildError: package wdune not in list for tag f31-updates-candidate
What has to be done, to bring wdune to fedora 31 ?
Try reading
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
fedpkg request-branch --repo wdune f31
fedpkg request-branch --repo wdune f30
> so long
> MUFTI
3:31 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
Hi,
| fedpkg request-branch --repo wdune f31
| fedpkg request-branch --repo wdune f30
$ fedpkg request-branch --repo wdune f31
Could not execute request_branch: Missing a Pagure token. Refer to
"fedpkg request-repo -h" to set atoken in your user configuration.
I created a new token at https://pagure.io/settings/token/new and
inserted it in ~/.config/rpkg/fedpkg.conf
???
so long
MUFTI
3:38 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
Hi,
| fedpkg request-branch --repo wdune f31
| fedpkg request-branch --repo wdune f30
$ fedpkg request-branch --repo wdune f31
Could not execute request_branch: Missing a Pagure token. Refer to
"fedpkg request-repo -h" to set atoken in your user configuration.
I created a new token at https://pagure.io/settings/token/new and
inserted it in ~/.config/rpkg/fedpkg.conf
???
so long
MUFTI
Try ticking all the ACLs boxes when you create the Pagure token
3:42 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
Hi,
$ fedpkg request-branch --repo wdune f31
Could not execute request_branch: Missing a Pagure token. Refer to
"fedpkg request-repo -h" to set atoken in your user configuration.
$ fedpkg request-repo wdune
Could not execute request_repo: A Bugzilla bug is required on new
repository requests
$
I adeded it a dummy bug
https://bugzilla.redhat.com/show_bug.cgi?id=1786307
but no effect 8-(
so long
MUFTI
4:51 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
The correct bug would be this, I think:
https://bugzilla.redhat.com/show_bug.cgi?id=1658153
$ fedpkg request-repo wdune
Could not execute request_repo: A Bugzilla bug is required on new
repository requests
$
I adeded it a dummy bug
https://bugzilla.redhat.com/show_bug.cgi?id=1786307
but no effect 8-(
- Thomas
5 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
* J. Scheurich [24/12/2019 10:42] :
$ fedpkg request-branch --repo wdune f31
Could not execute request_branch: Missing a Pagure token. Refer to
"fedpkg request-repo -h" to set atoken in your user configuration.
You need to get a new token. Go to
https://src.fedoraproject.org/settings/token/new
Click the "Toggle all" button then the "Create button" and copy-paste
the resulting API key in .config/rpkg/fedpkg.conf
Emmanuel
5 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
https://koji.fedoraproject.org/koji/packageinfo?tagOrder=extra_arches&...
**
| Information for package wdune
| f32 releng yes
Maybe this could be a problem ?
so long
MUFTI
6:03 a.m.
New subject: Final fedora distribution Was: How to reuild wdune ?
On Tue, Dec 24, 2019 at 11:43 AM J. Scheurich <mufti11(a)web.de> wrote:
Hi,
$ fedpkg request-branch --repo wdune f31
Could not execute request_branch: Missing a Pagure token. Refer to
"fedpkg request-repo -h" to set atoken in your user configuration.
$ fedpkg request-repo wdune
Could not execute request_repo: A Bugzilla bug is required on new
repository requests
$
I adeded it a dummy bug
https://bugzilla.redhat.com/show_bug.cgi?id=1786307
but no effect 8-(
Why are you trying to create the repo again? You already have it:
https://src.fedoraproject.org/rpms/wdune
And from the looks of it, you have not even attempted to read the
documentation we pointed you to ...
1. First, you imported the exploded upstream tarball into dist-git
2. you removed them (which is good)
3. then you reimported all the sources (BUT WHY) and removed the .spec
file from the repo (uhm ...?)
4. with the next commit you added back the .spec file but also
committed some temporary (config.*) files that are spit out by the
build (??)
5. and with the last commit you removed the BuildRequires that aren't
available in koji yet, because you haven't built them first (that
won't help you to get this building ...) and even committed the bodhi
update template ...
So, to summarize: Please just STOP what you're doing right now, and
wait (possibly until after the holidays) until your sponsor can help
you get this sorted out. If you continue like this, you won't get
anywhere. We've been trying to help you, but clearly it's not working
out.
Fabio
> so long
> MUFTI
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
1586
days inactive
1587
days old
20 comments
10 participants
participants (10)
-
Emmanuel -
Fabio Valentini -
J. Scheurich -
Kevin Fenzi -
Leigh Scott -
Robert-André Mauchin -
Thomas Moschny -
Todd Zullinger -
Tom Hughes -
Vitaly Zaitsev