Bug 1217305 - perl(Domain::PubicSuffix) is not available in a repository
Summary: perl(Domain::PubicSuffix) is not available in a repository
Status: RESOLVED FIXED
: 1217497 (view as bug list)
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Andreas Stieger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-18 17:26 UTC by Freek de Kruijf
Modified: 2023-11-26 08:29 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2023-11-18 17:26:50 UTC
I am trying to use opendmarc from project/repository server-mail but got the message:
Problem: nothing provides 'perl(Domain::PublicSuffix)' needed by the to be installed opendmarc....
I did install it using cpan and ignored the error message from zypper, but it is not ideal.
Comment 1 OBSbugzilla Bot 2023-11-18 19:35:03 UTC
This is an autogenerated message for OBS integration:
This bug (1217305) was mentioned in
https://build.opensuse.org/request/show/1127455 Factory / perl-Domain-PublicSuffix
Comment 2 Dirk Stoecker 2023-11-18 20:51:50 UTC
I approved of submission of Domain::PublicSuffix to Tumbleweed. Note that opendmarc isn't really maintained upstream.

Anyway I still use it myself, but there's a backlog of issues and tickets which nobody cares for. The openSUSE package has some of the patches applied, but there are lots more.

I recently added perl Mail::DMARC packages to devel:languages:perl, but I hadn't yet the time to check whether situation is better for this system of DMARC handling.

Feedback welcome.
Comment 3 Andreas Stieger 2023-11-19 06:24:00 UTC
should be in an upcoming snapshot
Comment 4 Andreas Stieger 2023-11-26 08:29:47 UTC
*** Bug 1217497 has been marked as a duplicate of this bug. ***