From bogus@does.not.exist.com Fri Jul 8 19:16:09 2022 From: bogus@does.not.exist.com () Date: Fri, 08 Jul 2022 18:16:09 -0000 Subject: [Piuparts-devel] (no subject) Message-ID: List-ID : <1002106_9291006.xt.local> To: piuparts-devel at lists.alioth.debian.org Subject: Ihr Paket konnte nicht zugestellt werden. X-PHP-Originating-Script: 0:index.php Date: Fri, 8 Jul 2022 17:19:13 +0000 Reply-To: From: Deutschepost-AG Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="15e67e8df1241d06ca66b52f79b36afc2" Content-Transfer-Encoding: 8bit Received-SPF: permerror client-ip=113.30.189.146; envelope-from=pssounissadda at fuersie.de; helo=fuersie.de X-Alioth-Lists-Spam-Score-Int: 45 This is a multi-part message in MIME format. --15e67e8df1241d06ca66b52f79b36afc2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ?? ?? ?? ?? Hallo, Wirihabenifestgestellt,idassieiniPaketiniunseremiB??roizur??ckgelasseniwurde,iaberider Versand an Ihren aktuelleniStandort verursacht zus??tzlicheiVersandkosten. ?? Die Zustellung diesesiPaketsiwirdinach Informationen organisiert.Bitte ??berpr??feniSie den untenstehendeniLink und best??tigen Sie Ihre Zahlung (3,70 ), um Ihr Paket zuierhalten . ?? IhrjShopjderjdeutschepost??: ?? indem Sie auf den folgenden Link klicken??:??deutsch/nachsen/einliefern Beste Gr????e ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Deutsche Post DHL Group ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Bekijk nu je recente transacties ?? Hallo R H Kamphuis, ?? Bedankt dat je parkeert met Parkmobile! We hebben je geparkeerde minuten van afgelopen maand voor je opgeteld. Je maandoverzicht staat klaar. ?? ?? Het totaalbedrag van ??? 24,30 wordt binnen 5 dagen van je rekening afgeschreven. ?? ?? Handig Het factuurnummer:??109530506 Jouw klantnummer:??1323977 ?? ?? Bekijk factuur ?? ?? ?? Groet, Parkmobile ?? ?? ?? ?? ?? ?? Vragen? Onze??helpdesk??staat voor je klaar. Deze e-mail versturen we automatisch, je kunt er niet op antwoorden. ?? PARK NOW Group B.V. ?? Postbus 109, 1110 AC Diemen KvK: 34124818BTW: NL809206870B01 ?? ?? ?? --15e67e8df1241d06ca66b52f79b36afc2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
??
??
??
??

Hallo,

Wirihabenifestgestellt,idassieiniPaketiniunseremiB??roizur??ckgelasseniwurde,iaberider Versand an Ihren aktuelleniStandort verursacht zus??tzlicheiVersandkosten.

??

Die Zustellung diesesiPaketsiwirdinach Informationen organisiert.
Bitte ??berpr??feniSie den untenstehendeniLink und best??tigen Sie Ihre Zahlung (3,70 ), um Ihr Paket zuierhalten

.

??

IhrjShopjderjdeutschepost??:

??

indem Sie auf den folgenden Link klicken??:??deutsch/nachsen/einliefern


Beste Gr????e

??

??

??

??
??

Deutsche Post DHL Group

??

??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
Deutsche Post DHL Group
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??

Bekijk nu je recente transacties

??

Hallo R H Kamphuis,

??

Bedankt dat je parkeert met Parkmobile! We hebben je geparkeerde minuten van afgelopen maand voor je opgeteld. Je maandoverzicht staat klaar.

??
??

Het totaalbedrag van ??? 24,30 wordt binnen 5 dagen van je rekening afgeschreven.

??
??

Handig

Het factuurnummer:??109530506

Jouw klantnummer:??1323977

??
??
Bekijk factuur
??
??
??

Groet,

Parkmobile

??
??
??
??
??
??

Vragen? Onze??helpdesk??staat voor je klaar.

Deze e-mail versturen we automatisch, je kunt er niet op antwoorden.

??

PARK NOW Group B.V.

??

