Re: Orphaned packages to be retired (~400 during this week)
On Mon, Sep 09, 2019 at 11:49:17PM +0200, 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 package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Note: If you received this mail directly you (co)maintain one of the affected > packages or a package that depends on one. Please adopt the affected package > or > retire your depending package to avoid broken dependencies, otherwise your > package will be retired when the affected package gets retired. > > Request package ownership via releng issues: > https://pagure.io/releng/issues > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2019-09-09.txt > grep it for your FAS username and follow the dependency chain. > > Package (co)maintainers Status > Change > > libxslt orphan, veillard 0 weeks ago My package requires libxslt. My understanding is that, this changed status '0 weeks ago' which means I have ~ 6 weeks to find a solution ... other than maintaining xslt ;P Is that right? Just trying to work out how much panic to feel ;P Tony. signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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
Re: F27 System Wide Change: Golang 1.9
On Wed, Jun 21, 2017 at 10:06:17AM +0200, Jan Kurik wrote: > Along with the rebase I do propose to drop ppc64 from Go > architectures(effectively disabling build of all packages adhering to > draft Go packaging guidelines) as ppc64 port of "GC" is not feature > complete(never were) and with Go 1.9 "GC" will be supporting only > Power 8 and up. Just for clarity, you're ppc64le would remain supported. Correct? signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: FTBFS if "-Werror=format-security" flag is used
On Wed, Dec 04, 2013 at 11:56:23PM +0100, Brendan Jones wrote: > Patching is not a problem. Unnecessary is the question. Explain to > me (not you in particular Rahul) how these printf's can possibly be > exploited? Google for sudo format string exploit Yours Tony pgpit7eFTE85S.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Grepping through all Fedora specfiles?
On Wed, Jul 24, 2013 at 12:14:53PM +0200, Ralf Corsepius wrote:
> On 07/24/2013 02:33 AM, Tony Breeds wrote:
> >On Tue, Jul 23, 2013 at 10:01:51PM +0300, Ville Skyttä wrote:
> >>On 2013-07-23 08:04, Ralf Corsepius wrote:
> >>>
> >>>For similar purposes, I have been using the CSV table returned by
> >>>"https://admin.fedoraproject.org/pkgdb/lists/bugzilla?tg_format=plain";
> >>>
> >>>I am downloading the CSV-table and then use scripts to filter the CSV
> >>>into lists and subsequently to feed them into further scripts for
> >>>further processing.
> >>
> >>I've used that approach too sometime and it certainly works, but it'll
> >>take ages to clone every package from git (even though the cloning can
> >>be trivially parallelized with xargs -P or parallel).
> >
> >Sorry to be dense but if you know the package name and you only care
> >about the specfile can't you do something like:
> The problem is that you don't know the package names ;)
But you and Ville, both indictated that you're using the URL above and
post-processing it to get the names.
So can't you just combine the 2 things to do:
---
#!/bin/bash
full_clone=0
base_url='http://pkgs.fedoraproject.org'
set -ex
[ -e pkgdb_list ] || {
wget \
-c https://admin.fedoraproject.org/pkgdb/lists/bugzilla\?tg_format\=plain \
-O pkgdb_list
}
pkgs=$( awk -F\| '/\}/ {print $2}' pkgdb_list )
for pkg in $pkgs ; do
echo "Grabbing the specfile for $pkg"
(
cd ~/fedora-specs
[ -e $pkg.spec ] || {
wget -o ~/tmp/$pkg.log -O $pkg.spec \
"$base_url/cgit/${pkg}.git/plain/${pkg}.spec?id=HEAD"
}
)
[ $full_clone == 0 ] && continue
echo "Grabbing the git repo for $pkg"
(
cd ~/fedora-git
[ -d $pkg ] || {
git clone git://pkgs.fedoraproject.org/git/${pkg}.git >&1
) > ~/tmp/${pkg}-git.log &
done
---
and then wait a long time ;P
As an aside, Any guesses as to how big the ~/fedora-git dir would be
after running the script above?
Yours Tony
pgpn54nZkV_ol.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Grepping through all Fedora specfiles?
On Tue, Jul 23, 2013 at 10:01:51PM +0300, Ville Skyttä wrote:
> On 2013-07-23 08:04, Ralf Corsepius wrote:
> >
> > For similar purposes, I have been using the CSV table returned by
> > "https://admin.fedoraproject.org/pkgdb/lists/bugzilla?tg_format=plain";
> >
> > I am downloading the CSV-table and then use scripts to filter the CSV
> > into lists and subsequently to feed them into further scripts for
> > further processing.
>
> I've used that approach too sometime and it certainly works, but it'll
> take ages to clone every package from git (even though the cloning can
> be trivially parallelized with xargs -P or parallel).
Sorry to be dense but if you know the package name and you only care
about the specfile can't you do something like:
base_url='http://pkgs.fedoraproject.org'
for pkg in $pkgs ; do
wget -o $pkg.log -O $pkg.spec \
"$base_url/cgit/${pkg}.git/plain/${pkg}.spec?id=HEAD" &
done
You can even vary HEAD, to be f18,f19 to look at other releases.
It saves you the git clone, which across the whole pakage base could be
significant.
Yours Tony
pgpV2v2S4PbmD.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Call for Bikeshedding: remote auth at install time
On Mon, Jun 03, 2013 at 06:07:59PM -0700, Adam Williamson wrote: > Whether this is a blocker or not comes down to a judgement call, because > it hinges on whether this is a significant inconvenience for a large > enough number of users. So we need to know from people who use Fedora in > remote auth environments whether it's a big problem not to be able to > set it up at install / firstboot time, or whether you'd be okay with > creating a local user to get through initial-setup and then configuring > remote auth from that local account. So my personal experience with Fedora (going back to Fedora 12) in an environment with nwtwork auth is that it never worked at install time. I always eneded up createing a local account and then configuring the network auth from there. Sure I tried it when I could but when it didn't work well I just ignored it and moved on. If I'd thought it was more of an issue I would have filed bugs but it was always an "it'd be nice" not a "must have". I don't even recall seeing an option for F18, and haven't tried the F19 betas myself. Oh and black and blue stripes is the ONLY option for any bikesehd. Yours Tony pgpBczzkn0N7G.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaned meanwhile package
On Mon, Mar 25, 2013 at 09:47:57PM +0100, Simone Caronni wrote: > I'm one of those poor souls having to deal with Lotus Notes at work. > > Well, actually my soul is kidnapped in Hell and I'm forced to work with the > damn tool for repentance. Words are not enough to describe the unbearable > agony that the super fat Lotus Notes native client and the funtastic iNotes > web interface bring to my life. I started thinking we do this for charity > towards the Notes sysadmins. > > Having said that, I need Sametime, and meanwhile has a few bugs open > upstream in Empathy, one of which is the missing field to specify which > server to connect to (!!) in the account settings. > > If there's nobody else who wants to step in, I would like to be the > mantainer; any help from co-mantainers is much welcome. I'll happily co-maitain with you. I need meanwhile/pidgin but I couldn't hope to top your description of /why/ I need it :) Yours Tony pgpXBjlj4vev3.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: git push permission denied
On Tue, Nov 15, 2011 at 07:22:53PM -0500, Neal Becker wrote: > I just had to setup a new machine, and new ssh keys. > > I visited > > https://admin.fedoraproject.org/accounts/user/edit/ > > I chose my new id_rsa.pub to upload. > > But I get: > > git push --verbose > Pushing to ssh://nbec...@pkgs.fedoraproject.org/mercurial > Permission denied (publickey). > fatal: The remote end hung up unexpectedly > > Hints? I had a similar problem that didn't make sense to me but manually adding the new ssh key to my agent (even though it was already there) fixed it for me. Next time I rebooted/restarted my X session the problem was resolved. One annoying gotcha I hit after adding the new key to my agent was that many places now failed to auth as it tried each key in my agent and exceeded the MaxAuthTries in sshd I hope that helps. Yours Tony pgpI6Efaoz9Bw.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: yum-builddep (Re: Compiling 32bit on 64bit Fedora)
On Thu, Sep 08, 2011 at 10:37:10AM +0300, Panu Matilainen wrote:
> On 09/08/2011 03:44 AM, Tony Breeds wrote:
> > Hi All,
> > On a related but different note. How hard would it be to get
> > yum-builddep to take an --arch arg to that we can esily get the 32-bit
> > builddeps on a 64-bit system?
>
> It's been recently implemented at upstream, see
> https://bugzilla.redhat.com/show_bug.cgi?id=734983 for details.
>
> Note that this is only possible when feeding spec-files to yum-builddep,
> and even then it requires that spec BuildRequires are using %{_isa}
> where relevant.
Thanks I'll test it out when it hits rawhide.
Yours Tony
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: yum-builddep (Re: Compiling 32bit on 64bit Fedora)
On Thu, Sep 08, 2011 at 09:27:20AM -0400, Adam Jackson wrote: > On Thu, 2011-09-08 at 10:44 +1000, Tony Breeds wrote: > > Hi All, > > On a related but different note. How hard would it be to get > > yum-builddep to take an --arch arg to that we can esily get the 32-bit > > builddeps on a 64-bit system? > > Is 'setarch i686 yum-builddep foo' not enough? I swear when I tried that nothing sensible happend. However trying it again today it seems to do the right thing for the 1 or 2 packages I care about. Yours Tony -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
yum-builddep (Re: Compiling 32bit on 64bit Fedora)
Hi All, On a related but different note. How hard would it be to get yum-builddep to take an --arch arg to that we can esily get the 32-bit builddeps on a 64-bit system? Yours Tony -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Poorly maintained gpsbabel
On Tue, Aug 03, 2010 at 01:11:54AM +0200, Volker Fröhlich wrote: > Maybe somebody can either help me to solve the problem or can take over the > package. If gpsbabel is orphaned or if Silfreed is looking for a co-maintainer I'd be happy to help. I use gpsbabel regualrly. Yours Tony -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
