$ sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync
Last metadata expiration check: 0:01:26 ago on Tue 03 Sep 2024 07:30:01 AM CDT.
Error:
Problem 1: problem with installed package signal-libringrtc-2.46.1-1.1.x86_64
- package signal-libringrtc-2.46.1-1.1.x86_64 from @
Additionally, see here:
https://stackoverflow.com/questions/63199763/maintained-alternatives-to-pypdf2
On Sunday, August 27, 2023 at 10:21:29 PM CDT, Globe Trotter via devel
wrote:
Thanks!
On Sun, Aug 27, 2023 at 5:39 AM Sandro wrote:
>
> On 27-08-2023 06:33, Globe Trott
Thanks!
On Sun, Aug 27, 2023 at 5:39 AM Sandro wrote:
>
> On 27-08-2023 06:33, Globe Trotter via devel wrote:
> > I am the maintainer of python-PyPDF2 for Fedora (which I do since I
> > was interested in pdf-stapler that I also maintain as a consequence).
> > For a whil
Hello,
I am the maintainer of python-PyPDF2 for Fedora (which I do since I was
interested in pdf-stapler that I also maintain as a consequence). For a while
now, upstream has been wanting all PyPDF2 users to pypdf. I was wondering how I
go about this for the F38 repos. Do I need to go through p
On Tuesday, May 16, 2023 at 03:30:03 AM CDT, Mamoru TASAKA
wrote:
Globe Trotter via devel wrote on 2023/05/15 23:36:
>> During unretirement of the package, I changed the dependency of slim from
>> desktop-backgrounds to f??-backgrounds-base in order to have a uniform
&
During unretirement of the package, I changed the dependency of slim from
desktop-backgrounds to f??-backgrounds-base in order to have a uniform
F-specific background for the slim login manager. However, the rawhide
installation can not find it. Any suggestions on what to do?
Thanks!
- Fo
un, May 14, 2023 at 02:04:57PM +0300, Benson Muite wrote:
> Ranjan,
>
> On 5/14/23 13:46, Globe Trotter via devel wrote:
> > Thanks! The package was cleared on BZ some time ago. Is there some
> > additional review that is needed?
> >
> Sorry, that is correct. Usuall
, Globe Trotter via devel wrote:
> Thanks, Kevin! No problem, no rush, I did not quite know what to expect,
> hence the questions. Thanks again!
>
>
It seems it is just the review that is needed:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_reti
Thanks, Kevin! No problem, no rush, I did not quite know what to expect, hence
the questions. Thanks again!
On Saturday, May 13, 2023 at 06:12:33 PM CDT, Kevin Fenzi
wrote:
On Sat, May 13, 2023 at 02:41:10AM +0200, Sandro wrote:
> On 11-05-2023 17:57, Globe Trotter via devel wr
Thanks, Sandro! How does one ping in the ticket on paguire?
On Friday, May 12, 2023 at 07:41:47 PM CDT, Sandro wrote:
On 11-05-2023 17:57, Globe Trotter via devel wrote:
> Still no movement on my unretire requests for both slim and oclock, not even
> a request for additional infor
Still no movement on my unretire requests for both slim and oclock, not even a
request for additional information.
On Sunday, May 7, 2023 at 10:50:42 AM CDT, Sandro wrote:
On 07-05-2023 17:34, Globe Trotter via devel wrote:
> How long does it take to unretire a package? I was think
I see, thanks! I had indeed forgotten that the previous request had been closed.
On Sunday, May 7, 2023 at 10:50:42 AM CDT, Sandro wrote:
On 07-05-2023 17:34, Globe Trotter via devel wrote:
> How long does it take to unretire a package? I was thinking that it
> was automatic, but
How long does it take to unretire a package? I was thinking that it was
automatic, but I have not received any notification yet. Did this request last
evening.
On Saturday, May 6, 2023 at 07:25:30 PM CDT, Globe Trotter via devel
wrote:
Thank you for this. I got:
fedpkg import
maybe not.
Thanks again!
On Saturday, May 6, 2023 at 04:52:55 PM CDT, Sandro
wrote:
On 06-05-2023 23:43, Sandro wrote:
> On 06-05-2023 19:36, Globe Trotter via devel wrote:
>> Can someone please review the oclock package? This was orphaned after
>> F35, and I package
Sorry, forgot the BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2025138
On Saturday, May 6, 2023 at 12:36:20 PM CDT, Globe Trotter
wrote:
Can someone please review the oclock package? This was orphaned after F35, and
I packaged it for myself, and then would like to put it up. It
Can someone please review the oclock package? This was orphaned after F35, and
I packaged it for myself, and then would like to put it up. It was tentatively
approved, but never finally done so. Thanks!
On Tuesday, November 23, 2021 at 02:43:00 PM CST, Björn Persson
wrote:
Ben Beasley
wrote:
On 06-05-2023 16:44, Globe Trotter via devel wrote:
> Right, but not pdf-stapler. I would have thought that that might be
> included too. Anyway, I am the maintainer for pdf-stapler so I can
> make myself aware, but I hope I will not be missing others.
Well, looking at the
Right, but not pdf-stapler. I would have thought that that might be included
too. Anyway, I am the maintainer for pdf-stapler so I can make myself aware,
but I hope I will not be missing others.
On Saturday, May 6, 2023 at 09:38:32 AM CDT, Sandro
wrote:
On 06-05-2023 16:29, Globe
that some of them may not respond.
On Saturday, May 6, 2023 at 09:01:28 AM CDT, Sandro
wrote:
On 06-05-2023 15:36, Globe Trotter via devel wrote:
> Is there an easy way to find out the reverse dependencies of a
> package (PyPDF2)? Should I contact the maintainers of these r
On Saturday, May 6, 2023 at 01:13:18 AM CDT, Paweł Marciniak
wrote:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages
Thanks!
Is there an easy way to find out the reverse dependencies of a package
(PyPDF2)? Should I contact the maintainers of
I am a co-maintainer (I think at least, I used to be co-) of PyPDF2 at least
for a while) or maintainer and I have noticed that the name has changed back to
pypdf (upstream). Is there an easy way to update the name of the package (in
the rpm) and importantly to make sure that the new pypdf rpm i
Did you find a co-maintainer for xfig? I use this package on and off and I
would not like to lose it.
On Tuesday, April 25, 2023 at 08:31:59 AM CDT, Hans de Goede
wrote:
Hi All,
I have been keeping the Fedora xfig package alive all these years
because I know that there are still use
2023 at 14:43, Globe Trotter via devel
wrote:
> Thank you for this!
>
> I set up
>
>
> $sudo dnf reposync
>
> and it is going on to do some sort of download for 69,222 (!) package?
>
> Is this correct? I seem to think that there are a bit more than 2,000
be
doing.
Thanks again!
On Tuesday, April 25, 2023 at 01:17:56 PM CDT, Stephen Smoogen
wrote:
On Tue, 25 Apr 2023 at 14:13, stan via devel
wrote:
> On Tue, 25 Apr 2023 17:30:28 + (UTC)
> Globe Trotter via devel wrote:
>
>> Is texlive-was-9 retired fo
Is texlive-was-9 retired for Fedora 38? My package did not upgrade from F37 and
so I was wondering about it.
Thanks
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code o
Btw, this is how I define my repo in the kickstart file:
repo --name=MyBaseRepo --baseurl=file:///home/itsme/rpmbuild/RPMS/$basearch
I have never had this issue before, even as recently as a week ago.
Thanks!
On Sunday, February 26, 2023 at 09:52:07 PM CST, Globe Trotter via devel
wrote
OK, I tried createrepo_c . but I get the same error.
Here is what I tried:
createrepo_c --update .
And now, nothing from the local repo come in.
Suggestions?
On Sunday, February 26, 2023 at 09:27:13 PM CST, Alexander Ploumistos
wrote:
On Mon, Feb 27, 2023 at 4:15 AM Globe
:03 AM CST, Globe Trotter via devel
wrote:
Hello,
I was using livecd-creator, and I get the following for local recently rebuilt
packages, but not for those built a few weeks ago.
Specifically, I get:
Package "wbar-2.3.4-2.fc37.x86_64" from local repository "MyBaseRepo&
Excellent, thank you. no, I am not planning to maintain EPEL branches.
On Sunday, February 26, 2023 at 07:53:08 PM CST, Alexander Ploumistos
wrote:
On Mon, Feb 27, 2023 at 2:39 AM Globe Trotter via devel
wrote:
> I am writing a spec file for SliM, the Simple Login Manager for Fed
Hi,
I am writing a spec file for SliM, the Simple Login Manager for Fedora 37. I
was thiniking of changing the default login image to the Fedora one. It appears
that that is stored in the RPM: f37-backgrounds-base and the file is
/usr/share/backgrounds/f37/default/f37-01-day.png
So, my quest
To answer my own question, by the trial-and-error method, it seems that the
current default needs to be taken out from the conf file.
On Sunday, February 26, 2023 at 02:48:52 PM CST, Globe Trotter via devel
wrote:
Sorry, I had a question on the xserver_arguments in the slim.conf file
Should the xserver_arguments be modified/removed in a patch? Or left as is?
Thanks!
On Sunday, February 26, 2023 at 10:44:38 AM CST, Todd Zullinger
wrote:
Hi,
Globe Trotter via devel wrote:
> I have been trying to package slim again. The package does not come with a
> signature or
Sorry, forgot to add: I will ask the slim-fork maintainer if he will sign the
release tarballs.
On Sunday, February 26, 2023 at 10:51:14 AM CST, Globe Trotter via devel
wrote:
Todd,
I only became aware of this fork yesterday, and have packaged it and put it on
bugzilla:
https
, 2023 at 10:44:38 AM CST, Todd Zullinger
wrote:
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_ve
Feb 26, 2023, at 11:02 AM, Globe Trotter via devel
> wrote:
>
> Hello,
>
> 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_
Hello,
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 signature provided.
Any suggestions or point
Hi,
I have filed a BZ request for unretiring slim. It is at:
https://bugzilla.redhat.com/show_bug.cgi?id=2173236
Can someone please review it?
Best!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@li
Hello,
I was using livecd-creator, and I get the following for local recently rebuilt
packages, but not for those built a few weeks ago.
Specifically, I get:
Package "wbar-2.3.4-2.fc37.x86_64" from local repository "MyBaseRepo" has
incorrect checksum
Error creating Live CD : Unable to insta
Looks good here too:
Downgrading:
Lmod x86_64 8.7.18-1.fc38 fedora 258 k
festival-data noarch 2.5.0-16.fc38 fedora 1.2 M
fwupd x86_64 1.8.10-1.fc38 fedora 1.8 M
fwupd-plugin-flashrom
According to
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming
unretiring a package requires review if retired for more than eight weeks.
According to releng, the package slim has been retired for 6+ weeks. Do I still
need to ask for review of this p
, Neal Gompa
wrote:
On Sun, Feb 19, 2023 at 9:33 PM Globe Trotter via devel
wrote:
>
> Hello,
>
> Since about Fedora 20 or so, I have been rolling my own Fedora spin without a
> desktop environment, and with openbox and slim (simple login manager). All
> worked well, beca
.
Looking at the i3 desktop kickstart file, I tried using lightdm (just to see
how I fare):
%post
systemctl enable lightdm
# create /etc/sysconfig/desktop (needed for installation)
cat > /etc/sysconfig/desktop < wrote:
On Tue, 2023-02-21 at 16:34 +, Globe Trotter via devel
t with F34 here:
$ fpaste fedora-live-shunya-old.ks
Uploading (3.3KiB)...
https://paste.centos.org/view/34c9dfe3
This has the same effect as the new one. At least, that is what it looks like.
Many thanks!
On Sunday, February 19, 2023 at 11:18:38 PM CST, Globe Trotter via devel
wrote:
Thanks for this. But this is separate. I was wondering how do I create a LiveCD
without a login display manager?
On Tuesday, February 21, 2023 at 07:59:27 AM CST, Sandro
wrote:
On 20-02-2023 22:09, Globe Trotter via devel wrote:
> I would be happy to unretire it if that is possi
PM CST, Sérgio Basto
wrote:
On Mon, 2023-02-20 at 02:28 +, Globe Trotter via devel wrote:
> Hello,
>
> Since about Fedora 20 or so, I have been rolling my own Fedora spin
> without a desktop environment, and with openbox and slim (simple
> login manager). All worked well
, Globe Trotter via devel
wrote:
On Sunday, February 19, 2023 at 09:25:50 PM CST, Neal Gompa
wrote:
On Sun, Feb 19, 2023 at 9:33 PM Globe Trotter via devel
wrote:
>
> Hello,
>
> Since about Fedora 20 or so, I have been rolling my own Fedora spin without a
> desktop e
On Sunday, February 19, 2023 at 09:25:50 PM CST, Neal Gompa
wrote:
On Sun, Feb 19, 2023 at 9:33 PM Globe Trotter via devel
wrote:
>
> Hello,
>
> Since about Fedora 20 or so, I have been rolling my own Fedora spin without a
> desktop environment, and with openbox and sli
Hello,
Since about Fedora 20 or so, I have been rolling my own Fedora spin without a
desktop environment, and with openbox and slim (simple login manager). All
worked well, because I did not need to roll these that often, with dnf upgrade
on existing installations, except up until now when I ne
Corsépius
wrote:
Am 19.07.22 um 16:45 schrieb Globe Trotter via devel:
> Thanks, btw, the command here says unknown command (see below).
>
> Btw, the log is here:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683
The trigger of this breakdown is the
-07-19 09:44:16,973 [ERROR] koji: Unknown command: save-failed-tree
On Tuesday, July 19, 2022 at 09:40:23 AM CDT, Jerry James
wrote:
On Tue, Jul 19, 2022 at 7:52 AM Globe Trotter via devel
wrote:
> checking whether the C compiler works... no
> configure: error: in `/build
g.log' for more details
Where is the config.log? I only have
build.log (tail)
hw_info.log (tail)
mock_output.log (tail)
root.log (tail)
state.log (tail)
Thanks again!
On Tuesday, July 19, 2022 at 08:33:57 AM CDT, Globe Trotter via devel
wrote:
Hello,
I was trying to fix a
g.log' for more details
Where is the config.log? I only have
build.log (tail)
hw_info.log (tail)
mock_output.log (tail)
root.log (tail)
state.log (tail)
Thanks again!
On Tuesday, July 19, 2022 at 08:33:57 AM CDT, Globe Trotter via devel
wrote:
Hello,
I was trying to fix a
Hello,
I was trying to fix a minor but severe error in the packging of osmo, and I get
the following error:
$ fedpkg import ~/rpmbuild/SRPMS/osmo-0.4.4-2.fc36.src.rpm
Could not execute import_srpm: (52, 'Empty reply from server')
Where is this error from and how do I get around it?
Thanks
Btw, I assume that i should call it xfontsel.gpg, or should I rename it too?
Thanks!
On Sunday, April 17, 2022, 10:50:37 AM CDT, Globe Trotter via devel
wrote:
Thanks very much! I will do this today.
On Sunday, April 17, 2022, 09:12:15 AM CDT, Björn Persson
wrote:
Ben
Thanks very much! I will do this today.
On Sunday, April 17, 2022, 09:12:15 AM CDT, Björn Persson
wrote:
Ben Beasley wrote:
> Please see
> https://src.fedoraproject.org/rpms/xfontsel/blob/a38f5a42fa7bc59378527cf05dabe29523675613/f/xfontsel.spec#_10
> for an example from the same grou
On Sunday, April 17, 2022, 05:26:52 AM CDT, Maxwell G via devel
wrote:
> Apr 16, 2022 8:01:27 PM Globe Trotter via devel
> :
>> Source1: %{source0}.sig
> Does this still fail if you use the full path? It looks like `%{source0}`
> isn't getting expanded
Hi,
I am trying to pakage oclock for Fedora. According to the packaging guidelines
I need to have a gpg key.
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verification
So, the package itself comes with a oclock-1.0.4.tar.gz.sig (from upstream).
How do I use this?
I tr
comments in the spec file. SKS keyservers have
gone offline since that package obtained its keyring, so try using
hkps://keys.openpgp.org instead.
That package also uses rpmautospec.
On Mon, Nov 22, 2021, at 7:02 PM, Globe Trotter via devel wrote:
> Thank you to Dan Čermák for reviewing this pack
in the long run. I like that of course, but I am
trying to understand where this is used?
Thanks for any advice!
On Monday, November 22, 2021, 04:21:59 PM CST, Globe Trotter via devel
wrote:
Hello,
Anyone willing to review this request for a recently (>8 weeks) orphaned
pack
Hello,
Anyone willing to review this request for a recently (>8 weeks) orphaned
package?
https://bugzilla.redhat.com/show_bug.cgi?id=2025138
Happy to review in return.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an emai
return, of course.
Thanks,
aa...@fedoraproject.org
On Saturday, November 20, 2021, 08:30:24 AM CST, Globe Trotter via devel
wrote:
Thank you, the BZ report is here:
https://bugzilla.redhat.com/show_bug.cgi?id=2025138
I am already a packager of other packages so I believe that I do not
, 2021-11-19 at 18:06 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Nov 19, 2021 at 01:57:12PM +0000, Globe Trotter via devel
> wrote:
> > I opened the following:
> >
> > https://pagure.io/releng/issue/10396
> >
> > I am not quite sure what happens after
:17AM +, Globe Trotter via devel wrote:
> Hi,
>
> As the name says, this is a review request for the orphaned package oclock. I
> find that the old spec file from F34 complies without errors and so would
> like to maintain it. But first, I need a review. Could someone please hel
Hi,
As the name says, this is a review request for the orphaned package oclock. I
find that the old spec file from F34 complies without errors and so would like
to maintain it. But first, I need a review. Could someone please help review
the package?
Thanks,
aa...@fedoraproject.org.
chmod 0755 public_html'
to make sure the directory exists with the correct permissions.
On 11/19/21 19:33, Globe Trotter via devel wrote:
> Hello,
>
> I have been trying to upload a couple of my files to my fedorapeople.org
> space following the instructions here:
> https
Hello,
I have been trying to upload a couple of my files to my fedorapeople.org space
following the instructions here:
https://fedoraproject.org/wiki/Infrastructure/fedorapeople.org#fedorapeople.org
and have been confused.
Actually, I go to my https://aarem.fedorapeople.org/ account and get:
replies below...
On Wed, Nov 10, 2021 at 09:48:24PM +, Globe Trotter via devel wrote:
>My apologies, i spoke too soon.
>
>I updated Makefile.in to be:
>
>install: gbuffy
> ./mkinstalldirs $(DESTDIR)$(bindir)
> $(INSTALL) gbuffy $(DESTDIR)$(bindir)
>
>Here is my update
I opened the following:
https://pagure.io/releng/issue/10396
I am not quite sure what happens after this, so I thought that I would mention
this here.
Thanks!
On Friday, November 19, 2021, 07:07:43 AM CST, Globe Trotter via devel
wrote:
Oh, the package is called pkgconfig(xorg
Oh, the package is called pkgconfig(xorg-macros), sorry for the goofup.
OK, oclock builds, I have filed a ticket on releng to unorphan the package.
On Friday, November 19, 2021, 03:39:37 AM CST, Björn 'besser82' Esser
wrote:
Am Freitag, dem 19.11.2021 um 06:17 +0000 sch
Hi,
oclock has been orphaned from F35 so i was trying to roll my own rpm (building
off the spec file for F34). I noticed that the spec file contains:
BuildRequires: pkgconfig(xorg-macros) >= 1.8
but I can not find this in the F34 repos. Where do I get this? If I succeed
with rolling a oclock
Actually, it turns out that the chmod is still needed. Fixed with the following
specfile:
%define ver 0.2.8
%define rel 1%{?dist}
Summary: multiple mailbox buffy for GTK+
Name: gbuffy
Version: %ver
Release: %rel
License: GPL
Group: Applications/Communications
Source0: ~/C.libs/linux/%{name
My apologies, i spoke too soon.
I updated Makefile.in to be:
install: gbuffy
./mkinstalldirs $(DESTDIR)$(bindir)
$(INSTALL) gbuffy $(DESTDIR)$(bindir)
Here is my updated spec file:
%define ver 0.2.8
%define rel 1%{?dist}
Summary: multiple mailbox buffy for GTK+
Name: g
Thanks!
> On Wednesday, November 10, 2021, 03:10:43 PM CST, David Cantrell
> wrote:
>This is common practice in older projects. You have a couple of options:
> 1) Patch Makefile.in to honor DESTDIR. Make the install target look ike this:
install: gbuffy
./mkinstalldirs $(DESTDIR)$
> On Wednesday, November 10, 2021, 02:47:17 PM CST, Artur Frenszek-Iwicki
> wrote:
>> ./mkinstalldirs /usr/bin
>> make: ./mkinstalldirs: Permission denied
> This sounds like "mkinstalldirs" is not executable, perhaps a simple "chmod
> +x mkinstalldirs" will be enough?
Thanks very much!
Ah!
S
Hi,
I have been trying to create a rpm for gbuffy which I like. However, I am
hitting an error in the install directories.
The program is at:
http://www.fiction.net/blong/programs/gbuffy/
Here is my specfile:
# Note that this is NOT a relocatable package
%define ver 0.2.6
%define rel 1%
Thanks, this has addressed the problem.
On Wednesday, September 22, 2021, 10:52:28 AM CDT, Dan Horák
wrote:
On Wed, 22 Sep 2021 15:43:36 + (UTC)
Globe Trotter via devel wrote:
>
>
>
>
>
> >On Wednesday, September 22, 2021, 08:32:05 AM CDT, Vit
>On Wednesday, September 22, 2021, 08:32:05 AM CDT, Vitaly Zaitsev via devel
> wrote:
> On 22/09/2021 15:24, Globe Trotter via devel wrote:
>> So, it appears that there is a standard /usr/lib64? But is it being set
>> directly by the spec file? How do I unse
> On Wednesday, September 22, 2021, 08:32:05 AM CDT, Vitaly Zaitsev via devel
> wrote:
> On 22/09/2021 15:24, Globe Trotter via devel wrote:
> So, it appears that there is a standard /usr/lib64? But is it being set
>directly by the spec file? How do I unset it?
Hi,
I was notified some time ago that sylfilter is FTBFS in Fedora Rawhide. So, I
was looking at the build log, and I got this:
.
+ /usr/lib/rpm/check-rpaths
***
*
* WARNING: 'check-rpaths' detected a broken RPATH O
Hi,
Ny kickstart file has the following:
%include /usr/share/spin-kickstarts/fedora-live-base.ks
%include /usr/share/spin-kickstarts/fedora-live-minimization.ks
But I have noticed that it wants to go into the rawhide repo. That is because
/usr/share/spin-kickstarts/fedora-live-base.ks has fedo
Thanks! How do I get around this issue?
I have setenforce set at 0.
Also, why does the issue go away when I reduce the packages to be packed in the
remix/spin?
On Monday, May 18, 2020, 5:26:35 AM CDT, Petr Pisar
wrote:
On Mon, May 18, 2020 at 12:07:38AM +, Globe Trotter via
uncommented. This is a strange default to have.
On Sunday, May 17, 2020, 7:31:43 PM CDT, Samuel Sieb
wrote:
On 5/17/20 5:27 PM, Globe Trotter via devel wrote:
> Sorry, during build. Also, no, I don't think that i am using /tmp for
> tmpdir. I am using a local directory
Sorry, during build. Also, no, I don't think that i am using /tmp for tmpdir.
I am using a local directory called tmp.
On Sunday, May 17, 2020, 7:16:09 PM CDT, Samuel Sieb
wrote:
On 5/17/20 5:07 PM, Globe Trotter via devel wrote:
> Thanks! Adding "--releasever=32&qu
5:18:55 PM CDT, Samuel Sieb
wrote:
On 5/17/20 12:58 PM, Globe Trotter via devel wrote:
> sudo livecd-creator --config=fedora-live-shunya-32.ks --tmpdir=tmp
> --fslabel=Fedora-Shunya-32-x86_64
Why do you think it's getting rawhide files? I don't see any reason why
sudo livecd-creator --config=fedora-live-shunya-32.ks --tmpdir=tmp
--fslabel=Fedora-Shunya-32-x86_64
On Sunday, May 17, 2020, 2:57:44 PM CDT, Samuel Sieb
wrote:
On 5/17/20 12:46 PM, Globe Trotter via devel wrote:
> My apologies. I am running on Fedora 32. My kickstart file is
g
# we need UPower for suspend and hibernate
upower
%end
On Sunday, May 17, 2020, 1:49:10 PM CDT, Samuel Sieb
wrote:
On 5/17/20 8:39 AM, Globe Trotter via devel wrote:
> I am trying to build a spin/remix but I keep running into the problem
> that rawhide is being pulled
Hi,
I am trying to build a spin/remix but I keep running into the problem that
rawhide is being pulled in. Nowhere do I include it. I simply use, in my ks
file:
repo --name=fedora
--mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
repo --name=update
Hello,
I have been trying to package franz from here:
https://github.com/meetfranz/franz/archive/v5.5.0.tar.gz
and I have the following spec file at:
UNTITLED - Pastebin Service
|
|
| |
UNTITLED - Pastebin Service
|
|
|
However, I get a bunch of warnings and errors and I am not sure
Thanks! Yes, I believe that I took it from someone (can't recall who). Crikes,
rewriting a spec file to make it up to date may not be that easy for me. Let us
see.
Thanks again!
On Tuesday, March 31, 2020, 9:17:01 PM CDT, Richard Shaw
wrote:
On Tue, Mar 31, 2020 at 9:05 PM
Hi,
I am the maintainer of slim. As per BZ and here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=41322154
slim was unable to build BuildError: error building package (arch armv7hl),
mock exited with status 1; see root.log for more information However, I can not
figure out where to see th
package.
Thanks!
On Monday, December 30, 2019, 11:08:55 AM CST, Tom Hughes
wrote:
On 30/12/2019 16:42, Globe Trotter via devel wrote:
> I use slim and have realized that it is retired/no longer supoorted from
> F31.
>
> So, I got the src.rpm from teh F30 stable and was tryin
Hi,
I use slim and have realized that it is retired/no longer supoorted from F31.
So, I got the src.rpm from teh F30 stable and was trying to rebuild it at least
to see what the issues were.
However, the rpmbuild
$ rpmbuild -bb slim.spec
error: This macro requires some arguments
I have never
Thanks, I will ignore it then.
On Sunday, December 29, 2019, 9:14:54 AM CST, Kevin Fenzi
wrote:
On Sun, Dec 29, 2019 at 02:45:20PM +, Globe Trotter via devel wrote:
> I got the following:
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-2b1eed3d9d
> Failed t
.
On Sat, Dec 28, 2019, 15:12 Globe Trotter via devel
wrote:
Thanks! There was an issue with koji and me. Now the update has been built and
submitted for testing. Should I fix the egg issue? How.Thanks!
I am not sure there is an "egg issue", but that's something you should
Ploumistos
wrote:
You are welcome. Sorry for the HTML, I am away from home.
On Sat, Dec 28, 2019, 15:12 Globe Trotter via devel
wrote:
Thanks! There was an issue with koji and me. Now the update has been built and
submitted for testing. Should I fix the egg issue? How.Thanks!
I am not sur
Thanks! There was an issue with koji and me. Now the update has been built and
submitted for testing. Should I fix the egg issue? How.Thanks!
On Saturday, December 28, 2019, 3:34:30 AM EST, Alexander Ploumistos
wrote:
On Sat, Dec 28, 2019 at 7:35 AM Globe Trotter via devel
wrote
ed to declare PKG-INFO as documentation? It's
included with the egg metadata. If you remove it from your %files
section, the package builds fine. If you are intent on keeping it
declared, you will have to copy it to your buildroot (I think).
On Fri, Dec 27, 2019 at 5:04 PM Globe Trotter via de
Thanks!
On Friday, December 27, 2019, 9:32:29 AM CST, José Abílio Matos
wrote:
> in lines 43-44 you have:
> %prep
> %setup -q -n stapler-%{version}
> the last line should be:
> %setup -q -n stapler
as you said the directory name does not have the version in it. :-)
I tried:
%setup
such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.2ZnEy2 (%prep)
Thanks again for your help!
On Friday, December 27, 2019, 3:08:05 AM CST, Alexander Ploumistos
wrote:
Hello,
On Fri, Dec 27, 2019 at 7:44 AM Globe Trotter via devel
wrote:
>
> However, I
On Thursday, December 26, 2019, 10:34:12 AM CST, José Abílio Matos
wrote:
> Something weird in your spec file is that it has two source files:
> Source0: https://pypi.python.org/packages/source/s/stapler/stapler-%
{version}.tar.bz2
> Source1: https://github.com/hellerbarde/sta
1 - 100 of 147 matches
Mail list logo