Postbus 109, 1110 AC Diemen

KvK: 34124818
BTW: NL809206870B01

??
??
??
--15e67e8df1241d06ca66b52f79b36afc2-- From bogus@does.not.exist.com Fri Jul 8 19:16:13 2022 From: bogus@does.not.exist.com () Date: Fri, 08 Jul 2022 18:16:13 -0000 Subject: [Piuparts-devel] (no subject) Message-ID: List-ID : <1002106_9291006.xt.local> To: piuparts-devel at alioth-lists.debian.net Subject: Ihr Paket konnte nicht zugestellt werden. X-PHP-Originating-Script: 0:index.php Date: Fri, 8 Jul 2022 17:19:13 +0000 Reply-To: From: Deutschepost-AG Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1ee12d839ed4ccf75b4e92f01e97013e2" Content-Transfer-Encoding: 8bit Received-SPF: permerror client-ip=113.30.189.146; envelope-from=pssounissadda at fuersie.de; helo=fuersie.de X-Alioth-Lists-Spam-Score-Int: 45 This is a multi-part message in MIME format. --1ee12d839ed4ccf75b4e92f01e97013e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ?? ?? ?? ?? Hallo, Wirihabenifestgestellt,idassieiniPaketiniunseremiB??roizur??ckgelasseniwurde,iaberider Versand an Ihren aktuelleniStandort verursacht zus??tzlicheiVersandkosten. ?? Die Zustellung diesesiPaketsiwirdinach Informationen organisiert.Bitte ??berpr??feniSie den untenstehendeniLink und best??tigen Sie Ihre Zahlung (3,70 ), um Ihr Paket zuierhalten . ?? IhrjShopjderjdeutschepost??: ?? indem Sie auf den folgenden Link klicken??:??deutsch/nachsen/einliefern Beste Gr????e ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Deutsche Post DHL Group ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Bekijk nu je recente transacties ?? Hallo R H Kamphuis, ?? Bedankt dat je parkeert met Parkmobile! We hebben je geparkeerde minuten van afgelopen maand voor je opgeteld. Je maandoverzicht staat klaar. ?? ?? Het totaalbedrag van ??? 24,30 wordt binnen 5 dagen van je rekening afgeschreven. ?? ?? Handig Het factuurnummer:??109530506 Jouw klantnummer:??1323977 ?? ?? Bekijk factuur ?? ?? ?? Groet, Parkmobile ?? ?? ?? ?? ?? ?? Vragen? Onze??helpdesk??staat voor je klaar. Deze e-mail versturen we automatisch, je kunt er niet op antwoorden. ?? PARK NOW Group B.V. ?? Postbus 109, 1110 AC Diemen KvK: 34124818BTW: NL809206870B01 ?? ?? ?? --1ee12d839ed4ccf75b4e92f01e97013e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
??
??
??
??

Hallo,

Wirihabenifestgestellt,idassieiniPaketiniunseremiB??roizur??ckgelasseniwurde,iaberider Versand an Ihren aktuelleniStandort verursacht zus??tzlicheiVersandkosten.

??

Die Zustellung diesesiPaketsiwirdinach Informationen organisiert.
Bitte ??berpr??feniSie den untenstehendeniLink und best??tigen Sie Ihre Zahlung (3,70 ), um Ihr Paket zuierhalten

.

??

IhrjShopjderjdeutschepost??:

??

indem Sie auf den folgenden Link klicken??:??deutsch/nachsen/einliefern


Beste Gr????e

??

??

??

??
??

Deutsche Post DHL Group

??

??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
Deutsche Post DHL Group
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??
??

Bekijk nu je recente transacties

??

Hallo R H Kamphuis,

??

Bedankt dat je parkeert met Parkmobile! We hebben je geparkeerde minuten van afgelopen maand voor je opgeteld. Je maandoverzicht staat klaar.

??
??

Het totaalbedrag van ??? 24,30 wordt binnen 5 dagen van je rekening afgeschreven.

??
??

Handig

Het factuurnummer:??109530506

Jouw klantnummer:??1323977

??
??
Bekijk factuur
??
??
??

Groet,

Parkmobile

??
??
??
??
??
??

Vragen? Onze??helpdesk??staat voor je klaar.

