Re: Undelivered Mail Returned to Sender

2019-02-24 Thread Michael Schwendt
On Sun, 24 Feb 2019 11:50:45 +0100, Dridi Boukelmoune wrote: > >The mail system > > > > (expanded from ): > > connect > > to mail1.ATrpms.net[160.45.254.20]:25: Connection refused > > That's unfortunate, I was hoping to discuss this this the apt-rpm > downstream

Re: Problem with portaudio linking

2019-01-04 Thread Michael Schwendt
On Fri, 4 Jan 2019 10:41:46 +0100, Michal Ruprich wrote: > Hi, > > has anyone encountered a problem on F28 when building a package that > uses portaudio? I was building newer version of wireshark a month ago > and -lportaudio worked fine. Now the build with the same version fails > with message

Re: Self Introduction: J."MUFTI" Scheurich

2018-12-12 Thread Michael Schwendt
On Mon, 10 Dec 2018 11:25:55 +0100, J. Scheurich wrote: > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Introduce_yourself > > | When a new package maintainer joins the Fedora Project, we request > that he/she introduces > | themselves on the Fedora devel >

Re: please help retire libocrdma

2018-11-06 Thread Michael Schwendt
On Tue, 6 Nov 2018 21:48:16 +0800, Honggang LI wrote: > hi, > > libocrdma had been merged into rdma-core in upstream, so libocrdma is > obsoleted by rdma-core. > > The package owner Selvin tried to retire this package, but failed > with authentication. > > We need someone who manages/maintains

Re: Unretire recordmydesktop

2018-11-04 Thread Michael Schwendt
On Sun, 4 Nov 2018 12:17:00 +, Richard W.M. Jones wrote: > recordmydesktop was retired in F27: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4RCB6MBC4JVGG4SYLIKUDOOT2REGA6N4/ > > It's claimed that it doesn't work and is full of crash bugs, but I was

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

2018-10-04 Thread Michael Schwendt
On Wed, 26 Sep 2018 09:20:30 -0600, Nathanael D. Noblet wrote: > I get what I think is a similar error with the google 'Online accounts' > > I get a certificate error. The message is: > > "No SNI provided; please fix your client." > > Would this be a related issue? Yes. If Google hands out

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

2018-09-24 Thread Michael Schwendt
On Mon, 24 Sep 2018 11:27:49 +0200, Florian Weimer wrote: > Actually, I assume Google simply made a mistake here. But this is > getting off-topic. As I've mentioned in the Fedora bugzilla ticket, pointing at the gnutls API is not a solution. libetpan upstream would appreciate a pull request.

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

2018-09-23 Thread Michael Schwendt
On Sat, 22 Sep 2018 16:32:07 -0500, mcatanzaro gnome org wrote: > You'll need to add a call to gnutls_server_name_set(), see: > > https://www.gnutls.org/manual/gnutls.html#Server-name-indication That an update for SNI may be required is clear, but it doesn't answer the question where a change

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

2018-09-22 Thread Michael Schwendt
On Wed, 18 Jul 2018 17:26:06 -0400, Ben Cotton wrote: > This change enables TLS 1.3 (draft28) support on the gnutls crypto library. > == Upgrade/compatibility impact == > That change should have no impact on upgrade or compatibility. The TLS > 1.3 protocol is designed in a way that does not

Re: Nonresponsive maintainer: Luke Macken (lmacken)

2018-08-16 Thread Michael Schwendt
On Thu, 16 Aug 2018 16:13:07 +0200, Miro Hrončok wrote: > On 16.8.2018 16:11, Dusty Mabe wrote: > > > > > > On 08/16/2018 07:29 AM, Miro Hrončok wrote: > >> Luke Macken (lmacken) is not responsive. > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1610474 > >> > >> Anyone knows how to

Re: Compilation issue after gcc removal

2018-07-19 Thread Michael Schwendt
On Fri, 20 Jul 2018 01:08:55 +0200, Marcin Zajączkowski wrote: > On 2018-07-20 00:26, Artur Iwicki wrote: > > I looked at libattr and in the changelog, there's this: > >> * Tue Jul 17 2018 Kamil Dudka 2.4.48-3 > >> - temporarily provide attr/xattr.h symlink until users are migrated > >>

audiofile package to become an orphan

2018-07-19 Thread Michael Schwendt
When I picked up the package in 2015, the upstream maintainer(s) apparently had stopped the maintenance already. Meanwhile, there have been a few CVEs and other fixes that have been ignored upstream. Recently, another CVE has been assigned to an issue, and there isn't any upstream interest either.

Notifications about "builds started to fail in Fedora rawhide"

2018-06-02 Thread Michael Schwendt
Can the service that creates these notifications be improved to include an excerpt of the problems that cause a build to fail? [...] Begin forwarded message: Date: Fri, 1 Jun 2018 23:37:57 + (UTC) From: notifications fedoraproject org Subject: claws-mail's builds started to fail in Fedora

