How to check if someone is already working on a package/ Self Introduction
by James Harshaw
Hello, my name is James Wilson Harshaw IV, but I usually go by bits3rpent.
I am a programmer who is looking to really wanting to get involved in
open source projects.
I recently was looking at some of the requests for software on the
Fedora Security Spin page, and I found a software that I also would
like, reaver-wps.
I am currently learning how to package software with SRPMS and SPEC
files, but I want to see if anyone is already working on packaging
reaver-wps before I start.
Is there anyway to check if someone is working on it? I did a quick bug
search on bugzilla and got this
"
* *Status:* NEW, VERIFIED, ASSIGNED, MODIFIED, ON_DEV, ON_QA,
RELEASE_PENDING, POST
* *Product:* reaver-wps
* *Component:* reaver-wps
* *Alias:* reaver-wps
* *Summary:* reaver-wps
* *Whiteboard:* reaver-wps
* *Content:* "reaver-wps"
"
Thanks in advance for your answers.
-bits3rpent
10 years, 6 months
guidelines for go?
by Matthew Miller
I've been asked to help package / review a project written in Go. Since the
language is new, we don't have packaging guidelines (unless I've missed
them!), and I'm a Go newbie myself, so I'm left with some questions.
The first question I have is over the location of packages -- the library
modules. The ones that are part of golang are under
%{_libdir}/golang/src/pkg. Should third-party packages go alongside, or
% elsewhere?
Also it appears that Go programs compiled with the canonical golang are
statically linked
(http://golang.org/doc/faq#Why_is_my_trivial_program_such_a_large_binary).
Gccgo supports dynamic linking, but I'm not sure about compatibility issues.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 6 months
lightdm
by poma
Removin buntu's residues from the 'lightdm-1.7.12-fedora_config.patch'.
poma
10 years, 7 months
lightdm-gtk
by poma
Alignin of the 'lightdm-gtk-greeter-1.5.2-bg_crash.patch',
…
patching file src/lightdm-gtk-greeter.c
Hunk #1 succeeded at 1367 (offset 14 lines).
…
poma
10 years, 7 months
Naming policy for adding language translation packages
by Parag Nemade
Hi,
I see that we are getting more and more translations packages in Fedora
and those can be installed now via yum-langpacks plugin. I found that these
packages are not following uniqueness in their naming. e.g. If I look into
Russian language translation packages then we have real fedora package
names as
tesseract-langpack-rus
kde-l10n-Russian
libreoffice-langpack-ru
childsplay-alphabet_sounds_ru
My suggestion is we should have some naming guidelines like use language
codes for language translation packages e.g. for Russian language your
package should end with "-ru" only.
We should have some uniqueness in package names.
Regards,
Parag.
10 years, 7 months
up* httrack
by poma
# yum update httrack
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package httrack.i686 0:3.43.9-7.fc20 will be updated
---> Package httrack.i686 0:3.47.26-2.fc21 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository
Size
================================================================================
Updating:
httrack i686 3.47.26-2.fc21 rawhide
637 k
Transaction Summary
================================================================================
Upgrade 1 Package
Total size: 637 k
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/share/httrack/html from install of
httrack-3.47.26-2.fc21.i686 conflicts with file from package
httrack-3.43.9-7.fc20.i686
Error Summary
-------------
# dnf upgrade httrack
Setting up Upgrade Process
Resolving dependencies
--> Starting dependency resolution
---> Package httrack.i686 3.43.9-7.fc20 will be upgraded
---> Package httrack.i686 3.47.26-2.fc21 will be an upgrade
--> Finished dependency resolution
Dependencies resolved.
================================================================================
Package Arch Version Repository
Size
================================================================================
Upgrading:
httrack i686 3.47.26-2.fc21 rawhide
637 k
Transaction Summary
================================================================================
Upgrade 1 Package
Total download size: 637 k
Is this ok [y/N]: y
Downloading Packages:
httrack-3.47.26-2.fc21.i686.rpm | 637 kB
00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Upgrading : httrack-3.47.26-2.fc21.i686
1/2
Error unpacking rpm package httrack-3.47.26-2.fc21.i686
error: unpacking of archive failed on file /usr/share/httrack/html:
cpio: rename
httrack-3.47.26-2.fc21.i686 was supposed to be installed but is not!
Verifying : httrack-3.47.26-2.fc21.i686
1/2
httrack-3.43.9-7.fc20.i686 was supposed to be removed but is not!
Verifying : httrack-3.43.9-7.fc20.i686
2/2
Complete!
10 years, 7 months
Concurrency Kit naming
by Michael Schwendt
https://bugzilla.redhat.com/1010613#3
Ralf Corsepius 2013-09-22 06:49:29 EDT wrote:
>
> (In reply to Michael Schwendt from comment #2)
> > The upstream name is "Concurrency Kit", so IMO the package should be named
> > "concurrencykit" or "concurrency-kit". However, the tarball and git repo
> > contain just "ck".
> Is this meant to be a provocation, Michael?
>
> > The FPC needs to clarify the naming guidelines, as else
> > it's not clear what "upstream name" they have in mind.
>
> From: https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
> "When naming a package, the name should match the upstream tarball
> or project name from which this software came."
... or _project name_ ...
And the same page uses the term "upstream name" several times. Anyway,
the FPC ticket suggesting clarification of the naming guidelines comments
on that.
> => Naming the package "ck" complies to this and you better stop wasting our time.
Follow http://fedoraproject.org/code-of-conduct
10 years, 7 months