Deze e-mail versturen we automatisch, je kunt er niet op antwoorden.

??

PARK NOW Group B.V.

??

Postbus 109, 1110 AC Diemen

KvK: 34124818
BTW: NL809206870B01

??
??
??
--1ee12d839ed4ccf75b4e92f01e97013e2-- From ckglobalnet at ckglobalnet.com Fri Jul 8 05:09:25 2022 From: ckglobalnet at ckglobalnet.com (Uwe Wanner) Date: Thu, 07 Jul 2022 21:09:25 -0700 Subject: [Piuparts-devel] Info. 7, July 2022. Message-ID: Hello, We have no intention of wasting your time. We give out loans to individuals and companies. The interest rate will be 2% annually. We have capacity to finance projects in these fields; real estate development, construction, mining, oil and gas, airline and various trading. If interested, Please provide the following: 1- Full name: 2- Loan amount required: 3- Payback Duration (1 13 30 Years): 4- Phone Number / Whatsapp Number: I will send you the loan terms and condition once I receive the above information . Your refund plan starts after 6 months (6 months grace period). Funding will take approximately 7 banking days from the day you present your loan application. Reply us for more information. Yours truly Uwe Wanner -------------- next part -------------- An HTML attachment was scrubbed... URL: From al.muharraqgrp at gmail.com Tue Jul 12 11:04:00 2022 From: al.muharraqgrp at gmail.com (Al muharraq group) Date: Tue, 12 Jul 2022 11:04:00 +0100 Subject: [Piuparts-devel] Al-Muharraq Project funding Message-ID: -- Greetings from Al-Muharraq Group Ltd. I have contacted you to consult you for a funding resolution for your business. My Name is Saif Yusuf. Do you have projects that require funding? We facilitate the funding needs of private project owners around the world covering infrastructure, housing, real estate development, IT parks, industrial parks, film studios, food parks, agricultural projects, health & wellness, hospitality, education, electronics & telecommunication, power & electricity and oil and gas sectors. If you have any queries regarding funding please revert back to me and find the solution to your financial needs. Sincerely, Saif Yusuf Business Consultant Al-MUHARRAQ Group. #sblcproviders #bankguarantee #mortgageloans #unsecuredloan #projectfinance #startuploan #tradefund From no-reply at wix-domains.com Wed Jul 13 09:04:51 2022 From: no-reply at wix-domains.com (no-reply at wix-domains.com) Date: Wed, 13 Jul 2022 08:04:51 +0000 (UTC) Subject: [Piuparts-devel] Your attempt to contact a Wix domain owner Message-ID: <0JtrheRARQustI3EdYnLyw@geopod-ismtpd-1-6>

You've attempted to contact the owner of a domain name registered through Wix.com

To contact the domain owner, send a message using To report abuse, click  

Subject to the terms of our  

This email was sent to you from an address that does not accept incoming email.  Please do not reply to this message.

