Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue
Hello Michael, The package/version format is still wrong. Could you fix this in the next SRU? Regards, Arnold Czeman From: Arnold Czeman (aczeman) Sent: Monday, September 7, 2020 2:46 PM To: Michael Hudson-Doyle Cc: ubuntu-devel-discuss@lists.ubuntu.com Subject: Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue Hello Michael, The next SRU would be good. Thank you. Cheers, Arnold Czeman From: Michael Hudson-Doyle Sent: Monday, September 7, 2020 12:51 PM To: Arnold Czeman (aczeman) Cc: ubuntu-devel-discuss@lists.ubuntu.com Subject: Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe. On Sat, 5 Sep 2020 at 06:39, Arnold Czeman (aczeman) mailto:arnold.cze...@oneidentity.com>> wrote: Hello, I have a little problem with the newest version of pam source package on Bionic. https://bugs.launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2/<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fpam%2F1.1.8-3.6ubuntu2.18.04.2%2F=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237917170=TO5%2FcquslSMlK94UrM%2FIorsBLxQQUiSpSR2021FQimM%3D=0> I would like to import to a git repo with gbp tool, but this package seems to have a wrong a package format. The earlier version of this package were non-native debian packages, they had extra archives which name match a *.diff.gz or a *.debian.tar.* pattern. They had two component version string (where a '-' concatenates the upstream version and the debian version). Right, the package should be non-native. But for some reason it is. All versions in bionic since release have been native though. The current version of this pam package has no extra archives, so it seems to be a native debian package, but it cannot be native package because it has a wrong version string format for this package format. I have found a description of the debian source package formats here: https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.debian.org%2FDebianMentorsFaq%23What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237917170=mlK4GHfo2WHHTORqX52NBT23lHUkhNVArQLqZ0rR7Aw%3D=0> I have also checked the gbp tool source code, and it seems to be a compatible one with this description. Could you please make a correct version string if you want this will be a native package, otherwise please generate a *.diff.gz or a *.debian.tar.* archive, just like an older version of this package! It's back to non-native in focal and groovy. It might make sense to fix it to be non-native in the next SRU, but it doesn't seem worth performing a SRU just for this to me. Cheers, mwh If I can help anything, please let me know! Thank you in advance, Arnold Czeman -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com<mailto:Ubuntu-devel-discuss@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ubuntu.com%2Fmailman%2Flistinfo%2Fubuntu-devel-discuss=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237927164=ZBWhIE05dkw4sNIvmr%2FRNKbSQtuaIjYIu0uCuzsmFZs%3D=0> -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue
Hello Michael, The next SRU would be good. Thank you. Cheers, Arnold Czeman From: Michael Hudson-Doyle Sent: Monday, September 7, 2020 12:51 PM To: Arnold Czeman (aczeman) Cc: ubuntu-devel-discuss@lists.ubuntu.com Subject: Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe. On Sat, 5 Sep 2020 at 06:39, Arnold Czeman (aczeman) mailto:arnold.cze...@oneidentity.com>> wrote: Hello, I have a little problem with the newest version of pam source package on Bionic. https://bugs.launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2/<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fpam%2F1.1.8-3.6ubuntu2.18.04.2%2F=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237917170=TO5%2FcquslSMlK94UrM%2FIorsBLxQQUiSpSR2021FQimM%3D=0> I would like to import to a git repo with gbp tool, but this package seems to have a wrong a package format. The earlier version of this package were non-native debian packages, they had extra archives which name match a *.diff.gz or a *.debian.tar.* pattern. They had two component version string (where a '-' concatenates the upstream version and the debian version). Right, the package should be non-native. But for some reason it is. All versions in bionic since release have been native though. The current version of this pam package has no extra archives, so it seems to be a native debian package, but it cannot be native package because it has a wrong version string format for this package format. I have found a description of the debian source package formats here: https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.debian.org%2FDebianMentorsFaq%23What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237917170=mlK4GHfo2WHHTORqX52NBT23lHUkhNVArQLqZ0rR7Aw%3D=0> I have also checked the gbp tool source code, and it seems to be a compatible one with this description. Could you please make a correct version string if you want this will be a native package, otherwise please generate a *.diff.gz or a *.debian.tar.* archive, just like an older version of this package! It's back to non-native in focal and groovy. It might make sense to fix it to be non-native in the next SRU, but it doesn't seem worth performing a SRU just for this to me. Cheers, mwh If I can help anything, please let me know! Thank you in advance, Arnold Czeman -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com<mailto:Ubuntu-devel-discuss@lists.ubuntu.com> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ubuntu.com%2Fmailman%2Flistinfo%2Fubuntu-devel-discuss=02%7C01%7CArnold.Czeman%40oneidentity.com%7C4c74e483b3c844323a2b08d8531c0d2b%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637350727237927164=ZBWhIE05dkw4sNIvmr%2FRNKbSQtuaIjYIu0uCuzsmFZs%3D=0> -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: pam 1.1.8-3.6ubuntu2.18.04.2 packaging issue
On Sat, 5 Sep 2020 at 06:39, Arnold Czeman (aczeman) < arnold.cze...@oneidentity.com> wrote: > Hello, > > I have a little problem with the newest version of pam source package on > Bionic. > https://bugs.launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2/ > I would like to import to a git repo with gbp tool, but this package seems > to have > a wrong a package format. > The earlier version of this package were non-native debian packages, they > had extra > archives which name match a *.diff.gz or a *.debian.tar.* pattern. They > had > two component version string (where a '-' concatenates the upstream > version and the > debian version). > Right, the package should be non-native. But for some reason it is. All versions in bionic since release have been native though. > The current version of this pam package has no extra archives, so it seems > to be a > native debian package, but it cannot be native package because it has a > wrong version > string format for this package format. > I have found a description of the debian source package formats here: > > https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F > I have also checked the gbp tool source code, and it seems to be a > compatible one with > this description. > > Could you please make a correct version string if you want this will be a > native package, otherwise > please generate a *.diff.gz or a *.debian.tar.* archive, just like an > older version of this > package! > It's back to non-native in focal and groovy. It might make sense to fix it to be non-native in the next SRU, but it doesn't seem worth performing a SRU just for this to me. Cheers, mwh > If I can help anything, please let me know! > > Thank you in advance, > Arnold Czeman > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