Re: The update system has the wrong package

2018-05-29 Thread Michael Schwendt
On Tue, 29 May 2018 16:54:00 -0400, Steve Dickson wrote: > Hello, > > I'm trying to update the rpcsvc-proto package. > When I try to create a new update, the system > only gives me rpcsvc-proto-devel as a choice > not rpcsvc-proto. > > Where do I open up a ticket to get this taken > care of?

Re: greenwave is a GO on ampache_browser-1.0.0-3.20180408.fc27 for "bodhi_update_push_stable" (fedora-28)

2018-04-08 Thread Michael Schwendt
On Sun, 8 Apr 2018 13:46:55 +0200, Michael Schwendt wrote: > Please make such a message flood opt-in by default instead of opt-out. > The communication about such new services and their purpose is extremely > poor IMO. There is not even a contact address on the page! Only a cryp

Fw: fedmsg notification

2018-04-08 Thread Michael Schwendt
Please make such a message flood opt-in by default instead of opt-out. The communication about such new services and their purpose is extremely poor IMO. [...] Begin forwarded message: Date: Sat, 7 Apr 2018 23:42:01 + (UTC) From: notifications fedoraproject org Subject: fedmsg notification

Fw: greenwave is a GO on ampache_browser-1.0.0-3.20180408.fc27 for "bodhi_update_push_stable" (fedora-28)

2018-04-08 Thread Michael Schwendt
Please make such a message flood opt-in by default instead of opt-out. The communication about such new services and their purpose is extremely poor IMO. [...] Begin forwarded message: Date: Sat, 7 Apr 2018 23:59:31 + (UTC) From: notifications fedoraproject org Subject: greenwave is a GO

Re: Best way to handle sub-package conflicts

2018-03-19 Thread Michael Schwendt
On Sun, 18 Mar 2018 12:44:37 -0400, Digimer wrote: > I think "Conflict" is the way to go. However, given how much the guide > urges not to use 'Conflicts', I worry that will make it > harder/impossible later to have the package accepted into Fedora. > > Would a use-case like this be an

Re: Best way to handle sub-package conflicts

2018-03-18 Thread Michael Schwendt
On Sun, 18 Mar 2018 11:22:23 -0400, Digimer wrote: > So the .spec creates four RPMs; "anvil-core", "anvil-striker", > "anvil-node" and "anvil-dr". > > All machines require "anvil-core", plus one (and only one) of the other > three packages. There is no scenario where, for example, 'anvil-node' >

Re: Best way to handle sub-package conflicts

2018-03-18 Thread Michael Schwendt
On Sun, 18 Mar 2018 10:22:49 -0400, Digimer wrote: > Hi all, > > I am creating a new RPM package for a cluster project we've created. > There is a common "core" package, and then three other packages that are > installed depending on the machine's role in the cluster; > > foo-core > foo-A >

Re: F28 FTBFS bugs?

2018-03-15 Thread Michael Schwendt
On Thu, 15 Mar 2018 11:01:00 +0100, Daiki Ueno wrote: > Hello, > > Yesterday I received a couple of new FTBFS bugs, apparently triggered by > the F28 mass rebuild: > > https://bugzilla.redhat.com/show_bug.cgi?id=1556047 > https://bugzilla.redhat.com/show_bug.cgi?id=1556162 > > As the mentioned

librsvg2 CVEs

2018-03-13 Thread Michael Schwendt
Why are CVEs about librsvg2 not being tracked within the package? Bugzilla shows several CLOSED EOL and a few current ones not mentioned within the package %changelog. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-03-12 Thread Michael Schwendt
> The example in "man encrypt" is the culprit. It extracts the bits from > each byte upwards into the bit vector, i.e. offset 0 = bit 0 from byte 0, > offset 1 = bit 1 from byte 0, offset 2 = bit 2 from byte 0 and so on. > > If doing it as in the Claws Mail source code, the ciphertext is the same

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-03-12 Thread Michael Schwendt
On Mon, 12 Mar 2018 13:12:49 +0100, Michael Schwendt wrote: > On Fri, 9 Mar 2018 16:32:17 +0100, Florian Weimer wrote: > > > GnuTLS uses Nettle, but does not provide access to DES. You can use > > Nettle directly: > > > > https://www.lysator.liu.se

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-03-12 Thread Michael Schwendt
On Fri, 9 Mar 2018 16:32:17 +0100, Florian Weimer wrote: > GnuTLS uses Nettle, but does not provide access to DES. You can use > Nettle directly: > > https://www.lysator.liu.se/~nisse/nettle/nettle.html#DES > > OpenSSL will work as well, but as Nettle is a preexisting dependency, > it's

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-03-09 Thread Michael Schwendt
On Fri, 9 Mar 2018 16:14:39 +0100, Florian Weimer wrote: > On 01/29/2018 03:38 PM, Michael Schwendt wrote: > > The reason why I ask is that Claws Mail still uses encrypt() with the sole > > purpose of being able to decrypt old passwords. It doesn't convert them to > >

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-03-09 Thread Michael Schwendt
On Mon, 29 Jan 2018 15:38:00 +0100, Michael Schwendt wrote: > On Tue, 9 Jan 2018 18:46:06 +0100, Jan Kurik wrote: > > > = System Wide Change: Replace glibc's libcrypt with libxcrypt = > > https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt >

Re: Appstream metadata compose failures

2018-03-04 Thread Michael Schwendt
On Sat, 03 Mar 2018 19:42:48 +0100, Kevin Kofler wrote: > PS: > > I wrote: > > > Richard Hughes wrote: > >> 64x64 is a very low bar indeed, compared to all of the other > >> platforms, e.g. Windows Store or the Apple AppStore. > > > > All that's going to happen with such a requirement is

Re: Appstream metadata compose failures

2018-03-03 Thread Michael Schwendt
On Fri, 02 Mar 2018 16:11:23 +0100, Kevin Kofler wrote: > Richard Hughes wrote: > > 64x64 is a very low bar indeed, compared to all of the other > > platforms, e.g. Windows Store or the Apple AppStore. > > All that's going to happen with such a requirement is that specfiles are > going to run

Re: Please review use /$ in %files (Was: Re: Escaping macros in %changelog)

2018-02-12 Thread Michael Schwendt
On Thu, 8 Feb 2018 18:39:19 +0100, Petr Stodulka wrote: > > The following: > > %files > > /some/directory/ > > > > is equivalent to: > > %files > > %dir /some/directory > > /some/directory/* > > > > > > There's nothing wrong here. > > > > > > Exactly. IMHO, use of %dir macro for "top" pkg

Re: Please review use /$ in %files (Was: Re: Escaping macros in %changelog)

2018-02-12 Thread Michael Schwendt
On Thu, 8 Feb 2018 18:09:25 +, Tomasz Kłoczko wrote: > I'm sure that in the past it was difference here :| You are mistaken about that. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Orphaned packages seeking new point of contact

2018-02-06 Thread Michael Schwendt
On Mon, 5 Feb 2018 07:42:45 -0500, Josh Boyer wrote: > >> rpms/gqview > > > > Really?! > > Congratulations, you have just explained why absentee maintainers are > bad and why we orphan things. No. I've only shown how surprised I am to discover that it is an orphan in the Fedora package

Re: Orphaned packages seeking new point of contact

2018-02-02 Thread Michael Schwendt
On Fri, 2 Feb 2018 10:32:33 -0800, Kevin Fenzi wrote: > rpms/gqview Really?! It is unmaintained for over 10 years. It has been forked into Geeqie (package "geeqie") roughly 10 years ago, and Geeqie at least has seen several releases since then. ___

Re: F28 System Wide Change: Replace glibc's libcrypt with libxcrypt

2018-01-29 Thread Michael Schwendt
On Tue, 9 Jan 2018 18:46:06 +0100, Jan Kurik wrote: > = System Wide Change: Replace glibc's libcrypt with libxcrypt = > https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt > > Change owner(s): > * Björn Esser > * Florian Weimer > > There are plans to remove libcrypt

Re: GCC broken in rawhide?

2018-01-26 Thread Michael Schwendt
On Fri, 26 Jan 2018 14:52:24 +0100, Remi Collet wrote: > DEBUG util.py:439: Error: Transaction check error: > DEBUG util.py:439:file /usr/share/info/dir conflicts between > attempted installs of annobin-3.2-1.fc28.x86_64 and info-6.5-1.fc28.x86_64 > > Seems related to >

Re: libcdio soname bump in rawhide

2018-01-25 Thread Michael Schwendt
On Thu, 25 Jan 2018 15:24:38 +0100, Adrian Reber wrote: > /usr/include/qt5/QtGui/qstatictext.h:70:18: note: no known conversion for > argument 1 from 'QString' to 'const QStaticText&' > > Which does not seem to be libcdio related. Is this a know error > in audacious-plugins? It is due to Qt

internal compiler error: in ix86_expand_prologue, at config/i386/i386.c:14572

2018-01-25 Thread Michael Schwendt
Are recent GCC changes we need to be aware of? i686 build ends due to various internal compiler errors. The same code has built fine before a few months ago. https://koji.fedoraproject.org/koji/buildinfo?buildID=1020693 https://kojipkgs.fedoraproject.org//work/tasks/8584/24438584/build.log

Re: make yum repo when we build things in koji

2018-01-20 Thread Michael Schwendt
Maybe create a solution based on "koji download-build --help"? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: make yum repo when we build things in koji

2018-01-20 Thread Michael Schwendt
On Fri, 19 Jan 2018 22:53:30 -0500, Dusty Mabe wrote: > On 01/19/2018 10:39 PM, Reindl Harald wrote: > Thanks! > I didn't know about this, but it's not exactly what I'm looking for because > that seems > to includ everything that has been built. I'm looking more specifically for > just a repo

Re: RFC: Dropping %{?_isa} hack

2018-01-19 Thread Michael Schwendt
On Fri, 19 Jan 2018 15:32:13 +, Tomasz Kłoczko wrote: > > dnf install wine.i686 > > wine is completely brain damaged example. Maybe. Something on x86_64 is broken nevertheless. If memory serves correctly, Yum could handle it, but dnf seems to run into non-arch-specific explicit

Re: RFC: Dropping %{?_isa} hack

2018-01-18 Thread Michael Schwendt
On Thu, 18 Jan 2018 20:07:27 -0600, Rex Dieter wrote: > I can > dnf install .i686 > > and I see no 64bit packages pulled in. With F27, dnf install wine.i686 really pulls in various x86_64 alongside their i686 builds. ___ devel mailing list --

Re: Looking for contact with Daniel Veillard libxml2 maintainer

2018-01-16 Thread Michael Schwendt
On Tue, 16 Jan 2018 18:13:40 +0100, Daniel Veillard wrote: > > https://src.fedoraproject.org/rpms/libxml2/pull-requests > > Page not found (404) It loads fine here and shows five pull requests. A temporary 404 would be a Fedora infrastructure problem to report somewhere.

Re: [Bug 1529276] New: findbugs-contrib-7.2.0.sb is available

2018-01-13 Thread Michael Schwendt
On Fri, 12 Jan 2018 16:13:24 +0100, Pierre-Yves Chibon wrote: > I believe the script runs at least daily so if you see something wrong then do > report it :) Here's a recently opened ticket about package "aide": Date: Fri, 12 Jan 2018 11:17:42 +

Re: [Bug 1529276] New: findbugs-contrib-7.2.0.sb is available

2018-01-12 Thread Michael Schwendt
On Mon, 1 Jan 2018 18:24:38 +0100, Pierre-Yves Chibon wrote: > > That's due to data migration bugs from pkgdb -> pagure over dist-git > > -> bugzilla. If you're not listed as contributor on src.fedoraproject.org > > for this package, eventually that will be synced to bugzilla. > > I also

Re: [Bug 1529276] New: findbugs-contrib-7.2.0.sb is available

2017-12-31 Thread Michael Schwendt
On Wed, 27 Dec 2017 10:37:33 -0700, Jerry James wrote: > On Wed, Dec 27, 2017 at 5:16 AM, bugzilla redhat com wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=1529276 > > > > Bug ID: 1529276 > >Summary: findbugs-contrib-7.2.0.sb is available > >

Re: Proven packagers - stop messing with other people packages!!

2017-12-04 Thread Michael Schwendt
On Mon, 4 Dec 2017 15:17:32 +0100, David Kaspar [Dee'Kej] wrote: > What happened in the case that lead me to write my initial e-mail was this: > 1) Proven packager received a BZ report for his own package. > 2) Proven packager discovered the issue was actually caused by package I > maintain/own.

Re: [Heads-up] libical 3.0.0 to reach rawhide, replacing libical-glib

2017-11-16 Thread Michael Schwendt
On Tue, 14 Nov 2017 08:27:28 +0100, Milan Crha wrote: > Hi, > the sum of changes is part of the release notes, which can be found > here: > https://github.com/libical/libical/releases Would be great, if such a document were included within the package. > > vcal_manager.c: In function

Re: [Heads-up] libical 3.0.0 to reach rawhide, replacing libical-glib

2017-11-13 Thread Michael Schwendt
On Mon, 13 Nov 2017 15:04:55 +0100, Milan Crha wrote: > > The upgrade seems to be API incompatible, so more than rebuilding > > dependencies is necessary. > > Hi, > that's true. libical upstream removed some deprecated symbols, most > notably icaltimetype::is_utc. Dunno yet what's the

Re: [Heads-up] libical 3.0.0 to reach rawhide, replacing libical-glib

2017-11-13 Thread Michael Schwendt
On Wed, 01 Nov 2017 12:26:12 +0100, Milan Crha wrote: > Hello, > I'd like to give a heads up about a plan to update libical to its 3.0.0 > release in rawhide once I figure out some details about its build. This > release also obsoletes libical-glib package, the project had been added > into

Re: Trying to contact developer Axel Thimm

2017-10-26 Thread Michael Schwendt
On Thu, 26 Oct 2017 18:16:00 -0400, Stephen John Smoogen wrote: > We have been getting bounced emails from Axel Thimm for a while and I > don't have any other way to contact him. He was an early maintainer of > packages but has not been seen in fas since 2013. > If anyone has had contact with

Re: Do I need Epoch: for downgrades in rawhide?

2017-10-16 Thread Michael Schwendt
On Sun, 15 Oct 2017 18:09:12 +0200, Till Hofmann wrote: > Hi all, > > if I want to downgrade a package in rawhide only (I only pushed the > update to rawhide), do I need to add an Epoch? > > background: > I updated librealsense to librealsense2 and afterwards realized that the > new library is

Re: Incomaptible changes in new package for f27

2017-10-10 Thread Michael Schwendt
On Tue, 10 Oct 2017 13:29:19 +0200, Jiri Vanek wrote: > Hello all! > > I seek advice how to proceed with following situation. > > There is new package for f27 - java-9-openjdk. > The issue is, RPM do not like change of directory to symlink which is exactly > what happened, and > dies with

Re: Broken dependencies: audacity

2017-10-08 Thread Michael Schwendt
On Sun, 8 Oct 2017 18:34:09 +0200, Pierre-Yves Chibon wrote: > > I've not been a maintainer of the package since Fedora 13. > > > > I'm not listed as a maintainer in pkgdb, although there are three > > "Obsolete" entries that have been inherited for many years it seems. > > You are marked as

Re: Broken dependencies: audacity

2017-10-08 Thread Michael Schwendt
On Sun, 8 Oct 2017 11:58:56 + (UTC), buildsys fedoraproject org wrote: > audacity has broken dependencies in the rawhide tree: > On x86_64: > audacity-2.1.3-6.fc28.x86_64 requires libwx_baseu-3.0-gtk2.so.0()(64bit) -snip- Why do I get such an email? I've not been a maintainer of the

Re: Brave New Packaging World

2017-10-03 Thread Michael Schwendt
On Tue, 3 Oct 2017 10:40:46 -0500, Greg Hellings wrote: > So I have a new package that's gotten through review. Previously requesting > git access was handled by pkgdb. > > Where is that functionality now? Is it still there? Is there a new way to > do it under Pagure? It's a bit of a maze:

Retiring pth

2017-10-03 Thread Michael Schwendt
Nothing depends on pth anymore. Nothing BuildRequires pth-devel anymore. gnupg2 has changed to using npth. Also, there has been a strange pull request with the title ``Add CI tests using the standard test interface'' that requires extra packager commitment without touching the package:

Re: [HEADS-UP] soundtouch soname bump

2017-10-01 Thread Michael Schwendt
On Sun, 01 Oct 2017 13:54:05 +0100, Sérgio Basto wrote: > btw Io-language and ardour2 buildrequires soundtouch-devel but not use > it ... Indeed. It only uses the soundtouch library as a fallback, if fftw is not available as needed for an internal rubberband lib. For the sake of making the

Re: Rawhide SONAME change in audacious-libs package

2017-09-23 Thread Michael Schwendt
On Sat, 2 Sep 2017 20:25:25 +0200, Michael Schwendt wrote: > Anything depending on Audacious libaudcore will need a rebuild due to a > SONAME change from libaudcore.so.4 to libaudcore.so.5 that has been > introduced with the upgrade to Audacious 3.9 in Rawhide. Same for F27 wher

Re: 15 seconds to unlock screen?

2017-09-21 Thread Michael Schwendt
On Mon, 18 Sep 2017 12:36:11 +0200, Vít Ondruch wrote: > I'd say you should try to downgrade to fprintd-0.7.0-4.fc27 as a > workaround and wait for fixed selinux-policy ... Right. The fprintd test update has been published before the strictly needed selinux-policy update. Meanwhile, the latter

Rawhide SONAME change in audacious-libs package

2017-09-02 Thread Michael Schwendt
Anything depending on Audacious libaudcore will need a rebuild due to a SONAME change from libaudcore.so.4 to libaudcore.so.5 that has been introduced with the upgrade to Audacious 3.9 in Rawhide. ___ devel mailing list -- devel@lists.fedoraproject.org

Re: FAILED: BuildError: package ... not in list for tag f28-pending

2017-09-01 Thread Michael Schwendt
On Thu, 31 Aug 2017 22:14:11 +0200, Björn 'besser82' Esser wrote: > > It's been several hours since this entirely new package repo has been > > created, > > but the koji build still fails. How long does it take for koji to learn > > about this new package? > it takes as long someone from releng

FAILED: BuildError: package ... not in list for tag f28-pending

2017-08-31 Thread Michael Schwendt
It's been several hours since this entirely new package repo has been created, but the koji build still fails. How long does it take for koji to learn about this new package? $ fedpkg build Building ampache_browser-1.0.0-1.fc28 for rawhide Created task: 21592583 Task info:

Re: removable setup rpm?!

2017-08-21 Thread Michael Schwendt
On Mon, 21 Aug 2017 10:07:48 +0200, Petr Stodulka wrote: > > *ouch* Covering such a corner-case is of limited use, IMO. > > What other package tools would benefit from such a protection? > > > > It's corner case, but user is user. We could say same thing about udev, > systemd, dnf... > Why

Re: Promoting a package to stable

2017-08-18 Thread Michael Schwendt
On Fri, 18 Aug 2017 11:55:33 -0400, Matthew Miller wrote: > On Fri, Aug 18, 2017 at 11:45:40AM -0400, Irina Boverman wrote: > > I have a package in F25/F25 stable distributions that will not install > > because the dependency is no longer there (new version of libwebsockets was > > promoted to

Re: removable setup rpm?!

2017-08-18 Thread Michael Schwendt
On Fri, 18 Aug 2017 17:03:57 +0200, Petr Stodulka wrote: > >> # dnf remove setup > rpm is low level tool. No, I am talking just about use of dnf which is high > level tool for working > with packages/modules. *ouch* Covering such a corner-case is of limited use, IMO. What other package

Re: removable setup rpm?!

2017-08-18 Thread Michael Schwendt
On Fri, 18 Aug 2017 15:20:55 +0200, Petr Stodulka wrote: > >>> $ rpm -q --whatrequires setup > >>> rpcbind-0.2.4-7.rc2.fc26.x86_64 > >>> shadow-utils-4.3.1-3.fc26.x86_64 > >>> > > # dnf remove setup > > I am not talking about update, I am talking about situation that you can > break

Re: removable setup rpm?!

2017-08-18 Thread Michael Schwendt
On Fri, 18 Aug 2017 08:10:16 -0400, Neal Gompa wrote: > On Fri, Aug 18, 2017 at 7:55 AM, Michael Schwendt wrote: > > On Fri, 18 Aug 2017 13:43:28 +0200, Petr Stodulka wrote: > > > >> Hi folks, > >> > >> I found now that the setup rpm is removable from t

Re: removable setup rpm?!

2017-08-18 Thread Michael Schwendt
On Fri, 18 Aug 2017 13:43:28 +0200, Petr Stodulka wrote: > Hi folks, > > I found now that the setup rpm is removable from the system, Clarify, please. What exactly have you found out? Have you found an update case where one of the package updater tools removed it actually? $ rpm -q

Re: Need assistance to build knotter for Fedora

2017-08-18 Thread Michael Schwendt
On Thu, 17 Aug 2017 15:54:25 -0700, Luya Tshimbalanga wrote: > Following the request from Design team, I struggle to package Knotter > for review due to failure related to Qt5. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=21287726 > > As I am not familiar with Qt5. Can someone help

Re: g2clib static lib file name change

2017-08-15 Thread Michael Schwendt
On Tue, 15 Aug 2017 22:13:00 +0200, Jos de Kloe wrote: > Hi, > > I just build a new version of g2clib (upgraded from 1.4.0 to 1.6.0), and > with this change this static library for grib file handling changes name: > old: libgrib2c.a > new: libg2c_v1.6.0.a > > I dont know of a packaging

Re: koji-1.13 cannot be resolved as a dependency in f25

2017-08-12 Thread Michael Schwendt
On Sat, 12 Aug 2017 10:45:29 +0800, Chenxiong Qi wrote: > [root@e151b05870c7 pkgs]# dnf repoquery koji > Last metadata expiration check: 0:01:39 ago on Sat Aug 12 02:25:14 2017. > koji-0:1.10.1-13.fc25.noarch > koji-0:1.13.0-2.fc25.noarch > > and koji-1.13 is listed by resolving the dependencies

Re: Approved packages that never get imported?

2017-07-23 Thread Michael Schwendt
On Fri, 21 Jul 2017 18:06:58 -0500, Jason L Tibbitts III wrote: > MS> The ticket blocks FE-NEEDSPONSOR. No idea why you've approved the > MS> review officially, setting the fedora-review+ flag without being > MS> able to sponsor the new contributor. > > Because that is perfectly acceptable. It

Re: RFD Unifying graphviz.spec with upstream

2017-07-20 Thread Michael Schwendt
On Thu, 20 Jul 2017 09:36:10 -0400 (EDT), John Ellson wrote: > Specific examples please? Non-versioned Obsoletes as one example. Arch-independent explicit Requires as another example. When is the last time you've run the fedora-review tool on this src.rpm?

Re: Approved packages that never get imported?

2017-07-20 Thread Michael Schwendt
On Wed, 19 Jul 2017 14:40:41 +0100, Richard W.M. Jones wrote: > > > these packages (https://copr.fedorainfracloud.org/coprs/jonludlam/opam/) > > > about a year ago and never heard back, so... technically I guess I > > > could proceed with the non-responsive maintainer policy. But is that > > >

Re: RFD Unifying graphviz.spec with upstream

2017-07-20 Thread Michael Schwendt
On Wed, 19 Jul 2017 13:27:54 -0400 (EDT), John Ellson wrote: > Jaroslav Škarvada requested that i move the discussion from: > > https://bugzilla.redhat.com/show_bug.cgi?id=1410366 > > about unifying the graphviz .spec file with upstream, to this list. > > > Perhaps the unification

Re: some help needed with requires issue in spec file for pyproj

2017-07-06 Thread Michael Schwendt
On Thu, 6 Jul 2017 14:33:21 +0200, Jos de Kloe wrote: > Anyway, one thing still puzzles me. > You put the proj-nad and proj-epsg requires in both sub-packages now, > and clearly this works well. > However, the BuildRequires on proj-nad and proj-epsg are still in the > generic section, so does

Re: 610 emails for a branch import in dist git?

2017-07-02 Thread Michael Schwendt
On Wed, 28 Jun 2017 13:21:43 +0530, Parag Nemade wrote: > On Wed, Jun 28, 2017 at 12:29 PM, Michal Novotny wrote: > > > Can you, please, show the emails or just one of them? > > > > > >

610 emails for a branch import in dist git?

2017-06-27 Thread Michael Schwendt
Whoever set up that service, seriously? Why would I receive 610 emails for activity in "epel7"? For packages with a longer git history, it will likely be thousands of emails. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

2017-06-14 Thread Michael Schwendt
On Mon, 12 Jun 2017 22:38:11 + (UTC), till fedoraproject org wrote: > eflspot, dchen, sereinit 114 weeks ago > audacious-plugins (maintained by: mschwendt, atkac, danfruehauf) > audacious-plugins-jack-3.8.2-2.fc26.i686 requires

Re: not all that qualified...

2017-06-02 Thread Michael Schwendt
On Thu, 01 Jun 2017 02:29:53 +, Christopher wrote: > Do you have a link to an explanation of the automated fedora-review > process, and/or some of these step-by-step checklists you mention? fedora-review is a tool and a package with the same name. You simply point it at a bugzilla ticket

Re: Upgrade path w/ new compat package

2017-04-05 Thread Michael Schwendt
On Wed, 5 Apr 2017 14:18:02 +0200, Vít Ondruch wrote: > Just to make sure, I'll quote myself from my initial response: > > Dne 4.4.2017 v 08:05 Vít Ondruch napsal(a): > > Please do these changes just in Rawhide. And you think in Rawhide you are free to violate upgrade paths? Breaking

Re: Upgrade path w/ new compat package

2017-04-05 Thread Michael Schwendt
On Wed, 5 Apr 2017 13:11:56 +0200, Vít Ondruch wrote: > Is this some special process for js-jquery? No. > It is quite common that package bumps its version or soname and breaks > something. We either fix the incompatibility or provide "compat" package. > > You can take recent update of openssl

Re: Upgrade path w/ new compat package

2017-04-05 Thread Michael Schwendt
On Wed, 5 Apr 2017 10:37:30 +0200, Vít Ondruch wrote: > > https://fedoraproject.org/wiki/Package_Renaming_Process > > > > https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages > > > > because you want the new js-jquery2 package to replace the previous > >

Re: Upgrade path w/ new compat package

2017-04-04 Thread Michael Schwendt
On Tue, 4 Apr 2017 11:48:44 +0200, Vít Ondruch wrote: > It is not rename jquery is updated and introduced new jquery2 > package. There is nothing to obsolete anywhere *sigh* It is exactly this, https://fedoraproject.org/wiki/Package_Renaming_Process

Re: Reviving a stale Package Review request

2017-04-04 Thread Michael Schwendt
On Tue, 4 Apr 2017 14:48:53 +0200, Tarjei Knapstad wrote: > I would like to revive a stalled Package Review request created by > someone else, but I am unsure how to proceed. I've commented on the > request and added an updated SPEC and SRPM, but I'm not sure how to > proceed from here. Should I

Re: Upgrade path w/ new compat package

2017-04-04 Thread Michael Schwendt
On Tue, 4 Apr 2017 08:05:13 +0200, Vít Ondruch wrote: > Please do not obsolete anything. For rubygem-jquery-rails, I'd like to > use jQuery 1.x, 2.x as well as 3.x It would only be a rename. It would not stop you from adding explicit Requires to pull in all three js-jquery packages.

Re: Upgrade path w/ new compat package

2017-04-03 Thread Michael Schwendt
On Mon, 03 Apr 2017 19:35:24 +, Christopher wrote: > There seem to be a lot of possible guidance on the Wiki for what I'm trying > to do, but no clear, unambiguous step-by-step path to follow. So, I'm > seeking advice here. > > js-jquery provides jquery 2.x and js-jquery 2.x > js-jquery1

Re: Non-versioned Obsoletes tags

2017-04-03 Thread Michael Schwendt
On Mon, 03 Apr 2017 11:30:38 +0200, Igor Gnatenko wrote: > That wasn't call to change anything, I know. > I don't want to change anything, I know. > RPM behavior is not interesting because it is just evaluating constraints, > nothing else. Interesting thing is depsolving - libsolv. Maybe,

Non-versioned Obsoletes tags

2017-04-03 Thread Michael Schwendt
On Sat, 01 Apr 2017 19:54:28 +0200, Igor Gnatenko wrote: > repo system 0 testtags > #>=Pkg: foo-static 1 1 x86_64 > repo available 0 testtags > #>=Pkg: bar 1 1 x86_64 > #>=Obs: foo-static > #>=Pkg: foo-static 2 1 x86_64 > system x86_64 rpm system > poolflags implicitobsoleteusescolors >

Re: Mass issue: /usr/bin/env dependency

2017-04-01 Thread Michael Schwendt
On Sat, 1 Apr 2017 15:52:53 +0100, Tomasz Kłoczko wrote: > Please start playing with those specs files which I've posted. You have seen my reply to that faulty test case of yours, haven't you. Nothing would change. > I fully understand that it is not easy to understand some new approach if > so

Re: Mass issue: /usr/bin/env dependency

2017-04-01 Thread Michael Schwendt
On Fri, 31 Mar 2017 22:44:27 +0100, Tomasz Kłoczko wrote: > OK so it is exactly like trying to fix the C code issue with left some > parts of last changes iteration which should be fixed by deleted such > lines completely and instead such deletion someone is implementing jump > over such left

Re: Mass issue: /usr/bin/env dependency

2017-04-01 Thread Michael Schwendt
On Fri, 31 Mar 2017 21:10:29 +0100, Tomasz Kłoczko wrote: > According to those two "laws" at the moment *I think* that what it was > codified in FPG was caused by something stupid :) > Lets say .. it was something like misinterpretation when in on upgrade test > package from 2.0 to 3.0 someone

Re: Unversioned Obsoletes (was Re: Mass issue: /usr/bin/env dependency)

2017-03-31 Thread Michael Schwendt
On Fri, 31 Mar 2017 15:16:22 -0400, Fernando Nasser wrote: > A few issues I remember caused by unversioned Obsoletes (before they > were banished to Hell) were: > > - Not being able, ever again, to provide the thing being obsoleted. And > believe me, things change ;-) > > - The Obsoletes

Re: Mass issue: /usr/bin/env dependency

2017-03-31 Thread Michael Schwendt
On Fri, 31 Mar 2017 19:41:30 +0100, Tomasz Kłoczko wrote: > OK. Could you please show me example? Any non-versioned Obsoletes tag in the repo metadata hides the obsolete package from the depsolver's view during updates, and depending on the implementation even during first installs. > It is yet

Re: Mass issue: /usr/bin/env dependency

2017-03-31 Thread Michael Schwendt
On Fri, 31 Mar 2017 17:32:09 +0100, Tomasz Kłoczko wrote: > I see that you and other people proposing versioned Obsoletes rules never > ever analysed step by step whole scenario(s) or done kind of 10 min POC to > prove correctness/incorrectness of this. Looks like again .. it is result > of using

Re: Mass issue: /usr/bin/env dependency

2017-03-31 Thread Michael Schwendt
On Thu, 30 Mar 2017 19:05:54 +0100, Tomasz Kłoczko wrote: > I see more and more issues related to FPG. And most discouraging is not > what is inside FPG because I can agree with most of the advices in this > document > Seem some packagers are using it almost blindly. And we are not talking >

Re: Mass issue: /usr/bin/env dependency

2017-03-30 Thread Michael Schwendt
On Wed, 29 Mar 2017 19:26:31 +0100, Tomasz Kłoczko wrote: > On 29 March 2017 at 17:04, Michael Schwendt wrote: > > > It has been discussed several times, has met resistance and lead to > > actions like > > https://fedoraproject.org/wiki/Features/SystemPythonExecuta

Re: Mass issue: /usr/bin/env dependency

2017-03-29 Thread Michael Schwendt
On Wed, 29 Mar 2017 14:40:31 +0100, Tom Hughes wrote: > On 29/03/17 14:16, Ralf Corsepius wrote: > > On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote: > >> I would say using env in the shebang line is useful. Particularly for > >> portability. As a developer, I wouldn't like removing it from my

Re: application and header files

2017-03-15 Thread Michael Schwendt
On Tue, 14 Mar 2017 19:04:22 -0400, Randy Barlow wrote: > What do you find misleading about the review? It has discussed headers that are not installed anywhere. I expected to find a spec file that either deletes headers from the buildroot or includes them in a non-devel package to begin with.

Re: application and header files

2017-03-14 Thread Michael Schwendt
On Tue, 14 Mar 2017 17:34:16 -0400, Randy Barlow wrote: > During a package review[0], I suggested that a CLI application's header > files need to go into a -devel subpackage (they are currently not being > packaged, except for the -debuginfo subpackage.) The reviewer > disagrees, but

  1   2   3   4   5   6   7   8   9   10   >