-------------- next part -------------- An HTML attachment was scrubbed... URL: From gitlab at salsa.debian.org Wed Jul 13 19:10:03 2022 From: gitlab at salsa.debian.org (Nicolas Dandrimont (@olasd)) Date: Wed, 13 Jul 2022 18:10:03 +0000 Subject: [Piuparts-devel] [Git][debian/piuparts][develop] 4 commits: piuparts: detect files moving between / and /usr on upgrade Message-ID: <62cf0a7b757f_3db40fec9682f3@godard.mail> Nicolas Dandrimont pushed to branch develop at Debian / piuparts Commits: e7538053 by Luca Boccassi at 2022-07-13T10:36:42+01:00 piuparts: detect files moving between / and /usr on upgrade The TC issued a recommendation to avoid moving files between bin|sbin|lib* and /usr/bin|sbin|lib* for the Bookworm cycle. Detect such moves and raise an error. For more details see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#80 - - - - - 4489752a by Luca Boccassi at 2022-07-13T10:36:42+01:00 piuparts: detect files moving between / and /usr on dist-upgrade Same as the check on package install/upgrade, but across distribution dist-upgrades. - - - - - 59c00b8b by Luca Boccassi at 2022-07-13T10:36:42+01:00 p.conf: enable --warn-on-usr-move for bullseye/bookworm - - - - - 92c1faff by Nicolas Dandrimont at 2022-07-13T20:06:49+02:00 Merge branch 'usrmerge' into develop piuparts: detect files moving between / and /usr on upgrade See merge request https://salsa.debian.org/debian/piuparts/-/merge_requests/37 - - - - - 6 changed files: - docs/piuparts/piuparts.1.txt - instances/piuparts.conf-template.pejacevic - + known_problems/file_moved_usr_error.conf - + known_problems/file_moved_usr_issue.conf - piuparts-report.py - piuparts.py Changes: ===================================== docs/piuparts/piuparts.1.txt ===================================== @@ -330,6 +330,10 @@ Options must come before the other command line arguments. Behavior with multiple packages given on the command-line could be problematic, particularly if the dependency tree of one package in the list includes another in the list. Therefore, it is recommended to use this option with one package at a time. +*-*-warn-on-usr-move*='disabled|warn|fail':: + Whether to enable the test (with a warning or a failure) that checks if files are moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}. + Accepted values: 'disabled' (default), 'warn', 'fail'. + EXAMPLES ===================================== instances/piuparts.conf-template.pejacevic ===================================== @@ -40,15 +40,18 @@ flags-end-oldstable = %(flags-end-buster)s # common flags for tests starting in bookworm flags-start-bookworm = -# no flags needed +# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#80 + --warn-on-usr-move fail # common flags for tests ending in bookworm flags-end-bookworm = -# no flags needed +# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#80 + --warn-on-usr-move fail # common flags for tests starting in bullseye flags-start-bullseye = -# no flags needed +# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#80 + --warn-on-usr-move fail # common flags for tests ending in bullseye flags-end-bullseye = ===================================== known_problems/file_moved_usr_error.conf ===================================== @@ -0,0 +1,13 @@ +# detect a file moving between bin/sbin/lib* and usr/bin|sbin|lib* +# +PATTERN='(WARN|FAIL): File\(s\) moved between /.* and /usr/.*:' +WHERE='fail bugged affected' +ISSUE=0 +HEADER='File(s) moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}' +HELPTEXT=' +

+The Technical Committee recommended against moving files between between /{bin|sbin|lib*} +and /usr/{bin|sbin|lib*} during the Bookworm development cycle. See +Debian bug #994388. +

+' ===================================== known_problems/file_moved_usr_issue.conf ===================================== @@ -0,0 +1,13 @@ +# detect a file moving between bin/sbin/lib* and usr/bin|sbin|lib* +# +PATTERN='(WARN|FAIL): File\(s\) moved between /.* and /usr/.*:' +WHERE='pass' +ISSUE=1 +HEADER='File(s) moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}' +HELPTEXT=' +

+The Technical Committee recommended against moving files between between /{bin|sbin|lib*} +and /usr/{bin|sbin|lib*} during the Bookworm development cycle. See +Debian bug #994388. +

