[opensuse-buildservice] Enabling (only) Opensuse UPDATE repo breaks "zypper se" command output formatting
I'm running Opensuse Leap. If I disable the zypper Opensuse update repo enabled=0 baseurl=http://download.opensuse.org/update/leap/42.1/oss/ And exec for example zypper se -s | grep letsencrypt It works | letsencrypt.sh | package | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh | srcpackage | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh-apache2 | package | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh-nginx | package | 0.1.0-4.1 | noarch | opensuse-security But if I ENable it enabled=1 baseurl=http://download.opensuse.org/update/leap/42.1/oss/ The output is now padded with tens of thousands of spaces for each line I'm not gonna paste the output here, but zypper se -s | grep letsencrypt If > DISable the repo zypper se -s | grep letsencrypt > tmp1.txt > ENable the repo zypper se -s | grep letsencrypt > tmp2.txt you can see the difference in size -- 632 bytes vs 40K bytes! -rw-r--r-- 1 root root 632 Jul 30 11:15 tmp1.txt -rw-r--r-- 1 root root 40K Jul 30 11:08 tmp2.txt This is ONLY with this specific 'update' repo. All other repos work either way, enable or disabled. It's reproducible on a bunch of different machines here. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
the 'padded' output can bee seen here http://paste.opensuse.org/aa65f0b6 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On samedi, 30 juillet 2016 11.38:09 h CEST lists@ssl-mail.com wrote:
the 'padded' output can bee seen here
Confirmed on Leap, but still work on TW. A bugreport should be created, can you open one ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sat, Jul 30, 2016, at 12:06 PM, Bruno Friedmann wrote:
On samedi, 30 juillet 2016 11.38:09 h CEST lists@ssl-mail.com wrote:
the 'padded' output can bee seen here
Confirmed on Leap, but still work on TW.
A bugreport should be created, can you open one ?
I read the bug report Andres referenced and the fix SR submitted to Factory (https://build.opensuse.org/request/show/415231) Isn't that just about a single package's problem? calibre? What I see is for any / all 'zypper se -s' attempts when the UPDATE repo is ENABLED. I guess I don't understand the fix, or if what I'm seeing is a different problem. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hello, On 07/30/2016 09:16 PM, lists@ssl-mail.com wrote:
On Sat, Jul 30, 2016, at 12:06 PM, Bruno Friedmann wrote:
On samedi, 30 juillet 2016 11.38:09 h CEST lists@ssl-mail.com wrote:
the 'padded' output can bee seen here
Confirmed on Leap, but still work on TW.
A bugreport should be created, can you open one ?
I read the bug report Andres referenced and the fix SR submitted to Factory (https://build.opensuse.org/request/show/415231)
Isn't that just about a single package's problem? calibre?
Yes, but since you did "zypper search -s | grep ...", the output of calibre will have been in the output.
What I see is for any / all 'zypper se -s' attempts when the UPDATE repo is ENABLED. I guess I don't understand the fix, or if what I'm seeing is a different problem.
The issue with your exact symtoms caused by calibre metadata is fixed in
the update repo since 21:21 CEST. Please try again.
Andreas
--
Andreas Stieger
On Sat, Jul 30, 2016, at 12:52 PM, Andreas Stieger wrote:
The issue with your exact symtoms caused by calibre metadata is fixed in the update repo since 21:21 CEST. Please try again.
Just tried zypper clean --all zypper ref zypper se -s on several machines, and both at main, and alternative repo mirrors. All of them are still "padding" output like crazy. Maybe needs some more time to propagate across the repos & mirrors? Is there any zypp(er).conf that we can do to avoid the problem this/next time? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Maybe needs some more time to propagate across the repos & mirrors?
Is there any zypp(er).conf that we can do to avoid the problem this/next time?
Took a few hours, but all sorted now. `zypper se -s *` behaves normally again. Thx. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hello, On 07/30/2016 08:28 PM, lists@ssl-mail.com wrote:
If I disable the zypper Opensuse update repo [...] But if I ENable it [...] zypper se -s | grep letsencrypt [...] you can see the difference in size -- 632 bytes vs 40K bytes!
See https://bugzilla.opensuse.org/show_bug.cgi?id=990425
Andreas
--
Andreas Stieger
Am Sa 30 Jul 2016, 11:28:25 schrieb lists@ssl-mail.com:
I'm running Opensuse Leap.
If I disable the zypper Opensuse update repo
enabled=0 baseurl=http://download.opensuse.org/update/leap/42.1/oss/
And exec for example
zypper se -s | grep letsencrypt
letsencrypt is not in update repos. And letsencrypt does no more exists. It was renamed to certbot. Search certbot and you will find last stable release in: https://build.opensuse.org/package/show?project=devel%3Alanguages%3Apython&package=certbot Regards Eric -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On dimanche, 31 juillet 2016 11.35:15 h CEST Eric Schirra wrote:
Am Sa 30 Jul 2016, 11:28:25 schrieb lists@ssl-mail.com:
I'm running Opensuse Leap.
If I disable the zypper Opensuse update repo
enabled=0 baseurl=http://download.opensuse.org/update/leap/42.1/oss/
And exec for example
zypper se -s | grep letsencrypt
letsencrypt is not in update repos.
And letsencrypt does no more exists. It was renamed to certbot.
Search certbot and you will find last stable release in:
https://build.opensuse.org/package/show?project=devel%3Alanguages%3Apython&p ackage=certbot
Regards Eric
Eric, there is a valid letsencrypt package a) letsencrypt.sh is packaged and available in security repo b) certbot is missing in devel:language:python3 (oh yeah :-) Be ready for future use ;-) https://pythonclock.org/ -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am So 31 Jul 2016, 12:17:21 schrieb Bruno Friedmann:
And exec for example
zypper se -s | grep letsencrypt
letsencrypt is not in update repos.
And letsencrypt does no more exists. It was renamed to certbot.
Search certbot and you will find last stable release in:
https://build.opensuse.org/package/show?project=devel%3Alanguages%3Apython &p ackage=certbot
Regards
Eric
Eric, there is a valid letsencrypt package
a) letsencrypt.sh is packaged and available in security repo
b) certbot is missing in devel:language:python3 (oh yeah :-) Be ready for future use ;-) https://pythonclock.org/
a) Okay i see. The package in security is not the the package itself. It's only a script to download. Right? b) No, it is not missing. certbot/letsencrypt is not compatible to python3. This is from http://letsencrypt.readthedocs.io/en/latest/using.html#system-requirements: "The Let’s Encrypt Client presently only runs on Unix-ish OSes that include Python 2.6 or 2.7; Python 3.x support will hopefully be added in the future” Regards Eric -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On dimanche, 31 juillet 2016 13.00:52 h CEST Eric Schirra wrote: > Am So 31 Jul 2016, 12:17:21 schrieb Bruno Friedmann: > > > > And exec for example > > > > > > > > zypper se -s | grep letsencrypt > > > > > > letsencrypt is not in update repos. > > > > > > And letsencrypt does no more exists. > > > It was renamed to certbot. > > > > > > Search certbot and you will find last stable release in: > > > > > > https://build.opensuse.org/package/show?project=devel%3Alanguages%3Apyth > > > on > > > &p ackage=certbot > > > > > > > > > Regards > > > > > > Eric > > > > Eric, there is a valid letsencrypt package > > > > a) letsencrypt.sh is packaged and available in security repo > > > > b) certbot is missing in devel:language:python3 (oh yeah :-) > > Be ready for future use ;-) > > https://pythonclock.org/ > > a) Okay i see. The package in security is not the the package itself. > It's only a script to download. Right? Seems to do more (Not personnally tried) * Signing of a list of domains * Signing of a CSR * Renewal if a certificate is about to expire or SAN (subdomains) changed * Certificate revocation > > b) No, it is not missing. certbot/letsencrypt is not compatible to python3. > > This is from > http://letsencrypt.readthedocs.io/en/latest/using.html#system-requirements: > > "The Let’s Encrypt Client presently only runs on Unix-ish OSes that include > Python 2.6 or 2.7; Python 3.x support will hopefully be added in the future” oh damn, such a young project starting to develop code and forget future seem wired to me ;-) > > Regards > Eric -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Andreas Stieger -
Bruno Friedmann -
Eric Schirra -
lists＠ssl-mail.com