RE: cups-2.4.2-11.fc39.src.rpm depends on autoconf-2.71 or newer, not mentioned in .spec file, fails build

[Douglas Kosovic]

On Wed, Jun 28, 2023 7:15AM +1000, Jan Pazdziora wrote:
> On Sun, Mar 26, 2023 at 02:44:34PM +0300, ijaaskelai...@outlook.com wrote:
> > Kind regards, The Improvement Skeleton.
> 
> Please show the exact steps you use to build the cups package and the
> exact error message you get.
> 
> Technically you are correct because configure.ac has AC_PREREQ([2.71]).
> But autoconf is pulled in by the automake which is listed as BuildRequires
> in cups.spec file, and since Fedora rawhide only has
> autoconf-2.71-5.fc38.noarch, there really is not an older autoconf around
> to ruin your day.

I suspect he may be trying to rebuild the Fedora CUPS RPMs on a RHEL 8 or 9 
based machine.

Ironically CUPS 2.4.x doesn't actually need autoconf to be at least 2.71, on 
openSUSE they have a downgrade-autoconf-requirement.patch file which downgrades 
the requirement to 2.69:

https://build.opensuse.org/package/show/openSUSE%3AFactory/cups


Cheers,
Doug

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: PWG+OpenPrinting meetup 2023

[Douglas Kosovic]

Hi Zdenek,

Regarding packaging pappl-retrofit and printer applications, looking at the 
pappl-retrofit based snaps from Till Kamppeter, I suspect the existing Fedora 
pappl package might need to be modified.

For example, extract from ps-printer-app's snapcraft.yaml file which modifies 
pappl's default build settings:

https://github.com/OpenPrinting/ps-printer-app/blob/master/snap/snapcraft.yaml


  pappl:
...
override-build: |
  set -eux
  # Raise the supported number of vendor-specific options/attributes in
  # PAPPL to 256, as the original 32 can be too small for some busy PPD
  # files
  perl -p -i -e 's/(define\s+PAPPL_MAX_VENDOR\s+)32/\1 256/' pappl/printer.h
  # De-activate log-rotating. It does not work with the forked processes
  # of the filters
  perl -p -i -e 's/(system->logmaxsize\s+=).*/\1 0;/' pappl/system.c
  # As we do not use PAPPL's own backends but the CUPS backends using the
  # "cups" device scheme of pappl-retrofit, we let the manual "Network
  # Printer" device on the "Add Printer" page of the web interface use a
  # "cups:socket://..." URI instead of simply "socket://..."
  perl -p -i -e 
's/(httpAssembleURI\(.*?)"socket"(.*?\))/\1"cups:socket"\2/' 
pappl/system-webif.c
  # PAPPL's build system does not insert the LDFLAGS when linking.
  # Patching Makedefs.in to fix this
  perl -p -i -e 's/^(\s*DSOFLAGS\s*=\s*\S*\s+)/\1\$\(LDFLAGS\) /' 
Makedefs.in



Cheers,
Doug

-Original Message-
From: Zdenek Dohnal  
Sent: Thursday, May 18, 2023 4:26 AM
To: Development discussions related to Fedora 
Subject: PWG+OpenPrinting meetup 2023

Hi all,

I've joined annual PWG+OpenPrinting virtual meetup where the news and statuses 
from the current printing development are discussed.

The main points are:

- cups-filters 2.0 betas and release candidates are released and present in 
Fedora 38

- since new cups-filters are in Fedora 38, nothing stands in the way of 
packaging pappl-retrofit and printer applications based on it into Fedora as 
RPMs - any volunteers are welcome!

- CUPS 2.4.x, CUPS 2.5 and CUPS 3.0 are delayed:

     - 2.4.x - there are several regressions I haven't able to tackle yet, but 
I hope there is a new version in a month

     - 2.5 - OAuth support took lot of time to implement

     - 3.0 - libcups (its version 3.0) has a beta which developers which uses 
libcups 2.0 can compile and link their applications and see what changed 
between major release

- GTK (its version 4) has merged support for Common Print Dialog Backends - 
universal print dialog, which can work not only with cups, but with other 
possible backends (like google cloud print)

- WIP on Printer Setup Tool for GNOME Control Center - full support for 
driverless printers and printers via printer applications


The full report is attached.


Zdenek

-- 
Zdenek Dohnal
Software Engineer
Red Hat, BRQ-TPBC
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Inactive packagers to be removed after the F37 release

[Douglas Kosovic]

On Sun, Sep 4, 2022 at 1:38 PM Mattia Verga wrote:
> If anyone wants to have a look to what packages **may** be orphaned 
> when those users are removed from the packager group, I've set up a 
> script and uploaded the results here [1].
>
> Do not be too scared by those results: there's still plenty of time for
> those users to show up and declare their willingness to maintain their
> status. If you, however, see a package you care listed with an asterisk
> (look at the bottom of the list), take notice that these are the
> packages that will surely be orphaned, because the current
> maintainer has asked to be removed from the packager group.
> Maybe you can start asking them to transfer the package to you.
> 
> I plan to post an updated list before the end of the month and at
>  mid October (or maybe Ben will do, if he prefer).
> 
> [1] https://mattia.fedorapeople.org/inactive-packagers/affected_packages.txt

Regarding the following package from that list :
- NetworkManager-l2tp (owned by ivanromanov)

I've been maintaining the package (and upstream source) since 2016, but I'm not 
the 'owner" or "main admin", just a member/admin.

What's the best way to become owner of the NetworkManager-l2tp package?



Thanks,
Doug

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: urw-fonts: Versioning Mess

[Douglas Kosovic]

On 30/11/2016, 9:38 PM, "Dominik 'Rathann' Mierzejewski" 
 wrote:

> 2) or map the X.Y.Z versioning to MMDD from upstream - IOW - X == 
Year,
> Y == Month, Z == Day (based on the snapshot date in the name of the source
> archive)
> 3) or set the Version to some constant (35 for example) and just use the
> snapshot to distinguish between older and newer releases.

What does the number "35" mean here, anyway?

Each PostScript specification defines a core set of fonts:
- PostScript 1 has 13 base fonts.
- PostScript 2 has 35 base fonts.
- PostScript 3 has 135 base fonts.

So, the URW++ base35 font pack is a replacement for the 35 Adobe PostScript 
Level 2 base fonts.



Doug



 

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org