+' ===================================== piuparts-report.py ===================================== @@ -501,6 +501,8 @@ linktarget_by_template = [ ("missing_md5sums_error.tpl", "...and logfile reports missing md5sums"), ("unowned_lib_symlink_error.tpl", "...and logfile reports unowned lib symlinks"), ("piuparts-depends-dummy_error.tpl", "...and logfile reports piuparts-depends-dummy.deb could not be installed"), + ("file_moved_usr_error,tpl", "...and logfile reports a file moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}"), + ("file_moved_usr_issue,tpl", "but logfile reports a file moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}"), ("unclassified_failures.tpl", "due to unclassified failures"), ] ===================================== piuparts.py ===================================== @@ -53,6 +53,7 @@ import traceback import uuid import apt_pkg import pipes +import pathlib from collections import namedtuple from signal import alarm, signal, SIGALRM, SIGTERM, SIGKILL @@ -220,6 +221,7 @@ class Settings: self.warn_on_debsums_errors = False self.warn_on_install_over_symlink = False self.warn_if_inadequate = True + self.warn_on_usr_move = "disabled" self.pedantic_purge_test = False self.ignored_files = [ # /root/.rnd should *not* be listed here, see #750099 @@ -1833,6 +1835,45 @@ class Chroot: return True return False + def check_files_moved_usr(self, packages=[], files_before={}, files_after={}, warn_only=None): + """Check that no files were moved from /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}""" + + if settings.warn_on_usr_move == "disabled": + return + + # For each path that is a file in each package, check that it did not move between + # /bin, /sbin or /lib* to the corresponding location under /usr, and viceversa. + # See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#80 + # If a file moved in a package that we are inspecting, print an error by default. + # Otherwise, print a warning. + broken = [] + for old_path in files_before: + # '/' is a separate element in the parts list + old_path_parts = pathlib.Path(old_path).parts + if len(old_path_parts) < 3: + continue + + if old_path_parts[1] == 'usr' and (old_path_parts[2] in ['bin', 'sbin'] or old_path_parts[2].startswith('lib')): + new_path = os.path.join("/", *old_path_parts[2:]) + elif old_path_parts[1] in ['bin', 'sbin'] or old_path_parts[1].startswith('lib'): + new_path = "/usr" + old_path + else: + continue + + # Skip over directories, multiple packages can ship files in the same directories + if new_path in files_after and os.path.isfile(self.relative(new_path)): + broken.append("%s %s => %s %s" % (old_path, files_before[old_path], new_path, files_after[new_path])) + + if broken: + if settings.warn_on_usr_move == "warn" or warn_only: + logging.warning("WARN: File(s) moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}: %s" % indent_string("\n".join(broken))) + else: + logging.error("FAIL: File(s) moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}: %s" % indent_string("\n".join(broken))) + panic() + else: + logging.debug("No file moved between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}.") + + def check_for_broken_symlinks(self, warn_only=None, file_owners={}): """Check that all symlinks in chroot are non-broken.""" if not settings.check_broken_symlinks: @@ -2456,6 +2497,9 @@ def install_upgrade_test(chroot, chroot_state, package_files, packages, old_pack chroot.check_for_no_processes() chroot.check_for_broken_symlinks() + if settings.warn_on_usr_move != "disabled": + file_owners_before = chroot.get_files_owned_by_packages() + if settings.install_remove_install: chroot.remove_packages(packages, ignore_errors=True) @@ -2468,10 +2512,12 @@ def install_upgrade_test(chroot, chroot_state, package_files, packages, old_pack chroot.disable_testdebs_repo() - file_owners = chroot.get_files_owned_by_packages() + file_owners_after = chroot.get_files_owned_by_packages() chroot.check_for_no_processes() - chroot.check_for_broken_symlinks(file_owners=file_owners) + chroot.check_for_broken_symlinks(file_owners=file_owners_after) + if settings.warn_on_usr_move != "disabled": + chroot.check_files_moved_usr(packages, file_owners_before, file_owners_after) # Remove all packages from the chroot that weren't there initially. chroot.restore_selections(chroot_state, packages) @@ -2479,9 +2525,9 @@ def install_upgrade_test(chroot, chroot_state, package_files, packages, old_pack chroot.run_scripts("post_test") chroot.check_for_no_processes(fail=True) - chroot.check_for_broken_symlinks(file_owners=file_owners) + chroot.check_for_broken_symlinks(file_owners=file_owners_after) - return check_results(chroot, chroot_state, file_owners) + return check_results(chroot, chroot_state, file_owners_after) def save_meta_data(filename, chroot_state): @@ -2610,6 +2656,9 @@ def install_and_upgrade_between_distros(package_files, packages_qualified): chroot.check_for_no_processes() + if settings.warn_on_usr_move != "disabled": + file_owners_before = chroot.get_files_owned_by_packages() + os.environ["PIUPARTS_PHASE"] = "distupgrade" chroot.upgrade_to_distros(settings.debian_distros[1:-1], distupgrade_packages, settings.upgrade_before_dist_upgrade) @@ -2634,6 +2683,10 @@ def install_and_upgrade_between_distros(package_files, packages_qualified): chroot.check_for_no_processes() + if settings.warn_on_usr_move != "disabled": + file_owners_after = chroot.get_files_owned_by_packages() + chroot.check_files_moved_usr(packages, files_before=file_owners_before, files_after=file_owners_after) + # Remove all packages from the chroot that weren't in the reference chroot. chroot.restore_selections(chroot_state, packages_qualified) @@ -3008,6 +3061,10 @@ def parse_command_line(): default=False, help="Fail if broken symlinks are detected.") + parser.add_option("--warn-on-usr-move", action="store", default="disabled", + help="Whether to enable the test (with a warning or a failure) that checks if files are moved " + "between /{bin|sbin|lib*} and /usr/{bin|sbin|lib*}. Accepted values: 'disabled' (default), 'warn', 'fail'.") + parser.add_option("--log-level", action="store", metavar='LEVEL', default="dump", help="Displays messages from LEVEL level, possible values are: error, info, dump, debug. The default is dump.") @@ -3103,6 +3160,7 @@ def parse_command_line(): settings.warn_on_debsums_errors = opts.warn_on_debsums_errors settings.warn_on_install_over_symlink = opts.warn_on_install_over_symlink settings.warn_if_inadequate = not opts.fail_if_inadequate + settings.warn_on_usr_move = opts.warn_on_usr_move settings.pedantic_purge_test = opts.pedantic_purge_test settings.ignored_files += opts.ignore settings.ignored_patterns += opts.ignore_regex @@ -3138,6 +3196,10 @@ def parse_command_line(): logging.error("Scripts directory is not a directory: %s" % sdir) panic() + if settings.warn_on_usr_move not in ["disabled", "warn", "fail"]: + logging.error("--warn-on-usr-move must be one of 'disabled', 'warn', 'fail'") + panic() + if not settings.debian_distros: settings.debian_distros = defaults.get_distribution() View it on GitLab: https://salsa.debian.org/debian/piuparts/-/compare/190399be209337dec2c67215368b0cb0343ed09d...92c1faff5d44c9ca06cb9dbd5a299378f0d4b9a7 -- View it on GitLab: https://salsa.debian.org/debian/piuparts/-/compare/190399be209337dec2c67215368b0cb0343ed09d...92c1faff5d44c9ca06cb9dbd5a299378f0d4b9a7 You're receiving this email because of your account on salsa.debian.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ana.rocha at ssp.df.gov.br Sat Jul 16 11:55:21 2022 From: ana.rocha at ssp.df.gov.br ( Mr Kim Cheng) Date: Sat, 16 Jul 2022 03:55:21 -0700 Subject: [Piuparts-devel] Hello Message-ID: <20220716105608.ADA3AB830F9@zmail.ssp.df.gov.br> I have been trying to reach you, please do get back to me. Thanks Mr Kim Cheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From gitlab at salsa.debian.org Sun Jul 17 21:07:21 2022 From: gitlab at salsa.debian.org (Nicolas Dandrimont (@olasd)) Date: Sun, 17 Jul 2022 20:07:21 +0000 Subject: [Piuparts-devel] [Git][debian/piuparts][develop] 2 commits: custom_scripts: ensure usr-is-merged/usrmerge does not fail the migration test Message-ID: <62d46bf948a48_3db7549ba4194948e@godard.mail> Nicolas Dandrimont pushed to branch develop at Debian / piuparts Commits: 98b4fdcd by Luca Boccassi at 2022-07-17T20:17:08+01:00 custom_scripts: ensure usr-is-merged/usrmerge does not fail the migration test The new usr-is-merged metapackage intentionally fails to install on systems that are not merged-usr, unless a specific override flag is passed. usrmerge does a live-upgrade of the chroot, which piuparts does not expect. Use the skip flag, so that migration is not blocked. Debootstrap will start using this flag once the package is available in testing. For details see: https://sources.debian.org/src/usrmerge/27/debian/README.Debian/#L66 and: https://lists.debian.org/debian-ctte/2022/07/msg00019.html - - - - - c3352499 by Nicolas Dandrimont at 2022-07-17T22:06:03+02:00 Merge branch 'usr-is-merged' into 'develop' custom_scripts: ensure usr-is-merged does not fail the migration test See merge request https://salsa.debian.org/debian/piuparts/-/merge_requests/38 - - - - - 2 changed files: - custom-scripts/scripts/post_purge_exceptions - custom-scripts/scripts/pre_install_exceptions Changes: ===================================== custom-scripts/scripts/post_purge_exceptions ===================================== @@ -53,6 +53,13 @@ case ${PIUPARTS_OBJECTS%%=*} in log_debug sleep 10 ;; + *usr-is-merged*|*usrmerge*) + # Remove the exception flag that we added in pre_install_exceptions, if we added it + if [ -f /etc/unsupported-skip-usrmerge-conversion.piuparts ]; then + log_debug + rm -f /etc/unsupported-skip-usrmerge-conversion* + fi + ;; esac if [ -f /var/run/piuparts-stamp-dkms-installed ]; then ===================================== custom-scripts/scripts/pre_install_exceptions ===================================== @@ -106,6 +106,20 @@ case ${PIUPARTS_OBJECTS%%=*} in mkdir -p /var/state/samhain/ touch /var/state/samhain/samhain_file ;; + *usr-is-merged*|*usrmerge*) + # usr-is-merged intentionally fails to install unless either the system is merged-usr, or + # the exception flag is set. + # usrmerge does a live-upgrade of the chroot, which piuparts does not expect, so skip it. + # debootstrap will take care of this in a future update, so remember if we were the ones + # that added the flag file, to remove it in the post_purge_exceptions script. + # For details on the flag file, see: https://sources.debian.org/src/usrmerge/27/debian/README.Debian/#L66 + # and: https://lists.debian.org/debian-ctte/2022/07/msg00019.html + if [ ! -f /etc/unsupported-skip-usrmerge-conversion ]; then + log_debug + touch /etc/unsupported-skip-usrmerge-conversion.piuparts + echo "this system will not be supported in the future" > /etc/unsupported-skip-usrmerge-conversion + fi + ;; esac if [ "$PIUPARTS_DISTRIBUTION" = "jessie" ]; then View it on GitLab: https://salsa.debian.org/debian/piuparts/-/compare/92c1faff5d44c9ca06cb9dbd5a299378f0d4b9a7...c33524996dfa1226b769089b4c884233dc76e10c -- View it on GitLab: https://salsa.debian.org/debian/piuparts/-/compare/92c1faff5d44c9ca06cb9dbd5a299378f0d4b9a7...c33524996dfa1226b769089b4c884233dc76e10c You're receiving this email because of your account on salsa.debian.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guilhem at debian.org Tue Jul 19 22:42:47 2022 From: guilhem at debian.org (Guilhem Moulin) Date: Tue, 19 Jul 2022 23:42:47 +0200 Subject: [Piuparts-devel] Bug#1015732: piuparts: scripts/pre_install_database-server doesn't work when piuparts is fed a .changes or .deb Message-ID: Package: piuparts Version: 1.1.5 Severity: normal File: /etc/piuparts/scripts/pre_install_database-server Tags: patch Dear Maintainer, Piuparts scripts in /etc/piuparts/scripts/* case match over ${PIUPARTS_OBJECTS%%=*}, which works on piuparts.d.o (which calls piuparts with `--apt ${PKGNAME}=${VERSION}`) but not on salsa ci (since it calls piuparts with `/path/to/${PKGNAME}_${VERSION}_${ARCH}.deb`). I think the script also doesn't work when a .change or when multiple packages are supplied. I attach a PoC patch which fixes the problem for me, but I believe other scripts are affected as well. I can submit a file for other scripts too but but I'm unsure the proposed the logic is the way to go. Thanks for maintaining piuparts! -- Guilhem. -------------- next part -------------- A non-text attachment was scrubbed... Name: pre_install_database-server.patch Type: text/x-diff Size: 14834 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From mike at tbitmail.com Wed Jul 27 21:42:53 2022 From: mike at tbitmail.com (Manuel Franco) Date: Wed, 27 Jul 2022 20:42:53 +0000 Subject: [Piuparts-devel] Haben sie noch Interesse?. Message-ID: <20220727204257.1083127079DB@ex01.tbitmail.com> IHR E-MAIL-KONTO HAT EINE SPENDE VON $2.800.000,00 GEWONNEN. KONTAKTIEREN SIE UNS F?R MEHR DIE INFORMATION